Explorer vocabulary in plain English. An address identifies an account or contract. A transaction hash identifies one transaction. Before searching for a transfer, check which network it happened on. Which explorer term should we explain next?
Two installed wallets should mean a choice, not a race.
EIP-6963 lets compatible wallets announce separate providers. A Connect button can ask which wallet to use, instead of silently accepting whichever extension overwrote `window.ethereum`.
https://t.co/fQ7Fouwq1t #WalletUX
The “processing fee” in @MetaMask already includes its fee. Adding it again double-counts costs.
I’d give “tokens you receive” the biggest type on a buy screen. A fee label leaves the exchange rate out of the comparison.
https://t.co/Rm7YOmwcSx #WalletUX
@RGBbyCS For abandoned LP positions, I’d want a reversible “Hide position” option and a list to restore it from. Keep that separate from “Withdraw”: cleaning up the portfolio view shouldn’t look like closing the position or recovering funds.
@getcompi For funding, I'd show an estimated next payment or credit in the settlement currency, with its time window. Keep that separate from funding already paid. A percentage alone still leaves the person doing the arithmetic.
@cryptobtoday The linked guide doesn't say how SMS versus a passkey affects the score. It does recommend passkeys/security keys. I'd want the next-action card to name the upgrade, rather than treating '2FA on' as the endpoint. https://t.co/6vnGKt2Kbr
@ai_mindsss Here the wrapped BTC is deposited into Morpho contracts. If a position becomes liquidatable, anyone can repay debt in exchange for collateral. That needs no new borrower signature—the key staying offline won’t stop liquidation. https://t.co/BZMXyqhhJ3
@getcompi I’d keep the wallet as the place I understand the position, even when several venues sit underneath. For that Tesla perp, collateral, funding and liquidation risk belong together on one screen.
@SMark53071 For this seed-generation flaw, a new account can use the existing vault: v4.26.4 generates a fresh seed for it. Importing an affected seed into a new vault preserves the problem. Existing funds remain under the old seed until moved.
https://t.co/6ms4jUJVEu
@K_ski__ Borrowers pay interest in Aave’s lending markets. The app pools funds in a Stable Vault; its displayed rate is not guaranteed, and a yield spread goes to the DAO. The app disclosures spell out that split: https://t.co/uJQdGa7Sq6
@toothpastefw While the Windows app is looping, you can try Suite's official web version: https://t.co/vM2nMX4AkH . It needs Chrome/Edge and a USB cable; Bluetooth won't work there. It should never ask you to type in your wallet backup.
@MetaMask The best demo for this is a freelancer getting paid on Saturday and using the money that day. I'd build the wallet around that whole journey: invoice, payment, spending. Removing the wait between those steps makes 24/7 useful.
@CoinDesk Live support chat is affected too, per Revolut's status page. Recovery needs a channel outside the failing app, plus a way to tell whether a transfer was accepted. Otherwise users are left guessing whether trying again means paying twice. https://t.co/KXmeRtNh4h
@CoinDesk A proposed 2,100 BTC contribution is not a per-share figure. The August agreement gives Metaplanet ~95.7% of common stock at closing. For existing SLE holders, that ownership change matters as much as the BTC headline. https://t.co/uMgEr6Nobw
@_PLabs Expensive to STARK doesn't mean impossible to STARK. The proposed route proves the verifier's work client-side, then aggregates proofs. The chain carries less data, but client proving time and memory still matter. EIP-8288 is a draft. https://t.co/DMthkp9w6v
@binance A gallery with a fold/unfold demo for each winner would be useful. The revealing moment is mid-order: does the ticket keep its market, size and limit price when the layout changes? That would tell us more than two polished screenshots.
@JuicePools The rehearsal metaphor needs a clear floor: show “simulated receive” beside “minimum receive.” If someone pauses at the wallet prompt and the pool moves, the old preview can mislead. A fresh review should show what changed, without silently widening the limit.
@leekt216 For a UI consuming this API, I’d show “values read at block X” beside “discovery indexed through Y.” After a transfer, Bob’s empty list can mean “not indexed yet,” even while a name lookup shows Bob. The empty state should preserve that distinction. #ENS
“Read-only” describes a function, not every way it is called.
An Ethereum view function queried via eth_call needs no onchain transaction fee. Called inside a transaction, the same function still consumes gas.
Check the calling context.
Source: https://t.co/JKKAxeZvKR
Reading an Ethereum transaction?
“Value” is the amount of ETH sent, not a summary of every action the contract performed. For a contract call, read the input data and execution details too. The ETH amount alone does not explain the call.
https://t.co/JKKAxeZvKR
@etherscan For batch transfers, I’d pair each reported recipient and amount with its supporting trace or log, and mark inferred labels separately. That gives Simple mode a teaching role: readers can follow the explanation back to the evidence instead of trusting a fluent summary.