@WhatIsBrewing_@Trezor@SkyMoney@KyberNetwork@HyperliquidX Great question 🙂
Here’s a real one for: every screen says “Token approval,” with who you’re approving and the exact allowance. Unlimited ones get their own warning.
The spender should show by name (1inch here). It's a small regression, already fixed for this month's FW release.
Pretty happy with this one. Sky, KyberSwap and HyperEVM now clear sign on Trezor, plus a bunch of extended coverage 👌
If you're building a dApp and want your users to stop signing confusing hex blobs, get an ERC-7730 descriptor out there. Makes our life a lot easier too 😃
Your Trezor now clear-signs on @SkyMoney, @KyberNetwork, and @HyperliquidX HyperEVM.
Plus: extended coverage for Lido, Threshold, QuickSwap, Bedrock, Figment, Tally, Celo, Flare, and Tesseract.
The action, the tokens, the amounts. In plain language, on the one screen malware can't touch.
Every integration runs on ERC-7730, an open standard, inside Trezor's open-source firmware. No black box between the transaction and your screen.
The future of self-custody is readable.
Self-custody is a ticking time bomb?
Keeping your crypto on an exchange is convenient because someone else takes care of everything. But that also means trusting them with your money and relying on them to give you access to it.
Your seed phrase is your superpower, putting control of your money entirely in your hands.
By holding your own keys, you don't have to worry about someone freezing your funds, blocking your transactions, restricting your access, or deciding what you can do with your money.
Convenience is nice, but true ownership is always better.
What is clear signing?
When you swap on the Ethereum network or an EVM chain in Trezor Suite, your Trezor shows the transaction in plain language: the provider handling the swap, what you send, what you receive, and the fee you pay.
Clear signing matters because you can check the trade yourself on your Trezor device before you approve it and make sure it's exactly what you picked. If something doesn’t match, you can reject it on the device.
Looking forward to Saturday's clear signing session at DevCon in Mumbai! Thanks @redduckteam for hosting and for pushing clear signing forward 💪
Me and @suyashcrypto are presenting remotely on what we learned shipping ERC-7730 on Trezor devices 👇
@ParadigmaEdu@Felipether É galera, quando uma corretora é hackeada, mesmo que tu não perca NADA, ainda pode ficar sem acesso ao seu dinheiro até ela resolver 🤡
Mais um motivo pra manter as suas próprias chaves 🔐
The most dangerous button in Bitcoin this week was “Increase fee.”
If you use Electrum, update to 4.8.3.
A malicious Electrum server can fake a pending transaction, tricking you into signing a fee bump that sends your bitcoin to the attacker.
The attacker matches the last 4 characters of the original recipient address. The only part most people actually check.
Pro tip: Read the whole damn address. Every time. It takes just a few seconds.
@sundial1000 Fair concern. 128 was chosen to cover what other hardware wallets allow, so anyone migrating can fit their passphrase.
It's also a cap, not a target: ~12 random words already gets you past 128 bits.
I'll make sure our knowledge base makes that clear to avoid confusion, thanks!
We just shipped support for passphrases up to 128 bytes in Trezor firmware 2.13.0 🔐 (Model One stays at 50)
The extra room is great. But with passphrases, small mistakes can be permanent.
Here are a few things we would like every user to know 🧵
You used to approve transactions you couldn’t read and hope for the best.
Not anymore. Ambire and @Trezor now show exactly what you’re signing, like this @aave supply.
Blind signing out. Clear signing in.