Cypherpunk · #PoW · #CKB Contributor also on Nostr: npub1j7948t0lwa3vznttp55nl73funfrynnkwy3pj67xnxadhv6fy7rqq393v4

Joined December 2022
CKB Dev↾⇃ retweeted
Happy to share some news from @ckba_build CKBA’s DevRel and Ecosystem Support teams: our paper on CCC (github.com/ckb-devrel/ccc/), When EVM Defaults Break: Three SDK Patterns for UTXO-Family Wallets, has been accepted for poster presentation at IEEE International Conference on Distributed Ledger Technologies (ICDLT) 2026! Through this collaboration, @Hanssen0 (@CKBDevrel) and I (Ecosystem) built on the CCC team’s existing engineering work to distill three reusable design patterns: • Transaction composition: helping applications handle inputs, change, and fees. • Unified signing: providing a common interface across different wallet signing methods. • Reusable wallet connectors: sharing wallet connection and onboarding components across applications. The conference brings together academia and industry, with organizers from Nova School of Business and Economics, NOVA Information Management School, and the IEEE Portugal Section. It is part of BLOCKCHAIN. PT, a project funded through Portugal’s Recovery and Resilience Plan and the EU’s NextGenerationEU programme. For us, this is an opportunity to bring CKB’s experience in developer tooling and application development into a broader conversation with researchers and builders. Thanks to Hanssen and everyone who has contributed to CCC!
9
34
8
90
3,900
Introducing: Build on CKB! With the rapid growth of our CKBuilders programme, we've been devising new offerings to accommodate developers who are new to CKB and interested in learning. We now have the Build on CKB telegram channel for new developers to participate in weekly competitions to win prizes, receive devrel support, participate in peer learning, and get pre-hackathon preparation and support! We recently completed our first Build on CKB campaign, with 8 new developers all receiving CKB prizes! If you missed out, don't worry! We have a new campaign live now. Check it out on CKBoost: ckboost.netlify.app/campaign…
4
30
1
84
3,162
Straight from @Coinbase’s April paper on quantum computing and blockchains. 👇 “Crypto-agility is a highly recommended practice in general [...] even more so in the context of PQC.” Now guess which chains were designed to switch cryptographic algorithms without disrupting operations🧠 Hint: there’s only one.
2
32
4
86
3,943
CKB Dev↾⇃ retweeted
We are excited to announce that QuantumPurse is expanding its scope with two new projects: 🚀 QuantumPurse V2 Building on the foundation of QuantumPurse V1, security is reimagined across every layer — from software to hardware. High-performance, feature-rich, and built natively for each platform. 🔐 Hardware Integration Building on the shoulders of Trezor, we’re integrating CKB and bringing quantum-safe crypto to the quantum-ready hardware wallet, Safe7. Links: QPV2: 🎥 youtu.be/ND1t1HnbQpQ Trezor integration: 🎥 youtu.be/mtZ4mJIbD1U Home page: quantumpurse.org/ #CKB #PQC #PostQuantum #Crypto #Web5 #HardwareWallet #Trezor
8
34
6
86
6,262
CKB Dev↾⇃ retweeted
We've been talking a lot about tech here — Scripts, VM, protocols, optimizations ... Love that! But builders aren't just commit histories. That's why we started CKB Builder Story, a small series about the people behind the protocols. 🧑‍💻✨ Our first story features Tea (@teaplusplus11), creator of Quantum Purse (@quantumpurse), the industry's first SPHINCS+-based quantum-resistant wallet. He has built across ecosystems: EOS, Bitcoin, Ethereum, and now CKB. Here he shares how he stumbled into CKB, why he decided to stay & build long-term, his appreciation for Proof of Work, and why good architecture + good people matter. #nervos #pow #BlockchainDev
8
29
1,653
CKB Dev↾⇃ retweeted
Our paper on Measuring and Attacking the Ethereum Global Network was presented at the Science of Blockchain Conference 2025. Thanks to @masserova for presenting on our behalf! Paper: ia.cr/2025/588 SBC Recording: youtube.com/live/_2gnJjvodws… Mine: youtube.com/watch?v=8XmuQRhS…
2
5
1
28
3,001
CKB Dev↾⇃ retweeted
Built this `ckb-crypto-service` — a unified IPC service for calling crypto algorithms on CKB. - Designed to make on-chain development smoother and more consistent. - Works across Rust, C, and JS. - Currently supports: Blake2b, SHA-256, RIPEMD-160, Secp256k1, Schnorr, and Ed25519 Full post 👇 EN: yakihonne.com/profile/nprofi… CN: yakihonne.com/profile/nprofi… @CKBdev @CKBDevrel #IPC #multiprocessing #BlockchainDev
3
18
2
58
3,512
CKB Dev↾⇃ retweeted
✅ Meepo Hardfork completed at epoch 12293. Spawn syscall and CKB-VM v2 now live. explorer.nervos.org/hardfork If your node isn’t syncing blocks, please upgrade to the latest version. ⚙️ Upgrade: github.com/nervosnetwork/ckb… @NervosNetwork @CKBEcoFund @CKBDevrel @NervosNation #nervos #ckb #meepohardfork #hardfork
5
37
5
101
8,292
CKB Dev↾⇃ retweeted
Vitalik’s just realized RISC-V could be the future of ETH’s execution layer. Meanwhile, CKB’s been using RISC-V for smart contracts since day one and keep making moves with RISC-V in our CKB-VM.👷 🏗️⚒️ Let’s see what’s possible with CKB-VM enhancing blockchain functionality and check out these examples! - Running Bitcoin Scripts on CKB-VM: blog.cryptape.com/running-bi… - Quantum Computation: New Challenge to CKB’s Security? blog.cryptape.com/quantum-co… - Implementing EIP-712 on CKB-VM blog.cryptape.com/implementi… - Building a Zero-Knowledge Virtual Machine on CKB-VM for Privacy-Preserving and Secure Computing blog.cryptape.com/building-a… - CKB-VM brief intro: docs.nervos.org/docs/tech-ex… #riscv #Ethereum
2
29
2
101
5,094
CKB Dev↾⇃ retweeted
Replying to @FiberDevs
Excited to build, test, and improve together ⚡️
1
33
1,418
RT @Cryptape: ⚠️ Caution: NOT for casual readers! 😎 We’re tackling Bitcoin C++ codebase porting for CKB virtual machine and overcoming bina…
1
2
CKB Dev↾⇃ retweeted
✨ Showcase the powerful versatility of CKB-VM: blog.cryptape.com/running-bi… Now, you can run Bitcoin Script opcodes and validate transactions on CKB-VM without code changes. For dApp developers, this means validating a wider array of Bitcoin addresses on CKB, leveraging the security and decentralization of both Bitcoin and Nervos Network. What other possibilities do you see? Share with us 🫡 @NervosNetwork @CKBEcoFund #Bitcoin #nervosnetwork #BTCLayer2 #riscv #BTCFi
6
36
4
106
9,935
CKB Dev↾⇃ retweeted
Delighted to announce the release of our latest contribution to Bitcoin ecosystem - the RGB++ Protocol. RGB++ represents an extension of the RGB protocol, incorporating single-use seals and client-side validation techniques to effectively manage state alterations and transaction verification. Through isomorphic binding, it maps Bitcoin UTXOs onto Nervos CKB Cells, leveraging script constraints on both CKB and Bitcoin chains to ensure the correctness of state computation and the validity of ownership changes. Addressing technical challenges encountered in the implementation of the original RGB protocol, RGB++ introduces a myriad of possibilities, including blockchain-enhanced client validation, transaction folding, shared state, and ownerless contracts, all without the need for cross-chain transactions and without compromising security. Discover more about our groundbreaking advancements in blockchain technology. talk.nervos.org/t/rgb-protoc…
12
93
24
254
90,953
CKB Dev↾⇃ retweeted
Before we debate the feasibility of Bitcoin L2, it's helpful to define what Bitcoin L2 is? In my view L2 is a layer built on top of X to make X more "powerful", e.g. more scalable, more programmable, more privacy, etc. "A L2 is a layer as secure as L1" is simply an illusion. Extra layers introduce extra security assumptions and implementation bugs - you can still lose money in Lightning or optimistic rollups, e.g when you want to close channel or challenge/escape while L1 is in congestion. ZK rollups have different problems like more assumptions and unclear prover incentive design. Only L1 is as secure as L1. The compromise on security is the exact reason why L2s are more "powerful". So the right question is not if L2 is as secure (they're not), but how much less secure and how much more powerful? Different L2s make different choices, some are worse than others because they sacrificed a lot for little value in return. Some are just different preferences on trade-offs. Bitcoin L2 is even more interesting because in this case the X can refer to both 1. the PoW driven Bitcoin ledger, and 2. the BTC asset/currency/money. CKB is less secure/decentralized than the Bitcoin ledger, but as a 4 year-old PoW chain it's much more secure/decentralized on its own than recent L2s who try to "borrow" security from L1 (for L2s "security borrowing" is more like a fast bootstrapping strategy rather than a requirement). CKB extends UTXO model to bring more value and programmability to BTC, make BTC more powerful. CKB is UTXO based also means it could work well with other Bitcoin L2 technologies like Lightning/RGB/Taproot assets/inscriptions (yeah I consider client-side validation protocols a kind of L2). p.s. I use "secure/security" for short, L2s could compromise on decentralization (can read as "censorship resistance") too.
3
27
4
73
5,025
CKB Dev↾⇃ retweeted
CKB Is An Ideal Bitcoin Layer 2 As a monetary system, Bitcoin is inherently layered. But what should a Bitcoin monetary layer 2 look like? It should be an integral part of the entire system, sharing the same foundational values and design decisions. Ideally, it would be interconnected with layer 1, allowing for free BTC flow between layers, and offering a consistent user experience for both users and developers. CKB is the ideal monetary layer 2 for Bitcoin. CKB shares Bitcoin values, e.g. PoW not PoS, UTXO not Account, decentralization over TPS, no issuance manipulation, etc. With Cell, an extended UTXO model, CKB can provides more decentralized use cases for Bitcoiners while maintaining a consistent user and developer experience. Imagine operating CKB applications with a Bitcoin wallet, rotating addresses for privacy, and managing UTXOs under dust limit / minimum capacity constraints - all underpinned by the same foundational principles. Moreover, CKB is an excellent experimental ground for Bitcoin, provides an enhanced UTXO model with stronger programming capabilities while upholding Bitcoin's core values and design philosophy. This means CKB faces challenges akin to those of Bitcoin, with optimal solutions potentially benefiting both. The ability to use customized cryptographic primitives on CKB empower developers and researchers to explore their most innovative ideas. On CKB, it's easier to test new ideas like covenant (CTV), PSBT and Intents, which, if successful, could be integrated back into Bitcoin Layer 1. Importantly, a monetary layer 2 doesn't need to share security with Bitcoin. Multiple monetary layer 2s can form a more decentralized, resilient, and loosely connected monetary system with Bitcoin at its core. This system wouldn't have a single point of vulnerability in terms of security, and it would offer consistent user experience without liquidity fragmentation seen elsewhere. Because Bitcoin is money, it only needs to provide monetary functions, not everything else. Because UTXO is the first-class citizen here, accounts are abstracted away and managed off-chain. #CKB aligns perfectly with this vision, making it an ideal #Bitcoin #Layer2 .
19
123
18
233
36,640
CKB Dev↾⇃ retweeted
CKB smart contract developer, who's interested to work on our game for L1. No salary, just holy enthusiasm 😁 Are you technology believer? DM. @NervosNetwork community, share please!
4
18
50
2,019
CKB Dev↾⇃ retweeted
For interested readers, here're some real progresses on AA and quantum security instead of cheap talks - joy.id/ - github.com/cryptape/quantum-…
9
37
1,749
Satoshi: imagine a global financial system without middlemen ~15 years later: Middlemen Extractable Value, the engine of industry
1
7
37
2,009
CKB Dev↾⇃ retweeted
1/ I am currently testing a new revolutionary protocol, @khalani_network, the future of #DEFI. Khalani is a universal liquidity protocol and a multi-blockchain permissionless bridge, and that's what changes everything.
1
8
2
28
1,865