
Bitcoin OG. Co-founder @Satoshilabs @Trezor @Vexl @TropicSquare @Invity_io
Europe
Joined January 2009
- Tweets4.2K
- Following767
- Followers55.2K
- Likes6K
Sorry, the video is in Portuguese ๐ง๐ท, but this is the first real demo of my Tropic Key project! ๐ด๐
In the video I:
โข Unlock the password manager using the Tropic Key
โข Generate and display a TOTP code
โข Show the encrypted password storage
โข Connect the browser extension to the desktop app
โข Autofill a login and password
โข Log in using a passkey, similar to the Windows Hello experience
The hardware, desktop app and browser integration are finally talking to each other.
Still a prototype, but it works. ๐
@Trezor @tropicsquare
slush retweeted
Itโs been 4 years of not knowing who our customers are.
Vexl started as a gift to the Bitcoin community from @satoshilabs โ to bring Bitcoin back to its original idea: peer-to-peer currency, without centralized intermediaries.
Since then, 20,000 people across 100+ countries have joined Vexl. And the numbers keep growing ๐
We know KYC sucks. So, just this once, weโre rewarding you for the pain.
๐Drop your worst or most ridiculous KYC experience below. Worst one gets a Vexl merch pack ๐๐
slush retweeted
If an enemy wants you to panic to drive you into their flanking manouevre, the best move is to not panic and hold the position. Close the ranks, keep the line tight and dig in.
slush retweeted
Multiple entropy sources are only worth something if the code actually uses them. You can have four different sources of randomness in the device, but if it is using a test generator instead (code bug), none of those sources actually matter. Rolling dices doesnโt imply the device will actually use it. The entropy is not the problem here, the problem is the device not using it.
We already explained that Trezor does not use the affected code. Here are some examples of what we are already doing to make sure we do not accidentally bundle in testing RNG (random number generator):
๐ย We do not use MicroPython's random module at all. It is disabled outright in our firmware config [1].
๐ rng_fill_buffer() reads the STM32 TRNG peripheral registers directly. No macro dispatch, no software path to fall through to [2].
๐ The software PRNG lives in a file literally named "crypto/rand_insecure.c", and compiling it emits "NOT SUITABLE FOR PRODUCTION USE!" warning [3].
๐ random.reseed() exists only under ifdef TREZOR_EMULATOR, and the C function behind it only under USE_INSECURE_PRNG. Two independent guards, and no reseed API in production firmware at all [4].
๐ rng_fill_buffer_strong() fills from the MCU TRNG, then XORs every byte with Optiga output (Safe 3, Safe 5) and, on Safe 7, Tropic output on top. If a secure element fails it returns false and the caller raises RuntimeError. Fail-closed, not fail-quiet on models with a secure element [5].
๐ Our Entropy check makes sure that the hostโs (computer/phone) RNG is mixed in as an extra failsafe [6].
These are just some examples of how we protect from this kind of failure. That being said we never stop building and we always humbly learn from situations like these. So we are carefully studying what lessons can be learned from this incident and we are already drafting more safeguards on top [7].
You donโt have to trust me on this, our code is open-source and you can see for yourself or use your favorite AI model. See the links below. And donโt forget to ask your wallet if they can do the sameโฆ
[1] github.com/trezor/trezor-firโฆ
[2] github.com/trezor/trezor-firโฆ
[3] github.com/trezor/trezor-firโฆ
[4] github.com/trezor/trezor-firโฆ
[5] github.com/trezor/trezor-firโฆ
[6] trezor.io/learn/security-priโฆ
[7] github.com/trezor/trezor-firโฆ
slush retweeted
So I don't know why more people don't scream about this but KYC does not prevent crime.
I'm gonna lay out the numbers here because people do need to see this. The cost of pretending it works is measured in actual human lives now. follow along ๐งต 1/15
slush retweeted
Finally... #TROPIC01 is happily placed on the circuit board of the ๐ง๐ฟ๐ฒ๐๐ผ๐ฟ ๐ฆ๐ฎ๐ณ๐ฒ ๐ณ hardware wallet. The latest flagship hardware wallet from @Trezor.
It is the first open security element deployed in a globally available consumer device, created for those who believe that true trust can only be achieved when you can verify what's inside.
As our CEO @jan_pleskac said: "๐๐ฉ๐ข๐ต ๐ธ๐ฆ ๐ฉ๐ข๐ท๐ฆ ๐ข๐ค๐ฉ๐ช๐ฆ๐ท๐ฆ๐ฅ ๐ธ๐ช๐ต๐ฉ ๐๐ณ๐ฆ๐ป๐ฐ๐ณ ๐ช๐ด ๐ฎ๐ฐ๐ณ๐ฆ ๐ต๐ฉ๐ข๐ฏ ๐ซ๐ถ๐ด๐ต ๐ข ๐ฑ๐ณ๐ฐ๐ฅ๐ถ๐ค๐ต ๐ฎ๐ช๐ญ๐ฆ๐ด๐ต๐ฐ๐ฏ๐ฆ, ๐ช๐ต ๐ช๐ด ๐ข ๐ด๐ช๐จ๐ฏ๐ข๐ญ ๐ต๐ฐ ๐ต๐ฉ๐ฆ ๐ฆ๐ฏ๐ต๐ช๐ณ๐ฆ ๐ฉ๐ข๐ณ๐ฅ๐ธ๐ข๐ณ๐ฆ ๐ช๐ฏ๐ฅ๐ถ๐ด๐ต๐ณ๐บ."
Are you interested in joining more than 300 attendees and thousands online who already know this, and see what exactly ๐ง๐ฅ๐ข๐ฃ๐๐๐ฌ๐ญ does in ๐ง๐ฟ๐ฒ๐๐ผ๐ฟ ๐ฆ๐ฎ๐ณ๐ฒ ๐ณ?
Check out our new case study page atย tropicsquare.com/applicationโฆ
#TROPIC01 #TrezorSafe7 #SatoshiLabs #OpenSecurity #Transparency #SecureHardware #CryptoSecurity #trezor #TS7 #tropicsquare #secureelement
slush retweeted
With the new @Trezor Safe 7 and the open secure element #TROPIC01 by @tropicsquare, the fun is just taking off. The TROPIC01 is easily extended with a PKCS#11 wrapper, meaning it can easily be turned into a true smart card. It is even efficient enough to be powered by an NFC antenna, meaning we can start to build open smart/banking/credit/identity cards on top of it. We can build HSMs on top of the Safe 7 with a bit of firmware extensions, and we can build decentralized financial services with Trezor-to-Trezor transactions on top of the hardened Bluetooth stack and much more. Such a powerful platform waiting to be awakened.
slush retweeted
The best thing about building something new is that every day sets a new all-time high.
@vexl just crossed 17K users and I could not be more proud!
slush retweeted
๐ก๐ผ๐ ๐๐๐๐ ๐ฎ ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐๐ฎ๐๐ป๐ฐ๐ต: ๐ ๐ฃ๐ฎ๐ฟ๐ฎ๐ฑ๐ถ๐ด๐บ ๐ฆ๐ต๐ถ๐ณ๐ย ๐
@Trezor Safe 7 is here. And at its core is TROPIC01, the first transparent, auditable secure chip integrated in mass-market consumer devices.
This isnโt marketing spin. Itโs a validation of a paradigm shift from security by obscurity to hardware security you can actually verifyโ
.
๐ง๐ฅ๐ข๐ฃ๐๐๐ฌ๐ญ ๐ฒ๐
๐ฝ๐ผ๐๐ฒ๐ ๐๐ต๐ฎ๐ ๐ผ๐๐ต๐ฒ๐ฟ๐ ๐ต๐ถ๐ฑ๐ฒ:
โข Digital design logic (RTL๐ฅ๏ธ)
โข Firmware ๐
โข Detailed documentation๐
โข Attack surfaces and architectureโ ๏ธ
For the first time, independent researchers, not just vendors, can inspect what your Secure Element is doing.
๐ช๐ต๐ ๐ถ๐ ๐บ๐ฎ๐๐๐ฒ๐ฟ๐ย :
In systems that protect identity, data, and money, trust must be earned, not assumed. And verification is the only way to get there.
This isnโt just about crypto anymore. IoT, identity, and edge devices are next.
Transparency isnโt radical, itโs long time overdue๐.
See how #TROPIC01 powers the @Trezor Safe 7 and where verifiable security goes next.
tropicsquare.com/news-and-evโฆ
#TROPIC01 #TropicSquare #TrezorSafe7 #OpenHardware #SecureElement #TransparencyInTech
slush retweeted
In 21 hours ...
On 21st of October ...
Can't wait!
Tomorrow unlocks a new era of crypto security.
Weโre thrilled to finally reveal what weโve been building.
Get ready to experience what radical transparency truly means.
content.trezor.io/trezor-revโฆ
slush retweeted
Freedom tech doesn't wait for permission!
Freedom Store is @vexl's Foundation answer to Appleโs gatekeeping.
Launched at @BTCPrague with other tools that make you more sovereign!
@BullBitcoin_ @vexl @SovranBitcoin @bitkitwallet @MinibitsCash @LNFlash
More BTC Prague 2025 talks just dropped on YouTube.
This batch is all about freedom โ in speech, health, identity, and Bitcoin itself.
Start with @LeaPetras Breaking the Chains โ a talk on how to fight Big Tech censorship in the digital age. ๐งต
slush retweeted
We believe that once you start keeping secrets and limit the flow of information & knowledge, it stalls your innovation and product development.
So โฆ no matter where you read our first holiday blog post ๐ดโฆย what's more important is what you learn from it.
We are answering questions as:
โขIs transparency a guarantee of security?
โขHow does โsecurity through obscurityโ work in real life?
โขWhere does it end?
โขDoes open source mean secure?
That's why we decided to develop TROPIC01, the first secure element based on open architecture and open design.
We are convinced that security through transparency is the better alternative.
Read now: tropicsquare.com/blogs/securโฆ
#TROPIC01 #OpenHardware #SecureByDesign #NoBlackBoxes #RootOfTrust
slush retweeted

vexl ๐@vexl20 Jun 2025
๐จ๐ฟ
Czech RepublicConnected via Czech Republic App StoreAccount-level information, not a live location or per-post device.
On June 20th, Vexl Foundation introduced @FreedomStoreFTW. 2025 won't be like "2025".
slush retweeted

vexl ๐@vexl18 Jun 2025
๐จ๐ฟ
Czech RepublicConnected via Czech Republic App StoreAccount-level information, not a live location or per-post device.
๐จHard to believe now but 41 years ago, Apple told the world that 1984 wouldnโt be like โ1984.โ
Fast forward 41 years. An App Store Dictatorship. Apple didnโt stop Big Brother. Apple became Big Brother. The hypocrisy is staggering...
youtube.com/watch?v=VtvjbmoDโฆ
slush retweeted
Replying to @BTC_for_Freedom
the long but hopefully honest as I can explanation as I see it so far:
The real debate is less technical than it is philosophical in my opinion. To us who want the purpose of Bitcoin as a singular and focused monetary system, it seems like an explicit capitulation to "just put whatever you want in the blockchain, here's an official way to do it."
While it likely wont make a significant difference from a practical standpoint, it feels like crossing an ideological line. There are tons of jpegs being put into the chain, and there are a few, low cost (mostly ineffective) measures that people have been putting into place for mempool policy to attempt to mitigate on their own nodes or block templates.
However, IF those mitigations were the standard are done broadly across the node network (say core implemented them the way they are trying to implement this PR to remove the limit completely), then they actually would have some effect. Yes, its largely a cat and mouse game, but nonetheless it would do something, just like OP_RETURN being set at a strict limit has ensured that 99% of transactions have adhered to that limit.
In addition, node runners who want the option to set this themselves, feel that prioritizing monetary transactions over jpegs is being a good steward. This PR started a pointless battle because it not only sets the default to infinity, but it removes the configuration option completely so a node runner cant change it.
Those in support of removing the limit and configuration option, are saying that because no solution would be full proof, its a waste of time.
There's a worthwhile addition that those who oppose have (imo fairly) noted that some in support have potential conflicts of interest working directly with taproot wizards, invested in NFT and VM tools, or other crypto adjacent persons or projects.
I agree nothing is fully effective and don't believe that "everyone is malicious" here, but standards do matter, and more importantly, how we culturally treat what is a hack and exploit to input arbitrary nonsense into the chain matters. Cat and mouse or no, all of our focus and energy should be toward protecting and engineering Bitcoin to be the best and most secure money. And if we start embracing crypto culture, we will get crypto results.
In other words, "a jack of all trades is a master of none."
There are plenty of arguments on both sides that are being repeated that aren't accurate. These stand out, atm:
- people who want to remove the limit saying inscriptions will use this instead, when they wont because its still more expensive in fees because inscriptions get the witness discount.
- people opposed claiming this will make it harder to run nodes are wrong too, having explicitly unspendable UTXOs is technically superior than big, fake signatures, and the 4mb weight limit is the same regardless of what is happening. (plus, op_return falls under original 1mb still)
My analogy defending my position against:
-- Just because we can make money letting people rent out the courts for parties and concerts, doesn't mean we should. If the courts are exclusively designed and used for protecting people's rights and arbitrating conflict, then we lose a core foundation that "parties and concerts" are entirely downstream of and dependent on. Maybe people still manage to get parties in the courthouse, but how do we treat them culturally regardless of effectiveness at stopping them?
- Put another way, sure I think drugs should be legal, but should we be handing out needles?
My simplest steelman (hopefully accurate) of the support:
-- If filtering is largely futile, then if we just open up the limit to a less costly (for node UTXO set not fees) way to use bitcoin to host arbitrary data, then at least people who want to be good stewards using NFTs or the like, have the option of not creating toxic UTXOs. And if we try to stop them, they are more likely to create private mempools that don't broadcast to the network but pay directly to a miner, which causes information discrepancies with the public network and fee predictions, as well as possible mining centralization concerns if this made out of band fees become popular.



















