←
Nervos.bit6,548 posts
Nervos.bit avatar

Nervos.bit

@NervosNetwork

CKB Community account #PoW #UTXO ✨#Web5 #RISCV *none of the posts on this page are endorsed or financial advice*

◷ Joined May 2018▧ 1,901 Photos and videos
Nervos.bit avatar
Nervos.bit@NervosNetwork·Sep 29

It's crypto-agility.

One of the most interesting parts of Ethereum’s post-quantum roadmap isn’t the specific PQ signature schemes it’s researching. It’s crypto-agility. Today, ordinary Ethereum accounts are tied to ECDSA/secp256k1. Ethereum’s proposed Frame Transactions (EIP-8141) would change that by making authentication programmable at the account level. In simple terms, Ethereum would stop mandating a single signature scheme for ordinary accounts and instead let accounts define their own verification logic. With Frame Transactions, a user could migrate from ECDSA to a post-quantum signature scheme, and later from that scheme to another one, without Ethereum needing a hard fork every time the cryptography changes. This is what crypto-agility is all about, and what we’ve been raving about for some time now. If a PQ scheme is weakened, broken, or simply superseded, you want to be able to replace it without redesigning the protocol. What Ethereum is trying to introduce at the account layer is conceptually very similar to something CKB already gets from its architecture. On CKB, ownership isn’t hardcoded to one signature algorithm. Instead, Cells are protected by Lock Scripts: verification programs executed by the RISC-V-based CKB-VM. A Lock Script can verify secp256k1 or SPHINCS+/SLH-DSA today, or some entirely different signature scheme introduced in the future. The base layer doesn’t need to be redesigned around each new scheme. It simply executes the verification program. It’s very cool to see a leading chain like Ethereum converging on the same conclusion CKB arrived at seven years ago: Blockchains shouldn’t be built around the assumption that today’s cryptography will still be tomorrow’s cryptography.

Common Knowledge Base Association (CKBA) avatar
⟳ Nervos.bit retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Nov 15

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.

Post attachment
Common Knowledge Base Association (CKBA) avatar
⟳ Nervos.bit retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Nov 17

iCKB just got a lot easier to use. If you know Lido's stETH, iCKB is the same idea for the NervosDAO: deposit CKB, get a token back, and stay liquid instead of waiting out the DAO's withdrawal cycle. Phroi has rebuilt the whole stack, the DApp, SDK and bot, on CCC, a CKB developer toolkit that also connects apps to many kinds of wallets. It replaces libraries that are no longer actively maintained. The contracts underneath stay the same, and Phroi has tested them extensively against the protocol's rules. What's new for users: 👉 The new DApp works with any wallet CCC supports, from JoyID and UTXO Global to MetaMask, UniSat and Nostr wallets. 👉 A quote before you connect, and a plain-words preview of the real transaction before you sign. 👉 Convert your full balance. The old DApp kept 600 CKB back from every conversion. 👉 Withdrawals should get faster: the pool's DAO deposits are now staggered, so some are always close to unlocking. For builders, the new iCKB SDK is one package whose only dependency is CCC. Link to the full write-up in first reply 👇

Post attachment
Common Knowledge Base Association (CKBA) avatar
⟳ Nervos.bit retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Nov 14

Alive24, a developer in the CKB community, opened a CryptoMondays London talk with a promise: by the end, you’d know enough about quantum computing to explain it to friends and family “and sound like you’ve done your homework.” The talk starts with Schrödinger’s cat, which is alive and dead at once until someone opens the box. A qubit works a bit like that: an ordinary bit is a zero or a one, but a qubit can be both until it’s measured. Link enough qubits together and you get a quantum computer, which could crack certain math problems that ordinary computers can’t. That includes the problem behind the signatures that make sure only you can spend your crypto. New ways to sign transactions that quantum computers aren’t expected to break already exist. The hard part is getting a blockchain to make the switch, because “there’s no CEO to sign off an upgrade.” On CKB, no network upgrade is needed. A new signature method can be added as software, and holders move when they choose. We’ve written up the full talk 👇 nervos.org/knowledge-base/wi…

Post attachment
Nervape 🦍🦴 avatar
⟳ Nervos.bit retweeted
Nervape 🦍🦴@Nervapes·Nov 15

Nervape at DesignerCon - Day 2 Highlights 🎰 Nervape Spin to Win machine (thanks to @limitbreakcstms) ⛺️ Nervape CAMP ♠️ Nervape x Chao Sui Poker 🦍 Analogue series Last Day is here. Sun Nov. 15 📍 Booth 2020 The Expo at World Market Center, Las Vegas dcon.eventround.com/events/3… APE IN. #DesignerCon #DCON2026 #ArtToys #DesignerToys #NERVAPE

0:26
FiberDevs avatar
⟳ Nervos.bit retweeted
FiberDevs@FiberDevs·Nov 13

🚲 Fiber Dev Log 41 🚲 Channel V2 has landed in v0.10.0-rc2! ⚡️ Alongside the new signing and recovery protocol, we’ve been working on smoother channel funding and more accurate payment queries. Here's a closer look at this release candidate and the accompanying Mainnet update: - Channel V2 (rc2): V2 improves upon V1 with independent signing sessions (removing extra empty exchanges) and safer context saving for dropped connections. It also introduces full 32-byte payment hashes for on-chain settlement. - Mainnet deployment: An updated commitment-lock contract is now live on CKB Mainnet to support the new V2 settlement format. - Node operations: Channel funding and watchtowers now coordinate their CKB cell selection upfront, preventing transaction conflicts and saving setup work. 🔜 We're also working on Hosted LSP support for multiple channels per client, including separate CKB and token channels. Clients will be able to cancel their own invoices as well. These changes are still under review. Full dev log: github.com/nervosnetwork/fib…

Rypto avatar
⟳ Nervos.bit retweeted
Rypto@RyptoCrypto·Nov 8

Imagine giving an AI agent access to your crypto without handing over the whole wallet. That's what one builder is testing on $CKB. It's called QuotaCell. The idea is simple. You set a spending budget from a shared wallet, and teammates or software agents can make payments within those rules. The clever part is who enforces the limit. Not just the app. The $CKB network itself checks the rules, even when a payment is built outside the app. And if you change your mind, you can revoke access. In testing, the owner switched off a helper's spending power. The next payment attempt was rejected. Then the owner closed the shared wallet and recovered the spendable test funds. No signature from the helper needed. Here's the honest catch. This is one developer testing on a private local setup with test tokens. It's not on public testnet and hasn't been audited. Closing it also leaves about 600 CKB locked up for now. So it's early, not a finished wallet you should trust with real money. But as AI agents start handling payments, enforceable spending limits could matter a lot. An agent gets a budget instead of unrestricted access. That's the kind of practical building I like seeing on $CKB.

0:58
CKB Dev↾⇃ avatar
⟳ Nervos.bit retweeted
CKB Dev↾⇃@CKBdev·Nov 11

The monthly #CKB development log is out: This cycle focused on stabilizing light-client data consistency and expanding local developer tooling, alongside targeted infrastructure upgrades. We've overhauled how the browser light client handles storage and proof requests. By grouping database writes into single, atomic transactions, the client is now far more resilient against inconsistent data and interrupted syncs. A few other highlights: - OffCKB plugins: A new sandboxed host lets developers pull in compatible tools directly from npm or GitHub without bloating the core CLI. - Faster infrastructure: CKB Explorer was optimized to process heavy testnet blocks much faster, while the discovery service improved its connection handling. - DAO treasury: The experimental voting project added a standalone local demo, allowing developers to test the full path from a proposal to a treasury payout. Meanwhile, heavier architectural changes, such as the transaction-pool refactor and a new RocksDB layout, continue to move through rigorous review and benchmarking. Full dev log: github.com/nervosnetwork/ckb…

Common Knowledge Base Association (CKBA) avatar
⟳ Nervos.bit retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Nov 9

Learning to build on CKB takes time. The tooling is different enough from most ecosystems that new developers often hit walls that take days to get past. The CKB AI Scholarship is a direct response to that. CKBuilders get access to the Share-AI platform for shared AI model access at Level 1, and personal Claude accounts for more intensive development work at Level 2, with access tied to specific output and reporting requirements. Alongside this, a CKB-specific MCP server is in development, trained on CKB documentation and tooling, with the aim of giving the models enough context to be genuinely useful on CKB-specific problems. The hypothesis is straightforward: better AI tools, trained on the right material, should substantially reduce the time from onboarding to shipping. More than 40 developers are already using the platform. Full Q3 report 👉 talk.nervos.org/t/nervos-com…

Blockchain Pioneer Student Club avatar
⟳ Nervos.bit retweeted
Blockchain Pioneer Student Club@bps_club·Nov 9

🔗 [RECAP] BPSC KNOWLEDGE SHARING — EXPLORING NERVOS CKB What makes CKB different? Our latest online session brought BPSC members together to explore Nervos Network and its approach to blockchain design! 💻 From the blockchain trilemma to CKB’s technical foundations, we covered: 🔹 UTXO & the Cell Model 🔹 Lock Scripts & Type Scripts 🔹 CKB-VM & RISC-V 🔹 Learning resources and the CKBuilders community More learning, more sharing, and more steps toward becoming Web3 builders. 🚀 #BPSC #Nervos #CKB #CKBuilders @NervosNation

Post attachmentPost attachmentPost attachmentPost attachment
Nervos Community Catalyst avatar
⟳ Nervos.bit retweeted
Nervos Community Catalyst@NervosCatalyst·Oct 27

A year on from our last CKBuilders article, we return to follow the journeys of old and new faces in our developer community: their experiences, challenges, and successes. The future of CKB is bright! nervos.org/knowledge-base/CK…

CKB Dev↾⇃ avatar
⟳ Nervos.bit retweeted
CKB Dev↾⇃@CKBdev·Oct 14

A different kind of building at #CKCon 2026! 🇲🇾🌺 We're in Kuala Lumpur this week! Catching up, sharing ideas, and talking about what's next for CKB. Great to hear updates and fresh ideas from people across the ecosystem, including @RunningCKB, @ckbsamurai, @JackyLHH, @aaaaaaaalive24, @kashortgirl, @aszepieniec, @teaplusplus11, @BitcoinLightApp, with @ebubedev and @rypto joining remotely. Lots of interesting work and discussions about what's next! And finally we put the laptops aside and built miniature cities together. 🏙 Turns out we've got some pretty good city builders on the team too! 😄

Post attachmentPost attachmentPost attachmentPost attachment