Missed the entry again. Bridge leg still not usable, agent already treating the capital like it had landed.
I was in OctoClaw logs too late and the signal was not the annoying part. Setup flagged. Route sim passable. Local balance cache had a path that looked clean for about half a second. Source tx had a hash, a few confirmations, enough for the script to start acting brave, except the destination side still had not indexed and one of the load-balanced RPC endpoints was answering from behind reality.
Bad read. Agent trusted it anyway.
Model is fine, route is not. Relayer still has not landed the message, destination view is stale, one RPC says funds exist, another says no balance, cache is holding onto the last good-looking response, and now the write path is doing that stupid half-failed thing where an earlier attempt is not fully dead but not fully accounted for either, so the nonce order is already broken before the agent even signs the next transaction.
Simulation passes. That almost makes it worse.
Live tx sizes from the cached balance. Replacement gets dropped somewhere in mempool sludge or lands after the candle already moved. On the user side it just looks like OctoClaw missed, woke up late, shoved the wrong size, froze for no obvious reason, whatever label they put on it while the capital is stuck in that ugly overlap of bridge accounting not caught up, relayer not done, cache lying, and RPC freshness being basically a coin flip.
Next tx still fires into it, nonce mismatches, gas burns, stale route.