Home
Notification
Profile
Trending Articles
News
Bookmarked and Liked
History
Creator Center
Settings
binji_x
--
Follow
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
Disclaimer: Includes third-party opinions. No financial advice. May include sponsored content.
See T&Cs.
77
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
Sign Up
Login
Relevant Creator
binji_x
@binji_x
Follow
Explore More From Creator
oh hey it’s going to be a big week for eth btw
--
it’s going to be big week for eth btw
--
eth cc roll call 👇 who’s coming to cannes?
--
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.
--
Latest News
Bitcoin(BTC) Surpasses 106,000 USDT with a 0.51% Increase in 24 Hours
--
Cryptocurrency Market Experiences Significant Liquidations
--
Hong Kong's Stablecoin Regulations Limit Sales to Licensed Entities
--
Polymarket's Success Highlights Potential for Mainstream Crypto Products
--
Vitalik Buterin Discusses AI's Impact on Learning and Development
--
View More
Trending Articles
Trump Meets Ripple CEO – $XRP Surges on Breaking News
Farhan shamshad 408
$BTC 🚨 BREAKING: BTC Just Shattered Expectations at $106.
Ametistho
📰 Trump–Ripple Meeting Sparks XRP Momentum The crypto worl
zali5120
🚨 OM Coin to $9 Again? Let’s Break It Down 🧠💥
SHARP_TRADER
Pi Coin Users Are FUMING: Wallet Migration Goes TERRIBLY Wrong!
fb ansari
View More
Sitemap
Cookie Preferences
Platform T&Cs
