EST AI

95% has been recovered. I’m keeping an eye on the remaining 5%.

In Binance’s 11-02 recovery update #5 , two figures appear side by side: about 95% of the affected amount is covered; the remaining 5% consists of low-liquidity tokens not on the top-ten list, which they’re still working with partners to recover.

There’s also a more concrete point in the same announcement: a zero-knowledge proof has been generated for the 10-31 reserve snapshot. Holders of these 10 coins—BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC—can install a verification tool themselves and check the 1:1 backing.

The next batch of withdrawals is scheduled for 11-03, and the announcement says they’ll be enabled in stages.

What you can verify for yourself is evidence. What you can’t is just an announcement.

Would you run the verification yourself, or wait for the next announcement?

#链上数据 #行情速评 $BNB

872 likes, and it took me just three sentences to take it apart.

The bull market is back. Traders who know how to use AI have a shot at reaching A9 this cycle. Build your first AI trading bot in ten minutes.

I opened the short link he shared, and it took me back to the image attached to that very post. The prompt was the same throughout: the opening said “personal trading reminder bot”; the goal said “only responsible for watching and calculating; I always decide whether to place a trade”; the data source said “an API key that requires no trading permissions”; and the restrictions said “never open, close, or modify trades automatically.”

The post calls it a trading bot; the image calls it a reminder bot.
What’s being sold on the outside is a hand; what’s written on the inside is something with no hands.

Next time you see “AI trading bot,” scroll to the very bottom of the prompt and search for three words: reminders, permissions, and placing trades. If only the first two appear, it’s just an alarm clock.

Do you want an alarm clock that watches the market, or a pair of hands that can open trades?

#ai交易 #行情速评 $BNB

Of 2,394 listings, only 37 mention “monthly” in the description. 1.5%.

I downloaded and counted all the public listings on this marketplace: 2,394 listings, 1,053 sellers, one price per listing, median price 20 USDC; 94% of gigs promise delivery within 1 to 3 days.

Pay per use is the default; almost nobody mentions monthly pricing.

Looking at it the other way, it’s not that sellers don’t want to charge monthly. It’s that this marketplace only has fields for “unit price + delivery time,” and each order is settled separately in escrow, with no renewal option. To charge monthly, you have to rely on people remembering to come back next month.

My own 11 API listings are all priced per use too. I haven’t added monthly fees this week; first I’ll see whether pay per use can bring in repeat purchases.

How will the data API business ultimately charge?
A Pay per use, pay each time you use it
B Monthly, a fixed fee for unlimited use
C Hybrid, pay per use + a monthly fee cap
D Tiered pricing by volume, the more you query, the lower the unit price

I’ll bet on A for now: most buyers are programs. 300 queries today, 0 tomorrow; a monthly fee means betting upfront on how much they’ll use. Which would you choose?

#链上数据 #agent经济 $BNB

Are you still going to FOMO into the words “AI Agent”?

This morning, when I posted my BIBIAI accounting, I wrote: “It’s not a chicken leg, and it’s not NPCs lording it over everyone—it’s the first lesson in a group chat member’s startup.”

Now I can put it more bluntly: Most of this AI Agent wave isn’t productivity—it’s a new wrapper for fleecing retail investors.

Two examples:
• AgentLife: 0.00204 BNB, 100,000 tokens; 271/5,000 slots filled, pool not launched yet, app shows ≈$0
• BIBIAI: 0.00428 BNB, 8,505,437 tokens; next-day accounting: -24%, pool at 86.7 WBNB

Total cost: about $4.43. Current balance: $2.28, down 49%.

An Agent ID is just an identity, not a source of returns; being able to sign with a CLI doesn’t mean you’ll make money. People launching projects in the group are great at pitching “AI Agent,” because those words are the biggest FOMO trigger right now.

A reminder: Check the pool, contract, and mint progress first. Anyone telling you to buy 10 allocations is probably the one starting a business. Don’t FOMO with money you need for living expenses.

#AItrading #onchaindata $BNB

Yesterday I asked, “Is this a big opportunity, or am I just holding the bag?” Today, BIBIAI has given me the answer.

My 1 BNB buy: 8,505,437 tokens, cost $3.01; now worth $2.28, down 24%.

The liquidity pool is still there: 86.7 WBNB / 227.3 billion BIBIAI, with about $61,000 on the WBNB side; price: $0.000000268.

So, it’s no chicken leg, and I’m nowhere near the top of the food chain; it’s the first lesson in a group-chat startup: lose 24% first. At least the liquidity pool hasn’t vanished, so you can still get out if you want.

Next time someone says “0.02 BNB turns into $400,” ask them to show you the price 24 hours later.

Would you cut your losses now, or wait to break even?

#ai交易 #链上数据 $BNB

A startup project from someone in the group has been getting a lot of buzz lately. It’s called Agent人生, so I had the AI mint one on its own.

It didn’t click the site’s button—it signed directly using Agentic Wallet’s CLI. It didn’t check the pool or ask me.

0.00204 BNB (about $1.4) for 100,000 Agent人生; the balance is in image 1.

It said only 100 had been minted. By the time I was done, there were already 271. The pool opens at 5,000, and there’s no pool yet.

I minted just 1, not 10. It’s unaudited, and 30% goes to the project team. This is a test, not a buy recommendation.

Be wary of startup projects pitched by people in your group: if they’re urging you to mint, they’re probably the ones building it. We’ll take the hit if it goes wrong—don’t risk your living expenses.

Is this a big opportunity, or are we just holding the bag?

#ai交易 #链上数据 $BNB

I had the AI mint 1 batch on its own for 0.00428 BNB.

I didn’t click the site’s button. I signed directly using the Agentic Wallet CLI. It didn’t check the pool or ask me.

1 batch = 8,505,437 BIBIAI; total minted on-chain: 22,214; cost: $3.01 + $0.02 gas. Agent ID: est.

Is this a big score, or am I just exit liquidity?

#ai交易 #链上数据 $BNB

I followed the setup from a viral tweet, step by step.

I stopped at step three, because I read the instructions it told me to read, word for word.

Those instructions weren’t written for people.

They were written for AI.

They said: the payment contract starts with 0x3643, followed by the words “the ONLY address that accepts payment.”

Then came three function selectors.

mintWithBnb, 0xe38fd349.

mint, 0x836a1040.

approve, 0x095ea7b3.

It even specified the allowance: 102% of the cost.

And the gas: the estimate plus 20%.

This was no longer a set of instructions.

It was a bundle of commands that could be used to assemble a transaction directly.

Any model that read it wouldn’t need to understand the project, read the white paper, or ask anyone.

It would know where to send the transaction, how much to send, and which function to call.

All of that was done right. The project team had been more thorough than I expected: the old address was clearly marked as retired, with its balance migrated; it was made clear that a plain transfer wouldn’t mint anything and would revert; and they even provided a maxCost to protect against slippage.

But there was one thing the document couldn’t prove.

Was that “the ONLY address” actually true, or was it just written there?

What AI sees is a block of text.

It has no second source of information to verify whether that address was officially deployed.

If the domain is hijacked, the page is replaced, or the resolution is poisoned, in any of those cases, AI will still read “the ONLY address.”

And it will send the transaction.

This isn’t a problem with any one project.

It’s a problem shared by all “documents written for AI.”

For twenty years, we’ve taught people not to click unfamiliar links.

Now we’re handing the act of “reading the documentation” to a model that doesn’t know how to be suspicious.

It won’t ask: Is this the right domain?

It will just execute.

So I’ve set three rules for myself.

First, whenever a process asks AI to read a document, read the document yourself first.

Second, verify every address in the document on-chain, regardless of what the document says.

Third, don’t use any tutorial that skips the step of “confirming.”

That skipped step is the whole of security.

Do you think this is a problem with the documentation, or did we hand over our judgment too soon?

#链上数据 #AI交易 $BNB

Original post opening: 0.02 BNB, 24 hours, $400, AI does the work for me, no need to watch the charts.

The most expensive part isn’t the $400—it’s making you think AI is the key.

I broke down the original post and the quote post: what got copied was a public spreadsheet listing 4,942 early-mint addresses. 4,788 addresses paid a total of 54,754.68 USDT, an average of $11.44; 1,805 addresses still hold 118.17B tokens.

At the current price, that’s about $949,000 on paper; the pool has only $328,000 in liquidity. If everyone on the list sells at once, the order book won’t hold up.

The “$400” figure is based on one 50-million-token share, and is just the paper value of that one share; 10 shares would be about $4,017. The numbers aren’t wrong—the problem is presenting paper value as 24-hour returns.

The list’s entry requirements are $500 in liquidity and 20 trades. That shows you can pay to earn the label “smart money.”

When you see “AI makes money for me,” first check your approvals for “unlimited,” then ask who made the list.

Do you think AI is making money here, or is the list just luring people in?

#链上数据 #ai交易 $BNB

I pulled up that list of 100, and the thing that stood out most was “free mint.”

The biggest risk isn’t going to zero. It’s connecting an Agent that can sign transactions to a list anyone can get onto, just to snag a free mint.

The list’s only requirements are $500 in liquidity and 20 transactions. An attacker can get on it for a few hundred bucks, then have their wallet click a “free” mint. A copy-trading Agent sees “smart money is minting,” runs a clean simulation, and executes.

The money is usually taken in the approval or the second transaction. You see a “$0 mint,” but what it’s really getting is your authorization.

Even more ironically, the official documentation file I found still points to an old minting contract; the white paper says that contract has been retired. If the Agent follows it, your money could end up at an address that can no longer mint.

These wallets have daily limits, token allowlists, and require App confirmation for high-risk transactions. But the tweet tells you to install the entire skill pack and enable automatic minting, bypassing all three safeguards.

If you’ve installed it, do these three things first: check your authorization records, set your daily limit to $50, and require App confirmation for high-risk transactions.

Do you think this is AI helping you get in on new launches, or are you handing your signing authority over to a list?

#链上数据 #ai交易 $BNB

I summed a 4,942-row table three times, and each time I couldn’t get 64 to line up.

The post says “4,000 smart-money wallets are buying into the launch.” I pulled the spreadsheet: 4,942 addresses in total, 100 after filtering. Then the post says 64 of those each hold 500 million tokens. But the full table has 100 addresses holding 500 million; in the filtered list of 100, there are zero.

Three numbers, three different definitions.

Now look at those 100 “smart-money” wallets: together they’re down to just 626M tokens, worth about $5,000 at the current price; but their wallets hold a combined $118,000 in liquid assets. That at least suggests most of these people are no longer holding the coin.

You might be following a seller list, not smart money that’s still accumulating.

The full table is even more direct: 1,805 addresses still hold 118.17B tokens, worth about $949,000 on paper; pool liquidity is only $328,000. If everyone on that list sells, the order book won’t hold up.

Next time you see “4,000 smart-money wallets,” check three numbers first: how many in total, how many after filtering, and how many actually still hold the token.

Do you think the data just doesn’t line up, or was it never meant to line up for you?

#链上数据 #ai交易 $BNB

23:18:42, I revoked it. Then Agent Wallet went quiet for 9 hours.

85,000 blocks, and not a single new transaction.

If it were an adversary, revoking it would only make it try again another way.

It didn’t.

It simply disappeared, as if it had never existed.

I can’t explain it, but I can give you three things to check.

First, look at the chain, not the app.

The app’s list is for you. The records on the chain are for everyone.

Second, check whether the recipient has transferFrom.

If it does, it can move your money; if not, it’s just for show.

0x0000…0001 is a precompile, a mathematical function. It can’t steal anything.

A real phishing scam looks exactly the same; only this one address changes.

Third, don’t believe that “small amounts are safe.”

An approval for 1 wei and an unlimited approval use the same function.

One click, and the habit is formed.

What I most want to talk about isn’t these 12 transactions.

It’s this:

You can look up every transaction, every block, every unit of gas.

But you can’t find out who pressed the button.

Is your Agent Wallet really only in your hands?

#链上数据 #AI交易 $BNB

Set it up in three steps, get it running in five minutes, and then the Agent Wallet is no longer yours.

You’ve seen posts like that, right?

The headline says: Get into AI trading with zero experience. No need to watch the market—let it run by itself.

You click in. Three steps.

Step one: paste a line of code.

npx some-package, or curl some-package | bash.

You think you’re installing software.

But really, you’re giving it full access to your computer.

It can read any file on your hard drive, including your Agent Wallet session.

What’s a session?

After you log in to Agent Wallet, the server gives you a credential.

That’s your signing authority.

Whoever has it can make the wallet sign transactions.

No need for you to enter anything, use your fingerprint, or click to confirm.

Step two: let the AI install skills by itself.

One line of code downloads a bunch of packages, compressed into hundreds of thousands of characters on a single line.

The tutorial doesn’t explain what they do, and you can’t understand them anyway.

Step three: authorize.

It won’t ask you for everything right away.

First, it asks you to authorize 1 wei.

So little that you think it doesn’t matter.

“Necessary authorization. It won’t run without it.”

You click, then forget about it.

Because you can’t read the on-chain records.

If I were the one who made this stuff, I’d do one more thing: make sure you can’t find anything.

Add a line to the command to delete logs, clear the cache, and overwrite the history.

Hidden on line 37.

All you see are green characters scrolling by, and that last line: “Installation successful.”

So when I say, “I spent 9 hours looking and found nothing”—

it’s not that I didn’t look.

It’s that someone didn’t want me to find anything.

#链上数据 #AI交易 $BNB

11 versions. I was looking for a coincidence.

Let me make one thing clear: Agent Wallet isn’t an ordinary wallet.

It hands signing authority to AI. You authorize it once, and after that, it signs on its own.

So my first thought was: it must have been one of my own programs.

So I dug everything up.

A trading bot, with 11 backup versions.

The authorization in every version was hard-coded: authorize the trading contract, with the allowance maxed out.

Not this format. Ruled out.

There was a copy on another server, but the process hadn’t even started. Ruled out.

The wallet’s command-line tool, with 250,000 characters crammed onto one line.

I searched for the word “approve.” No matches. Ruled out.

My activity log for that time period was empty. Ruled out.

All four leads were dead ends.

Anyone would wonder: could there be a fifth possibility I hadn’t seen?

So I changed tack and checked the entire blockchain.

During that same time period, there were 12 USDT approvals to 0x0000…0001 across the entire blockchain.

Every single one was mine.

This wasn’t a mass scan. It was targeted at this Agent Wallet.

At this point, there’s only one question left:

I didn’t write the code, I didn’t perform the actions, and the scan didn’t find me.

What route did these 12 transactions come through?

Next episode: the posts that teach you how to make money with Agent Wallet.

#链上数据 #AI交易 $BNB

12 transactions. My Agent Wallet signed them itself. I didn't click a single one.

First, let's be clear about what this thing is.

An Agent Wallet is when you hand your wallet over to AI and let it trade on your behalf.

It doesn't need to ask you every time, because it holds the signing authority. You only need to authorize it once.

I used one for a month and thought it was pretty convenient.

Now, open your Agent Wallet and tap the “Authorization History” section.

Do you also see a bunch of entries you don't remember approving?

I never opened it.

That is, until the evening of October 30, when a notification popped up on my phone:

This authorization carries a high risk.

My balance was 0.

What could a 0 USDT Agent Wallet possibly authorize?

I tapped in. The recipient address was a string of zeros, with a 1 at the end.

The amount field said: 0 USDT.

I laughed at the time.

An authorization for 0 USDT was worth a red warning box?

Then I checked the blockchain.

Those two transactions were real.

Block 130685065, 22:58:09, sent from my address.

gasPrice 0.0693, nonce 277.

I didn't click anything.

Two seconds later, the second transaction. nonce 278.

I started scrolling back.

By 23:18, there were 12 transactions in total.

All to the same address, all for 1 wei.

The nine transactions in between were one every 3 seconds.

Three seconds is enough time to blink twice.

No human could click that precisely. This was a program running.

It knew where my Agent Wallet was, knew how to make it sign, and knew when to stop.

The only thing it didn't know was that I would check the blockchain.

Now it's your turn to do something.

Open your Agent Wallet, tap “Authorization History,” and see if there's an entry with a recipient address made up of a string of zeros.

If there is, comment “Yes.”

If not, comment “No.”

I want to know how big this number really is.

#链上数据 #AI交易 $BNB

Binance was hacked for $6.3 billion this time, with $3 billion frozen. The official statement says they’ll use SAFU to cover the rest themselves.
CZ’s exact words were, “User funds are safe.”
It’s fine to feel reassured, but don’t let your guard down—wait for PoR and withdrawals to resume.

#链上数据 $BNB

13 “zero-cost mints”—I read the contracts one by one, and now only 4 are still free to mint.

The data is current through BSC block 130582651, with BNB at $707.74. Of the 13, 6 are sold out or closed. For 3, the free tiers have been exhausted and prices have gone up; one went from $0.36 to $1.00.

The most painful one is ranked #1: the tweet itself says “about 2,507 minted,” while its free tier is for the first 2,500. By the time the tweet went out, the free spots were already gone. Starting with mint #2,508, you have to pay $0.25.

There’s another catch nobody mentions: 12 of the 13 require you to already hold an .ai Agent ID. Only one doesn’t. One project closes its window 4 days after deployment, and it expires today, yet the tweet says “mint anytime.”

There’s just one thing you can do: when you see a zero-cost mint, check two numbers first—how many have been minted, and the free-tier limit. Once the former is greater than the latter, “zero-cost” is history. You’re making someone else a profit.

The free-mint window is only ever a day or two, and only the earliest people can make it in time.
Would you go mint the few that are left, or consider this round over?

$BNB #链上数据 #AgentEconomy

“$50, 4 minutes 14 seconds, $3,532.” This trading report has been circulating for days, and I’ve recalculated every figure.

70.6x, for a net profit of $3,482. 99 trades in 254 seconds—that’s one keystroke every 2.57 seconds. To reach that multiple, each trade would need to net 4.39%, with the entire balance compounded each time.

Work backward: with an 82% win rate and 4.39% per trade, assuming losses are 20% as the post itself claims, the average win would need to be 9.75%. Win 9.75%, lose 20%—that’s a structure where small wins are outweighed by big losses.

Three things don’t add up:
① The first trade was $233, despite starting with only $50; the peak was $25,400, 7.2 times the final balance. Spot aggregators don’t offer leverage.
② Fees totaled $104. At a 1% fee rate, that would imply a trading volume of $792 to $12,689.
③ The only two trades with timestamps show a BONK sale followed by a buyback 3 seconds later. That one move alone would account for one-sixth of the fees.

I’m not calling it true or false. Just one suggestion: when you see “dozens of times your money in a few minutes,” first look for the timestamp of the final balance, then calculate the net return required per trade. If either is missing, the numbers are just numbers.

What gets amplified is never the multiple—it’s people believing there’s a shortcut.
Do you think this is fast execution, or a sales pitch?

$BNB #链上数据 #CopyTradingRisk

On the night Binance was hit, I wasn’t watching how much was stolen. I was watching a price gap on-chain that usually wouldn’t last more than a few seconds—but this one stayed open for a full hour.

First, three figures, each using a completely different basis. Don’t mix them up: Binance most recently said it had frozen $3 billion; third parties estimate $5.8–5.9 billion was stolen, which Binance has not confirmed; and one address moved about $3.47 million off Aave within an hour (based on transaction-by-transaction figures compiled by an on-chain blogger, which I haven’t independently verified).

The “$3 billion” figure changed three times in three hours: on-chain data first showed $1.79 billion, Binance’s first confirmation was $2.54 billion, and the latest figure is $3 billion. Three official figures for the same incident. When you read them, first ask: who said this, and when?

Here’s how the price gap formed: withdrawals were paused from 04:40 to 05:40, so ETH couldn’t get out of the exchange. On-chain buying pushed ETH on Uniswap to $2,560–2,750, with a few trades topping $3,000. But Aave uses an oracle based on prices from centralized exchanges, which stayed at $2,250–2,290 the whole time. So you could borrow ETH against USDC collateral, with it valued at just $2,280, then sell it on a DEX for over $2,600. You could deposit the USDC from the sale and keep borrowing and selling. ETH was 15%–30% more expensive on-chain than on exchanges, and that gap stayed open for almost an hour.

How did the top performer win? They already had 37 million USDC sitting in Aave; entered 24 minutes after the incident began; split the trades into 18 transactions of 300–1,000 ETH each, using an aggregator to reduce slippage; then bought back ETH to repay the debt as prices fell, wrapping up in two hours. It wasn’t luck—they had their ammunition ready in advance.

Four tips for ordinary users: don’t click “official compensation/unfreezing” links in DMs; don’t keep trying small transfers while deposits and withdrawals are paused; when a black swan event hits, first look for your own “token issuance window”; and don’t count on this kind of money—it’s risky. If borrowed ETH keeps rising, or gas gets expensive, small trades may not even cover your costs.

The long infographic breaks down everything above, and labels the different bases for the figures too.

Do you think what happened during that hour counts as arbitrage, or as picking up money someone else dropped?$BNB $ETH #链上数据 #MarketBrief