Update from TxWhy


Our homepage demo wallet is a public exchange wallet. Around October 30 its USDC account was frozen by the token's issuer, so two of our demos began answering "AccountFrozen". The engine was right: that is the true cause and no rebuild can fix it. The demo was wrong to depend on one account. Demos now choose their wallet from live chain state on every request, and a script checks all of them end to end after each deploy.

The daily gap hunt found this: 128 of the last 735 failed Pump.fun transactions were one error, QuoteReserveThresholdReached, from an unnamed program whose source calls itself pump_buy_guard. All 1,000 of its latest transactions failed the same way, about 1,400 a minute from one sender, each refused before it ever called Pump.fun. It is a sniper's entry rule doing its job. We had been answering it with the program's own message, which is the string "6018", and counting it with people's failures. It now gets a real answer, and 789 past cases were refiled as bot flow. The share of people's failures we rebuild is 21.2%.

New for integrators: the repair engine is now also a JSON-RPC method, repairTransaction, so an RPC provider can mount it behind its gateway next to a node's own methods.

Numbers: 45.3 million transactions sampled since September 21, 212,000 real failures replayed, 21,369 rebuilt and verified, zero engine errors. txwhy.vercel.app/proof

Give feedback to the team

Your message is private to you and the TxWhy team.

Create an account to send feedback

After signup, you can write a private message with this update attached.

More from TxWhy

All project updates