okay so i just wasted half my day on what i thought was a simple stuck nonce on Bittensor EVM @bittensor
was deploying a contract, first tx failed, second went through — classic right? except something weird happened. every single transaction after that was throwing "unknown error". not underpriced, not wrong nonce, just... unknown error. lovely.
spent hours trying everything. different RPCs, bumping gas to absurd levels, even spun up my own local node on a rented server thinking it was a rate limit issue. nothing worked.
turns out the failed deployment silently set an EIP-7702 delegation on my wallet as a side effect. my EOA basically had contract code attached to it without me knowing
the wild part? zero trace of it on the explorer. evm.tao.app shows absolutely nothing. no transaction, no event, nada. the only way i found out was calling eth_getCode directly on my own address and going "wait... why does my wallet have bytecode??"
tried removing it the normal way (type 4 txs) — nope, "unknown error" again. classic.
eventually found a non-standard way to redirect the delegation to a different contract that swept the funds out automatically. wallet unblocked, money safe, sanity partially recovered
honestly tho — would love to see the TAO team add proper type 4 support, show delegations on the explorer, and give us better error messages. would make building on Bittensor EVM so much less painful for devs
if your TAO wallet is randomly throwing "unknown error" on everything — run eth_getCode on your address before you do anything else. you're welcome
#Bittensor #TAO #EIP7702 #devlife
English
