United Kingdom
Joined February 2009
Mike retweeted
Replying to @virtualbacon
Correction for Mr. Bacon! 🥓 ❌ ​#QANplatform is QR straight from the genesis block. 🛡️ ​A true #Layer1 blockchain leveraging ML-DSA NIST-certified algorithm, real enterprise adoption is already live on their private chain. 💼⚡ ​Mainnet B4 end of 2026. 🚀 Please, DYOR on it💎
4
23
79
September Milestones: XLINK Goes On-Chain and Deterministic QVM Metering Takes Shape September was a month of deep engineering for QANplatform. Our team turned their attention to the work that will define the production network: moving XLINK signature management on-chain, building a caching layer to speed up QVM executions, advancing our deterministic gas-metering research toward a real pricing model, and hardening the network against the subtle edge cases that only appear under sustained load. This month also brought a major strategic milestone: with the execution-layer rebase complete, our audited quantum-safe stack is ready for the final security-audit phase. Read the full technical recap on our blog (link in replies)🔗👇
15
40
2
112
4,509
[Audit status update] Based on all received feedback, we have finalized the decision on the consensus layer integration for the mainnet stack. After careful consideration, we selected Lighthouse by Sigma Prime. As discussed previously, Lighthouse is the most widely used consensus client and is considered semi-official due to its broad adoption among node operators. This choice best meets the technical and policy requirements of our strategic partners. What happens next: Step 1: We are currently preparing the official Go-Ethereum based execution client to be compatible with the modified Lighthouse consensus client. Step 2: Once these modifications are ready, we will submit the execution client to the auditors, expected by end of next week. Step 3: Once the required Lighthouse modifications are completed, we will also submit the consensus client to the auditor. Just to clarify, the above steps do not alter the mainnet launch timeline, as these processes are fully parallel.
18
47
1
142
4,889
Where has the official telegram channel gone? Has it disappeared for everyone, or just me? Strange goings-on @Tap_Fintech
1
96
What's happened with the telegram channel? Seems to have disappeared. Not even linking from the likes of coin gecko @SaveWithCrypto
1
1
52
Mike retweeted
Replying to @Cointelegraph
@qanplatform community was just talking about this report.
5
14
49
240
My son got a new iPhone 18 pro for his birthday. He also dropped it on day 2, directly onto concrete!! Glad I spent the extra and got him a case that does what it's supposed to do #OutsidewithTorras #Ostandshot
37
$IONQ vient de montrer un truc que presque personne n’explique. Un ordinateur quantique fait des erreurs. Beaucoup. Pour qu’il serve vraiment, il faut les corriger pendant qu’il calcule. Pas après. Pas en pause. Ce « correcteur » s’appelle un décodeur. Jusqu’ici, le risque c’était qu’il soit trop lent ou trop cher : des racks de puces juste pour rattraper les fautes. Là, leurs chercheurs disent avoir un décodeur de bout en bout, en temps réel, pour une machine fault-tolerant à grande échelle. Et il tourne sur un seul processeur classique du commerce. Un CPU normal. Ils ont testé des circuits jusqu’à 408 qubits logiques et plus de 31 millions d’opérations. Dans leurs conditions, le surcoût de temps tombe autour de 0,02 %. Pourquoi ça compte??? Si la correction d’erreur exige une usine de serveurs, le quantique reste un labo. Si elle tient sur un processeur standard, le coût et le rythme deviennent industriels. Ce n’est pas encore la machine de 2028 livrée clé en main. Mais C’est un goulot qui recule. Un des plus durs. thequantuminsider.com/2026/0…
4
9
1
101
5,749
JUST IN: IonQ will install the “first on-premise quantum processor” at Nvidia’s quantum research center in 2027.
9
36
5
381
17,482
DELL'S CTO JUST CALLED QUANTUM "POTENTIALLY A BIGGER DEAL" THAN GENERATIVE AI. John Roese, Dell's global CTO and chief AI officer, on the company's new quantum program, "Generative AI was a big deal. Quantum is potentially a bigger deal because it will build on the shoulders of giants. Once we have viable, cost-effective, at-scale quantum systems, it changes everything." Dell has deployed an HPC cluster inside Diraq's Sydney laboratory, co-located with Diraq's silicon spin qubit processor, to test whether classical servers and a quantum chip can run as one machine with microsecond feedback. Dell's orchestration layer schedules the work and the quantum processor handles the parts classical compute can't. Diraq's CEO put the division of labor plainly: "call classical AI and CPUs for the big number crunching. Then, when there's a specific hard problem, you call the quantum processing unit." Diraq's qubits are modified silicon transistors, built on standard foundry processes, with a path to millions of qubits on a single chip inside one refrigerator that fits in a data center. Dell's business is data centers. Roese's word for it: "democratizing," qubits that ship in racks, not buildings. Next month Diraq installs a machine inside a commercial Equinix data center, the first ever. $DELL $INFQ $IONQ
19
61
12
206
21,960
Mike retweeted
The biggest mistake people make with quantum-resistant blockchains: They think the goal is simply to use post-quantum cryptography. That’s only half the problem. The bigger question is: how easy is it for developers to actually build with it? 🧵
4
7
136
2,915
Post-quantum isn’t a patch you add later! @intel Steve Orrin: 2030/31 is the migration deadline, but the risk is today. If your blockchain still relies only on ECDSA, your data and keys are already on the “harvest” list. Quantum-resistant from genesis isn’t optional, it’s risk management. Block 0 must be protected! bitcoin:native ethereum:native $SOL
Speaking on a recent podcast, Steve Orrin, Intel’s Federal Chief Technologist, warns that the quantum threat is "not a future problem, it's a today problem." "In my personal opinion, I think that from a risk perspective, 2030, 2031 is the right target. If we could do it earlier, we should, because the harvest now, decrypt later threat is already a risk. It’s already happening, and it has been happening. Every encrypted piece of data that’s been pulled off the net and waiting in some large database for when the quantum computer comes online — if you want that data to be protected after that, you need to have started post-quantum encrypting back when you created that data." - Steve Orrin, Intel’s Federal Chief Technologist The takeaway: start securing your data today to keep it safe in the quantum era. For decentralized systems, this means building on a blockchain that is quantum-safe from block 0.
4
6
24
520
Replying to @RapidCalls
You should check @QANplatform qanplatform:native is prelaunch and proved their mindset to the Community. The first Project I ever saw that compensated the whole community after a bridge was hacked. Legit AF and going for the next narratives. Quantum resistance low barriers Enterprise Blockchain #NoGhostChain Check also the team, and the co-founder Silur 😉
1
6
30
July Milestone: Successful completion of the TestNet migration to the official Ethereum execution client Our primary objective this month was clear: migrate the QAN TestNet to the official industry-standard Ethereum execution client while remaining compatible with our previous implementation without compromising our unique quantum-secure features. The engineering team has not only completed the migration to the official Ethereum client but has also proven that QANplatform can operate seamlessly on a standard Ethereum infrastructure while retaining the full power of the QAN Virtual Machine (QVM) and QAN XLINK. Read the full technical deep dive on our blog (link in comments) 🔗👇
17
47
3
124
7,039
It's a frustrating experience to receive an email saying that you tried to deliver a parcel, when in fact I have been at home all morning waiting between the alloted delivery time. @parcelforce .
12
1
9
5
382
Mike retweeted
Replying to @coinbureau
Quantum security is no longer something to watch- it's a requirement. All systems will be looking for solutions. That is a huge market for innovation. @QANplatform has the IP and enterprises have shaped what's required for the future of Blockchain utility.
7
32
188
If you wanted to read one thing today about an incredible #layer1 that is about to launch, then @kevalgala03 just made great use of your time . Don't miss this opportunity to be early! #Quatum #crypto #SOLANA #Avax #ETH #NIST #BLOCKCHAIN #Bitcoin #CLARITY $QAN $BTC
10 reasons @QANplatform is the quantum-resistant L1 worth watching. 1️⃣ Any programming language: QVM opens blockchain development to 20M+ programmers 2️⃣ Quantum-resistant from genesis: CRYSTALS-Dilithium (NIST-approved ML-DSA) built in 3️⃣ QAN XLINK: cross-signer protocol ensures 100% migration path when quantum attacks hit ECDSA 4️⃣ Harvest now, decrypt later: every ECDSA public key exposed onchain today is a future attack vector, QAN eliminates this 5️⃣ Audited core tech: QVM audited by Hacken (2025), XLINK audited, integration audit ongoing 6️⃣ EVM compatible: existing Ethereum DApps, DeFi, NFTs can migrate without rebuilding from scratch 7️⃣ Developer rewards: first L1 that pays developers lifetime royalties when their smart contract code gets reused 8️⃣ 5-minute cloud deployment: deploy QAN blockchain to AWS, Azure, GCP in under 5 minutes 9️⃣ Ethereum rebase: QVM core logic being ported to Ethereum infrastructure (~70% complete) 🔟 $21M mcap, mainnet 2026: audited, testnet live, CTO publicly committed The title insurance story says it better than any whitepaper. A property signed onchain in 2022 with ECDSA could have two mathematically valid owners by 2030. QAN signed its first block assuming ECDSA wouldn't hold. Most chains didn't. $QANX
4
67
10 reasons @QANplatform is the quantum-resistant L1 worth watching. 1️⃣ Any programming language: QVM opens blockchain development to 20M+ programmers 2️⃣ Quantum-resistant from genesis: CRYSTALS-Dilithium (NIST-approved ML-DSA) built in 3️⃣ QAN XLINK: cross-signer protocol ensures 100% migration path when quantum attacks hit ECDSA 4️⃣ Harvest now, decrypt later: every ECDSA public key exposed onchain today is a future attack vector, QAN eliminates this 5️⃣ Audited core tech: QVM audited by Hacken (2025), XLINK audited, integration audit ongoing 6️⃣ EVM compatible: existing Ethereum DApps, DeFi, NFTs can migrate without rebuilding from scratch 7️⃣ Developer rewards: first L1 that pays developers lifetime royalties when their smart contract code gets reused 8️⃣ 5-minute cloud deployment: deploy QAN blockchain to AWS, Azure, GCP in under 5 minutes 9️⃣ Ethereum rebase: QVM core logic being ported to Ethereum infrastructure (~70% complete) 🔟 $21M mcap, mainnet 2026: audited, testnet live, CTO publicly committed The title insurance story says it better than any whitepaper. A property signed onchain in 2022 with ECDSA could have two mathematically valid owners by 2030. QAN signed its first block assuming ECDSA wouldn't hold. Most chains didn't. $QANX
11
51
2
194
2,975
Replying to @QANplatform
A good reminder that infrastructure security extends beyond where assets are stored. The pathways data takes through a network can be just as important as the endpoints themselves.
2
3
19
229
Quantum isn’t waiting for 2030. Diamond NV‑center roadmaps point to 10,000+ qubits at room temperature, no giant cryo‑fridges ect. If a blockchain still relies on pre‑quantum signatures, it’s betting on math that won’t hold. @QANplatform is ahead of the curve. $BTC $ETH $SOL
In 2022, a signature was proof. In 2030, it's a question mark. It is a Wednesday morning in 2030. Maria underwrites title insurance for real estate transactions. Her firm started backing blockchain-recorded property titles in 2021, chasing the story every county recorder loved: no more lost deeds, no more forged paperwork, a permanent chain of ownership nobody could dispute. She is reviewing a claim on a commercial property in Ohio. The current owner bought it in 2022. The title transfer was signed on-chain, ECDSA, standard for the time. Nothing unusual. The chain of custody traces back nine sales, all the way to 1987, then digitized and anchored in 2021 as a single cryptographic root. The claim isn't about a lien anyone missed. It's about a signature. A forensic cryptographer flagged the 2022 transfer. The public key was exposed the moment the transaction posted. Someone with enough quantum compute could now produce a second signature for the same private key, mathematically valid, pointing to a different buyer. Not a hack. Not fraud in the traditional sense. A second, equally provable version of the truth. Maria's entire underwriting model assumes one signature means one fact. It was never built for a world with two. She adds a line to the claim file: "Pre-2024 on-chain signature. Cryptographic non-repudiation no longer assured. Escalate to legal." She has three more files on her desk with the same date range. Most chains signed their first block assuming ECDSA would hold for its lifetime. We signed ours assuming it wouldn't. Title insurers underwriting on-chain property records are now finding out which assumption their claims file depends on.
6
18
1
48
617