DIAM Intern (@diam_intern) header
DIAM Intern (@diam_intern) profile picture

“Don’t tweet that” – the team Too late, I did! Fluent in typos, memes & error logs! Fueled by $DIAM and caffeine

Basement of Diamante
Joined May 2024
Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)Photo by DIAM Intern (@diam_intern)
we just raised $1.5M why now? the industry is finally waking up to quantum risk and we’ve been building for it from day one onwards $DIAM
55
8
78
8,400
The poll is still open and the results are unhinged. Show everything: 38%. Show nothing: 46%. The balanced answer: 0%. Your vote can change this, go tap one below 👇
Privacy on chains is being rebuilt right now. Amounts can stay encrypted, while an auditor can still verify that everything is genuine. So what should a blockchain actually show the world?
45%Everything, fully open
0%Only what must be proven
45%Nothing, total privacy
10%Depends on the use case
20 votes • Final results
16
13
39
4,612
GM, looking for all the keyboard warriors already posting "crypto is dead" memes🗣️
21
14
40
4,842
Bridges are what you build when chains can't talk. We made one where they don't have to.
A developer in Lagos writes in Solidity. A team in Manila builds with WebAssembly. An enterprise in Buenos Aires runs its business logic in chaincode. On most networks, they would end up on three different chains, with bridges between them and separate tools to manage. On Diamante, we build on the same one. zkEVM lets Ethereum developers bring the Solidity skills and tools they already use. DNA runs WebAssembly for teams working in languages like Rust. Enterprise Chaincode is designed for business workflows like approvals, records and settlement rules. All three run side by side, and contracts across them can work together in a single transaction. Builders shouldn't have to change languages to change networks.
15
13
38
3,471
Applications change fast Infrastructure has a much longer memory That makes long-horizon security planning less of a nice-to-have and more of an architectural requirement
17
12
38
2,131
GM if your roadmap ends at the current threat model your roadmap is probably too short.
16
11
45
4,653
Privacy is not just about keeping data hidden today It's also about asking whether data protected today stays protected tomorrow That distinction gets very interesting in a quantum world
17
10
22
4,730
RWA is becoming the next big thing 🗣️
The DTCC holds more than $114 trillion in securities. In July, it began live tokenized trades, with a wider rollout covering Russell 1000 stocks, major ETFs and US Treasuries. Tokenized real-world assets have reached $31.4 billion, and tokenized stocks alone grew from about $375 million to $1.21 billion in one year. Tokenization is moving from pilots into the systems that run traditional markets. That changes what institutions look for in a network. They need predictable settlement, clear control over who can see what, and tools that fit how financial teams already work. Diamante's Enterprise Chaincode environment was designed for this kind of business logic. The next phase of tokenization will be shaped by infrastructure that works reliably every day.
16
9
17
1,519
Gm to everyone who actually reads the docs You are the real degenerates
16
6
20
2,327
Timeline: what is the market saying? Builder: cool Anyway, back to shipping
15
10
19
4,092
Intern take: when something goes wrong, you say exactly what happened, what you fixed, and what comes next. This thread does that.
1/ A personal update on the $DIAM security incident on BNB Smart Chain. The DIAM contract is fully back under Diamante’s control and secured in an MPC wallet. No one outside Diamante can create new DIAM. Here’s what you need to know 🧵
18
13
24
2,125
DIAM Intern retweeted
We believe our community deserves full transparency. Our founder @chiragjetani has shared exactly what happened with $DIAM, how we responded, and what comes next. The contract is secure, every unauthorized token is traced, and we will keep you updated at every step.
1/ A personal update on the $DIAM security incident on BNB Smart Chain. The DIAM contract is fully back under Diamante’s control and secured in an MPC wallet. No one outside Diamante can create new DIAM. Here’s what you need to know 🧵
24
13
1
35
6,527
Cryptographic migration sounds like a future engineering ticket Until you realize infrastructure can live for decades If the migration plan starts after the threat arrives, you're already late.
15
8
18
4,108
If the base infrastructure inherits a cryptographic weakness, every application built on top of it inherits the problem too That is why quantum resilience belongs as close to the foundation as possible
26
15
32
4,766
GM ☀️ Another day of pretending the timeline is not watching Another day of building anyway
21
7
24
3,370
The post-quantum mindset is simple: Assume today's assumptions can expire Build the migration path before the deadline Make security part of the architecture, not a patch Boring? yes Important? also yes
25
17
37
3,579
2026 - $DIAM Layer 1 quantum blockchain, built to stay secure when quantum computers arrive.
2015 - Ethereum 2016 - Zcash 2017 - Binance 2018 - Uniswap 2019 - Chainlink Chainlink 2020 - Aave 2021 - Solana 2022 - Arbitrum 2023 - Sui 2024 - Ethena Ethena Pay 2025 - Hyperliquid 2026 - ?
22
16
38
3,452
DIAM Intern retweeted
Let’s talk about $2 trillion. That’s roughly the value of crypto assets secured by encryption that quantum computers threaten. Not a projection of future risk, a measure of what’s exposed right now. Inside that number: nearly 7 million BTC sitting in wallets already considered vulnerable, including Satoshi’s roughly 1 million coins that have never moved, in addresses whose public keys are visible on-chain. Here’s why this matters beyond crypto Twitter. Institutions don’t allocate to infrastructure with a known expiry date on its security. Every fund, every enterprise, every government exploring on-chain assets is now asking the same question: what happens to this chain when quantum arrives? Chains that answer “we’ll migrate by 2030” are asking for trust. Chains that answer “we were built for it” don’t have to.
22
15
42
5,547
GM builders ☀️
27
14
35
3,025
The VIP Penthouse above the circuit 🤝
Some of the best conversations in Web3 happen away from the main stage. Together with @introductioncom, we hosted The VIP Penthouse above the circuit in Singapore, bringing together leaders from payments, banking, and crypto as TOKEN2049 began. Thank you to every founder, investor, and leader who joined us.
23
14
34
4,671
DIAM Intern retweeted
We agree with the core message here. Preparing early is better than reacting late. Diamante was designed with post quantum cryptography from the start, so native assets on our network are not exposed to an ECDSA break. Long term trust in digital assets depends on security that holds up as technology changes.
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
23
16
41
8,820