CryptoMochi (peacewise)

#Bitcoin Discord:peacewise#6158

[CryptoMochi (peacewise) @CryptoMochi]

@outerlumen Sending you so much strength and good vibes. You got this 💪

[CryptoMochi (peacewise) @CryptoMochi]

@voidvexa @TheHashmasks Welcome!

[CryptoMochi (peacewise) @CryptoMochi]

@artguy_eth @TheHashmasks This is a special piece

[CryptoMochi (peacewise) @CryptoMochi]

@TheHashmasks The real winner…

[CryptoMochi (peacewise) @CryptoMochi]

@voidvexa @TheHashmasks A few from my vault. I like clean backgrounds

[CryptoMochi (peacewise) @CryptoMochi]

@TheHashmasks It’s like picking your favorite child

[Hashmasks @TheHashmasks]

The mask escaped the JPEG.
Somewhere in Mexico

[Hashmasks @TheHashmasks]

Before the world knew what an NFT was, Hashmasks were on the walls of Art Basel.

One of the first NFT projects ever shown at the most prestigious art fair in the US. 2021.

The masks were always art. The market just hadn't figured that out yet.

[TokenWorks™ @token_works]

5000/10000 NFTs have been created so far, each with their accompanying ERC20 token.

Post yours below.

[Hashmasks @TheHashmasks]

We bought a Hashmask. You name it.

Reply to this post with your name for the mask + #NameThisMask. That's it.

The mask: Hashmasks #16337
https://t.co/dKaUhE54fq
Currently nameless. Be the first to name it.

🏆 Prize
This Hashmask, named on chain with the winning entry and transferred to the winner.

📅 Timeline (UTC)
- Replies close: Sunday May 17th, 23:59
- Shortlist published in Discord: Monday May 18th
- Voting in Discord: Monday May 18th → Wednesday May 20th
- Winner announced: Thursday May 21st

Shortlist criteria
- Fits the mask (traits, vibe, look)
- Memorable
- Lore potential

🔥 The naming itself
Once the winning name is picked, the team burns 1,830 NCT to write it on chain forever. That's how every Hashmask gets named.

Discord: https://t.co/5ezGc9KeJc

[vangoya @vangoyaa]

https://t.co/d8qUTggU46

[CryptoMochi (peacewise) @CryptoMochi]

@0xKiwi_ @cryptopunks @miladymaker @ForgottenRunes @MeebitsNFTs @TheHashmasks @mooncatrescue @waifusion @uwucrewnft @killergfnft @NFTX_ This is very valuable. Thank you!

[CryptoMochi (peacewise) @CryptoMochi]

Ok, let’s do it

Return to Monke

[Justin Drake @drakefjustin]

Today is a monumentous day for quantum computing and cryptography. Two breakthrough papers just landed (links in next tweet). Both papers improve Shor's algorithm, infamous for cracking RSA and elliptic curve cryptography. The two results compound, optimising separate layers of the quantum stack. The results are shocking. I expect a narrative shift and a further R&D boost toward post-quantum cryptography.

The first paper is by Google Quantum AI. They tackle the (logical) Shor algorithm, tailoring it to crack Bitcoin and Ethereum signatures. The algorithm runs on ~1K logical qubits for the 256-bit elliptic curve secp256k1. Due to the low circuit depth, a fast superconducting computer would recover private keys in minutes. I'm grateful to have joined as a late paper co-author, in large part for the chance to interact with experts and the alpha gleaned from internal discussions.

The second paper is by a stealthy startup called Oratomic, with ex-Google and prominent Caltech faculty. Their starting point is Google's improvements to the logical quantum circuit. They then apply improvements at the physical layer, with tricks specific to neutral atom quantum computers. The result estimates that 26,000 atomic qubits are sufficient to break 256-bit elliptic curve signatures. This would be roughly a 40x improvement in physical qubit count over previous state-of-the-art. On the flip side, a single Shor run would take ~10 days due to the relatively slow speed of neutral atoms.

Below are my key takeaways. As a disclaimer, I am not a quantum expert. Time is needed for the results to be properly vetted. Based on my interactions with the team, I have faith the Google Quantum AI results are conservative. The Oratomic paper is much harder for me to assess, especially because of the use of more exotic qLDPC codes. I will take it with a grain of salt until the dust settles.

→ q-day: My confidence in q-day by 2032 has shot up significantly. IMO there's at least a 10% chance that by 2032 a quantum computer recovers a secp256k1 ECDSA private key from an exposed public key. While a cryptographically-relevant quantum computer (CRQC) before 2030 still feels unlikely, now is undoubtedly the time to start preparing.
→ censorship: The Google paper uses a zero-knowledge (ZK) proof to demonstrate the algorithm's existence without leaking actual optimisations. From now on, assume state-of-the-art algorithms will be censored. There may be self-censorship for moral or commercial reasons, or because of government pressure. A blackout in academic publications would be a tell-tale sign.
→ cracking time: A superconducting quantum computer, the type Google is building, could crack keys in minutes. This is because the optimised quantum circuit is just 100M Toffoli gates, which is surprisingly shallow. (Toffoli gates are hard because they require production of so-called "magic states".) Toffoli gates would consume ~10 microseconds on a superconducting platform, totalling ~1,000 sec of Shor runtime.
→ latency optimisations: Two latency optimisations bring key cracking time to single-digit minutes. The first parallelises computation across quantum devices. The second involves feeding the pubkey to the quantum computer mid-flight, after a generic setup phase.
→ fast- and slow-clock: At first approximation there are two families of quantum computers. The fast-clock flavour, which includes superconducting and photonic architectures, runs at roughly 100 kHz. The slow-clock flavour, which includes trapped ion and neutral atom architectures, runs roughly 1,000x slower (~100 Hz, or ~1 week to crack a single key).
→ qubit count: The size-optimised variant of the algorithm runs on 1,200 logical qubits. On a superconducting computer with surface code error correction that's roughly 500K physical qubits, a 400:1 physical-to-logical ratio. The surface code is conservative, assuming only four-way nearest-neighbour grid connectivity. It was demonstrated last year by Google on a real quantum computer.
→ future gains: Low-hanging fruit is still being picked, with at least one of the Google optimisations resulting from a surprisingly simple observation. Interestingly, AI was not (yet!) tasked to find optimisations. This was also the first time authors such as Craig Gidney attacked elliptic curves (as opposed to RSA). Shor logical qubit count could plausibly go under 1K soonish.
→ error correction: The physical-to-logical ratio for superconducting computers could go under 100:1. For superconducting computers that would be mean ~100K physical qubits for a CRQC, two orders of magnitude away from state of the art. Neutral atoms quantum computers are amenable to error correcting codes other than the surface code. While much slower to run, they can bring down the physical to logical qubit ratio closer to 10:1.
→ Bitcoin PoW: Commercially-viable Bitcoin PoW via Grover's algorithm is not happening any time soon. We're talking decades, possibly centuries away. This observation should help focus the discussion on ECDSA and Schnorr. (Side note: as unofficial Bitcoin security researcher, I still believe Bitcoin PoW is cooked due to the dwindling security budget.)
→ team quality: The folks at Google Quantum AI are the real deal. Craig Gidney (@CraigGidney) is arguably the world's top quantum circuit optimisooor. Just last year he squeezed 10x out of Shor for RSA, bringing the physical qubit count down from 10M to 1M. Special thanks to the Google team for patiently answering all my newb questions with detailed, fact-based answers. I was expecting some hype, but found none.

[CryptoMochi (peacewise) @CryptoMochi]

@oliviscusAI @jgarzik That’s not good

[Lyn Alden @LynAldenContact]

The 1,700 comments to this post are an absolute goldmine, btw.

[Lyn Alden @LynAldenContact]

My new sci fi thriller, The Stolguard Incident, is now available!

Been working on this for a while. Enjoy. :)
https://t.co/GUyOAhs9D7

[CryptoMochi (peacewise) @CryptoMochi]

@LynAldenContact Wow! Congrats! I didn’t know this was coming. Looking forward to it

[CryptoMochi (peacewise) @CryptoMochi]

@steipete @OpenAI @openclaw Congrats… but it’s sad. Don’t forget Sam is another Zuck

[CryptoMochi (peacewise) @CryptoMochi]

BTFD