binji_x(@binji_x)s statistik

--

what’s there to do on solana?

Ansvarsfriskrivning: Inkluderar åsikter från tredje part. Ingen ekonomisk rådgivning. Kan innehålla sponsrat innehåll. Se användarvillkor.

SOL

154,11

+2.14%

111

0

Utforska de senaste kryptonyheterna

⚡️ Var en del av de senaste diskussionerna inom krypto

💬 Interagera med dina favoritkreatörer

👍 Ta del av innehåll som intresserar dig

E-post/telefonnummer

Relevant kreatör

binji_x

@binji_x

Utforska mer från Creator

gotta say, @bankrbot is getting really good. their cb wallet integration could be a big unlock if done right because it removes a huge chunk of the cognitive overhead that keeps people from going onchain less friction = more exploration = more txs ai is the new ui.

--

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.

--

Senaste nytt

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

--

Cookie-inställningar