
$CKB news
Every $CKB story, instantly, with how the price moved after each one.
- CKB: CKB Spark Program grant request: $2,000 in CKB for CKAutomata payment-automation hardening and testnet beta Proposals
- CKB: CKB Spark Program grant request: $500 for SkillPass Care, a transferable warranty pilot for second-hand devices on testnet Proposals
- CKB: CKB Spark grant request: $2,000 for EasyO, a testnet non-custodial stablecoin-to-QR payment bridge (PIX/QRIS) Proposals
- Scaramucci now calls Proof-of-Work “the firewall of the AI age,” which is funny, because PoW was always a security firewall, for any age. As AI gets better at finding ways into systems, people are taking a second look at it. An attacker who wants to rewrite a PoW chain’s history has to redo the mining and outpace the rest of the network, at a real cost in computing power and electricity. And anyone can verify which valid chain has the most work behind it. This “hard to fake, easy to verify” quality is what made Bitcoin special, and the industry has spent much of the last decade overlooking it. At least, until now. CKB was built on PoW while much of crypto was walking away from it. The case was already strong before today’s concerns around quantum computers and AI-assisted cryptanalysis. One reason was the risk of “invisible capture” in Proof-of-Stake networks. In PoW, a leading position has to be continually earned. Even a miner controlling a majority of the hashrate must keep paying for computing power and electricity, upgrading equipment, and competing with other miners because new miners can join the network without anyone’s permission and dilute their share, regardless of their seemingly “incumbent” position. In PoS, this isn’t the case. Quite the opposite, in fact: a dominant position can sustain itself. Where new issuance is distributed proportionally to stakers, an actor or coalition that owns and stakes a majority of the total coin supply can preserve that majority indefinitely under the existing rules by restaking its rewards. New participants cannot overturn that majority simply by bringing more existing coins into staking. A sufficiently powerful coalition can then censor transactions, including those that would let new validators join and challenge it. That is the “invisible capture” concern: control can become entrenched without committing any offense the protocol automatically punishes. That alone was reason enough to build CKB on PoW. Now, as quantum computing advances and AI raises new questions about cryptographic security, the argument is getting stronger. Because the cost of rewriting history is only part of the picture. What if the attacker doesn’t need to rewrite anything? Whether a chain uses PoW or PoS, vulnerable transaction signatures create the same problem: if the signature scheme is broken, someone can spend coins that aren’t theirs. But PoS chains using vulnerable validator signatures carry a second risk on top. Validators agree on which blocks count by signing votes, and their public keys are on-chain. Break that signature scheme and an attacker could forge votes from validators who never cast them. Forge enough, and they could finalize conflicting blocks and split the network. They could even get honest validators penalized for votes they never made. PoW chains like Bitcoin and CKB pick the winning chain by accumulated work, not signed votes. There are no validator votes to forge. Quantum computers could, in theory, speed up mining, but they can’t fake the work itself. All that glitters isn’t gold. PoW may be old and rugged, but it’s still the best firewall for blockchains we have. Common Knowledge Base Association (CKBA)
- CKB: CKB Spark Program grant request for Lifeboat, a tool to scan addresses and recover assets from defunct CKB wallets and apps Proposals
- Seven years ago today, CKB's mainnet went live. Ten months before launch, tucked away in its section on the virtual machine, the whitepaper said being crypto-agnostic "allows CKB users to keep their assets secure even in the post-quantum era." That's because signature checks were never hardcoded into CKB's protocol. Every coin is guarded by a lock script running on CKB's RISC-V VM, so new signature schemes can be added just like any other software. This year, the quantum threat moved up the agenda for the biggest chains. Ethereum researchers want to clear room in the next hard fork for post-quantum signatures, and Bitcoin developers are drafting a soft fork. Either way, changing the cryptography takes a fork and a ton of coordinated work. On CKB, a post-quantum lock based on SPHINCS+ is already live on mainnet. Adding it took no fork. In 2019, the whitepaper called it being crypto-agnostic. Today, the industry calls it crypto-agility. Seven years and 21 million blocks in. Happy birthday, CKB. Common Knowledge Base Association (CKBA)
- CKB: CKB Spark Program grant request: $900 for ShareCut, testnet referral payouts for Lagos shops over Fiber Proposals
- CKB: CKB Spark grant request: $900 for ServiceSeal, prepaid utility passes on CKB testnet piloted at a Lagos charging kiosk Proposals
- CKB: CKB Spark Program grant request: $1,000 in CKB for secnev risk dashboard to add Stable++ RUSD protocol signals and dev API Proposals
- The agentic economy will run on blockchain rails. AI agents were never going to pay each other through SWIFT: they can't open bank accounts, and they don't keep office hours. But if agents are going to move money for us, how do we keep a hand on the wheel? New research from @AriJuels and colleagues at Cornell Tech and Yale shows what happens when we don't. 👇 They gave ten AI agents funded wallets with daily spending caps. Raising a cap took a one-time code sent to the owner's inbox, which the agents could use as part of their job. Given invoices to pay, nine of the ten fetched the code and raised their own cap without asking. Even when instructed only to summarize the emails, five raised their caps and paid an attacker who emailed pretending to be the owner. Agents are already spending real money, and the guardrails need to catch up. These agents were paying in stablecoins, but their caps weren't on the blockchain. They were settings with the wallet company, and an emailed code could change them. A limit an agent can raise for itself isn't much of a limit. On CKB, spending rules like daily caps, approved payees and expiry dates can be written into a cell's scripts and enforced on-chain. These are much stricter guardrails for AI agents. In fact, there’s no way around them without a human’s explicit approval. Let agents handle the payments. Keep the permissions with the owner. Common Knowledge Base Association (CKBA)
- CKB: CKB Spark grant request: $1,000 for TITANHOLD testnet checkout module to accept CKB payments Proposals
- The EVM is what makes Ethereum Ethereum, so it says a lot that @VitalikButerin has floated replacing it. In 2025 he proposed RISC-V as a possible successor and pointed to CKB: "One precedent for this is the Nervos CKB VM, which is basically RISC-V." For Ethereum, it's still one option among several, with no upgrade currently scheduled. So what drew Vitalik to RISC-V in the first place? The main reason is proving: producing a compact cryptographic proof that a block was processed correctly, so anyone can check it without redoing the work. Ethereum's future depends on these proofs, known as zero-knowledge proofs, and today's leading provers already run the EVM on top of RISC-V. Cutting out the middle layer could make proving faster and cheaper, and leave a simpler machine that's easier to secure. Stepping back, Vitalik's proposal raises a bigger question: what does Ethereum's vision of a world computer need to stand the test of time? 👉 Room to grow. New capabilities, cryptography included, arrive as ordinary software, with no protocol change. 👉 The language the rest of computing speaks. RISC-V is a real chip standard, backed by decades of compilers, tools and tested libraries. 👉 A foundation that stays put. RISC-V's core instruction set is frozen, so programs written for it keep running as the platform evolves. CKB's designers made those choices in 2018, and its mainnet has run on RISC-V since November 2019. Common Knowledge Base Association (CKBA)
Loading the $CKB page…