Don

@LusoCryptoLabs has just open-sourced the Liquid Cells protocol on #NervosNetwork #CKB. Read more here: talk.nervos.org/t/liquid-cells… Check out the repo and leave your feedback: github.com/LusoCryptoLabs…

Over the past week, two negative developments hit the ecosystem. If you follow the project closely, you’re already aware: the USDI stablecoin is being discontinued, and ViaBTC announced that it will wind down its CKB mining pool. These are real setbacks, and we are not here to minimize them. Every bear market in crypto has been difficult, but this one feels particularly brutal. Across the industry, almost every important metric has been moving in the wrong direction. -User activity is down. -The talent pool is shrinking. -Venture capital has dried up significantly. -Project shutdowns are becoming more common. And on top of everything, the industry continues to get hit by exploits, with new AI tools like Mythos 5 making the attack surface even harder to manage. Building in this industry has never been easy, especially through prolonged market cycles. Despite the IPN team’s best efforts, over the last 2 years USDI unfortunately did not reach the scale needed to sustain operations, and ViaBTC has determined that operating a CKB mining pool doesn’t fit with the economics of their business. These events are setbacks for the ecosystem, but they are not a referendum on CKB. We have always taken a low-time-preference approach, we are well equipped to keep building through difficult cycles, and our conviction in CKB remains unchanged. Bear markets are brutal, but they have also historically been the periods when the most important infrastructure work gets done. And that is exactly what we are seeing. Over the last six months, community developer activity around CKB has increased substantially. The CKBuilders program under @NervosCatalyst has grown to over 60 developers at different stages of learning, practicing, and building on CKB. talk.nervos.org is full of posts about use cases for Fiber and discussions about improving its utility. Through CKBA, communication and ecosystem coordination efforts are ramping up. In short: we are still here, still building, and still committed to CKB’s long-term mission. Onward 👷

Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8141 ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-st… firefly.social/post/farcaster…

@LCDS_2 This is horrific. History repeats itself. How can humans hurt children like this? I will never understand