remember when we had to change nonces lol | binji_x on Binance Square

Trending Articles

Bookmarked and Liked

--

remember when we had to change nonces lol

Disclaimer: Includes third-party opinions. No financial advice. May include sponsored content. See T&Cs.

5

0

Explore the latest crypto news

⚡️ Be a part of the latests discussions in crypto

💬 Interact with your favorite creators

👍 Enjoy content that interests you

Email / Phone number

Relevant Creator

@binji_x

Explore More From Creator

we should solve this problem if we want mainstream adoption: wallets and apps treat nonce state as a private thing despite it being global shared data that lives in the mempool. without a synchronization layer different frontends will diverge and users will face invisible deadlocks like what i had today. the fix may be: > expose pending nonce information through a common api and surface any "stuck" statuses in wallet client uis + prompt replacement logic so users do not have to solve this stuff themselves users should *never* touch nonce gymnastics or need to be exposed to mempool heuristics. until that coordination exists at the apps/wallets level, we will need @basedkarbon & @AgentChud to save us each time. as for what happened, if you're curious: > every evm account maintains a monotonic sequence number called the nonce. >the chain will only accept a transaction whose nonce = the account’s current onchain value. >once a transaction is pending, the same nonce is locked until that transaction lands or is explicitly replaced. >i underpriced one transaction on base so it sat in limbo. >my local nonce cache in rainbow said next nonce is "x" yet the network still expected "n" rainbow coinbase wallet and rabby all signed new payloads with nonce x but without the required gas bump to satisfy the replacement rule every node discarded them and no txs went through. as a user *every* wallet gave zero user feedback that this was the root of the issue. to actually implement the solution, @MetaMask rescued me because its advanced panel exposes both nonce and dynamic fee fields. i resubmitted a 0 eth transfer to myself with the identical nonce as my last tx and a much higher priority fee + gas limit and the backlog cleared within seconds.

--

we should solve this problem if we want mainstream adoption: wallets and apps treat nonce state as private thing despite it being global shared data that lives in the mempool. without a synchronization layer different frontends will diverge and users will face invisible deadlocks like what i had today. the fix may be: > expose pending nonce information through a common api and surface any "stuck" statuses in wallet client uis + prompt replacement logic so users do not have to solve this stuff themselves users should *never* touch nonce gymnastics or need to be exposed to mempool heuristics. until that coordination exists at the apps/wallets level, we will need @basedkarbon & @AgentChud to save us each time. as for what happened, if you're curious: > every evm account maintains a monotonic sequence number called the nonce. >the chain will only accept a transaction whose nonce = the account’s current onchain value. >once a transaction is pending, the same nonce is locked until that transaction lands or is explicitly replaced. >i underpriced one transaction on base so it sat in limbo. >my local nonce cache in rainbow said next nonce is "x" yet the network still expected "n" rainbow coinbase wallet and rabby all signed new payloads with nonce x but without the required gas bump to satisfy the replacement rule every node discarded them and no txs went through. as a user *every* wallet gave zero user feedback that this was the root of the issue. to actually implement the solution, @MetaMask rescued me because its advanced panel exposes both nonce and dynamic fee fields. i resubmitted a 0 eth transfer to myself with the identical nonce as my last tx and a much higher priority fee + gas limit and the backlog cleared within seconds.

--

getting this error on my wallet; its odd because i have all the neccessary funds for this... anyone know what's up? i am on @base same issue across @Rabby_io & @rainbowdotme

--

ethereum say it back

--

who is the biggest extractor in crypto history?

--

Latest News

T-Mobile Distributes Settlement Funds Following 2021 Data Breach

--

Whale Increases Bitcoin Holdings Amid Rising Profits

--

DWF Labs Faces Losses in Recent Altcoin Investments

--

Trump Warns Musk Against Supporting Democratic Candidates

--

Deutsche Bank Considers Stablecoin Issuance Amid Crypto Legislation Progress

--

Trending Articles

Given the period in which there is a lot of talk about xrp a

🚨 $330 Million in Bitcoin Stolen Through Social Engineering

$SOL / USDT ✅ Entry Point (EP) EP: $151.80–151.90 (curren

Why Did I Keep Buying Tops and Selling Bottoms? I used to t

🟡 This Crypto Trick Helped Me Spot Winning Coins Before They Pump — And It Still Works

Cookie Preferences

Cookie Preferences