cryptographic abstraction is the right buzzword🫡
when you hear industry leaders talking about quantum computing,
it is because bad players are leveraging it to threaten the security of so many blockchain networks.
but @NervosNetwork already prepared from day 1.
CKB is built with cryptographic abstraction which makes it possible to secure and replace security models without breaking the CKB fundamental rules.
Common Knowledge Brother retweeted
Finally squeezed the esp32s3 HMI into the Blackbox prototype, battling hardware feels nostalgic in the AI era. Loving the increased viewing angle. The new MCU let's me run a $CKB light client on-board with headroom to incorporate stuff like the NFC reader thats also now inside.
nice.. there are now 2 chains that support SHRINCS 👏👏
In case you're wondering about the state of quantum safety on Chia, Sol just one-shotted supporting SHRINCS in chialisp. Will work on chain right this minute and only took a few minutes github.com/bramcohen/chialis…
if you've ever wondered how SPHINCS+ works..
great read👇
you're thinking too small. i don't need terabytes of random bits. i need a seed and a complete rejection of elliptic curves.
from this seed i grow an astronomical number of one-time secrets. each secret becomes a hash chain. you can walk forward through the chain but never backward. i arrange these chains into winternitz one-time signatures, and their public keys become leaves of merkle trees. those trees become leaves of larger trees. trees all the way up. a hypertree.
but first, at the bottom, i plant the FOREST OF RANDOM SUBSETS. FORS. the message is reduced to a string of ones and zeros. groups of bits select leaves from independent merkle trees. i reveal the corresponding secrets and the neighboring hashes, and you reconstruct the roots. the roots become a single hash. this is the message's signature, born from the forest.
now i sign that hash with a winternitz key. i prove the key belongs to a merkle tree by revealing its authentication path. i sign that tree's root with another key from the tree above. and again. and again. we ascend through layers of hash chains and sibling nodes until the entire structure collapses into ONE ROOT.
32 bytes. that's my public key. the entire forest is committed to those 256 bits.
i don't store the forest. i don't even remember which leaves i've used. the forest is deterministically regenerated from the seed whenever i need it. the message itself tells me where to go.
there are no elliptic curves here. no discrete logarithms. no hidden algebraic relationship waiting for a mathematician to invert. only preimages, hashes, and an unfathomable number of ones and zeros arranged into trees whose branches authenticate each other.
you can have my elliptic curves. you can have my RSA. but you cannot have the forest.
the forest is stateless. the forest remembers nothing. the forest verifies everything.
don't settle for the hype being pushed on you from on high
CKB has been steps ahead for the better part of a decade, it's only a matter of time.
Decentralization is a spectrum, while P2P is a paradigm shift. You're too smart to settle.
RUN CKB
Rob (@robbieklages) says @arc leapfrogged the blockchains before it, the same way each AI model leapfrogs the last.
"There's been so many blockchains that came before, and all of that is a learning moment."
"Arc has been able to leapfrog all of them, the same way AI models leapfrog one another."
"It truly feels that Arc is a next-generation blockchain, built with the benefit of everything the industry learned before it."
Common Knowledge Brother retweeted
@VitalikButerin going back to UTXO
@hasufl looking at POW elegance again
We gonna make it
Loving more this bear market now
Common Knowledge Brother retweeted
1/ Ethereum's state grows far faster than it churns. Most of it goes dormant and never gets used again, while real activity sits on a tiny set of active applications.
Here's a deep dive into what 10 years of mainnet access data shows about how Ethereum's state is actually used. 🧵👇
Common Knowledge Brother retweeted
This is why **crypto agility** is super important for blockchains.
It refers to "the ability to replace and adapt cryptographic algorithms for protocols, applications, software, hardware, and infrastructures without interrupting the flow of a running system to achieve resiliency."
It's not a buzzword. It's a design imperative that @NIST keeps urging everyone to adopt.
However, we don't see anyone else in the crypto industry approaching the threat of quantum computing with this in mind.
CKB is the **only** crypto agile blockchain in existence.
And it wasn't purpose-built for this. It's simply one of the features of its low-level flexible architecture.
A bold design that is now paying dividends.
Follow us to learn more about how CKB solved quantum resistance.
Dan Boneh suggests NIST's PQ DSA standards came out too soon. his take: if NIST had waited a couple years, ML-DSA signature sizes could be 1/3 of what they are today.
It is a critical trade-off on size and timing for post-quantum crypto deployment. That's why many systems don't realize that they will have to re-architect more than they think to handle larger key sizes. But waiting is also a gamble, and if you're doing anything in government, you can't wait.
Hats off to the cryptographers/product folks having to handle this!
the idea that you can upgrade a blockchain without forking it will be as transformational as smart contracts were a decade ago
Are you tired of endless upgrade discussions about hard forks?
Are you interested in playing with the latest advances in post-quantum cryptography or zk proofs?
Check this out to learn more about CKB & unleashing maximum flexibility with RISC-V👇
nervos.org/knowledge-base/ck…
Common Knowledge Brother retweeted
hi there, Trezor platform is open-source and everyone is welcomed to contribute. We’re starting by building the CKB implementation ourselves and aiming to integrate it into the ecosystem from there.
Common Knowledge Brother retweeted
Tadge Dryja, the co-inventor of the Lightning Network, just dropped an update on Utreexo, one of the most underappreciated scaling projects in bitcoin.
The problem is straightforward. Every bitcoin node that wants to validate transactions has to store the entire UTXO set, every unspent output on the network. Right now that's 11GB and growing. As more transactions hit the chain, as inscriptions and other data-heavy outputs pile up, every node operator has to store all of it. The UTXO set doesn't get pruned like old blocks can. It just grows.
Utreexo eliminates the entire UTXO set from your node. Instead of storing 11GB of data, a Utreexo node stores less than 1KB of hashes and still fully verifies every transaction. It's not a light client. It's not trusting anyone else. It's full validation with radically less storage.
The tradeoff has always been bandwidth. Utreexo nodes need to download extra proof data to verify transactions without storing the full set. Until recently, syncing the blockchain with Utreexo took 2-3x the data download of a normal node, pushing into terabytes. That problem is now being solved, new aggregator techniques from SwiftSync have eliminated the extra download overhead. The implementation is still being finalized, but the hard part appears to be behind them.
Two things worth noting:
First, Utreexo is quantum safe. The accumulator and aggregator are built entirely on hash functions, not elliptic curve cryptography. Whatever quantum computing does to bitcoin's signature scheme, it won't touch Utreexo. At a time when the quantum conversation is heating up, that's a meaningful design advantage.
Second, Utreexo directly addresses the tension around "spam" on bitcoin. Inscriptions, BRC-20 tokens, and other data-heavy outputs bloat the UTXO set that every node has to carry. Pruning helps with old block data but doesn't touch the UTXO set. Utreexo makes the entire debate irrelevant, if your node doesn't store the UTXO set at all, the
size of it doesn't matter.
New releases are out for both utreexod (BTCD-based) and Floresta (rust-based, built with rust-bitcoin). Both are in testing mode, not ready for real funds yet, but ready for developers and node operators to try.
This is the kind of quiet, foundational work that actually scales bitcoin at L1. No token. No VC round. No press tour. Just better engineering.
