do cool shit #web5 @runningckb

Joined January 2017
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.
Blackbox companion wallet generates capped spend auth tokens for the terminal, first sub threshold auto-approval refund confirmed🎉
11
1
46
1,179
Common Knowledge Brother retweeted
What’s the missing piece of the digital economy?
3
18
5
48
7,258
Common Knowledge Brother retweeted
Replying to @VitalikButerin
@VitalikButerin going back to UTXO @hasufl looking at POW elegance again We gonna make it Loving more this bear market now
I feel like all the advantages of PoS were pretty well understood 5 years ago. the many subtle advantages of PoW, very much less so ^_^
1
1
31
1,415
Common Knowledge Brother retweeted
I feel like all the advantages of PoS were pretty well understood 5 years ago. the many subtle advantages of PoW, very much less so ^_^
42
9
5
145
21,133
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. 🧵👇
6
24
2
94
7,682
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!
21
2
66
4,046
Common Knowledge Brother retweeted
Hey Nervos Fam, I’m building a $CKB directory app. Help decide which app image panels will be the default options, link to vote page in the replies, will be adding more applications to the list over the coming days so be sure to check back. #runckb
3
16
4
58
2,297
Common Knowledge Brother retweeted
Replying to @imadl_official
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.
5
2
28
1,473
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.
25
83
8
428
21,586
Common Knowledge Brother retweeted
Silent payments is not just a new approach to static payment codes. It's the first serious contender to improve the address derivation system since HD wallets in 2013. HD wallets were a big win over single keys, and silent payments could be a similar leap forward.
9
118
15
518
35,011
Common Knowledge Brother retweeted
Great idea! Here's a quick plot showing estimated transactions per second with different hash-based signature schemes. This one uses size-optimized parameters, verification-optimized below 👇
Replying to @n1ckler
Just give the expected impact on TPS if fully implemented for all active wallets transacting (evaluate size impact + comparr aggregation model to current implementation) Everything else just unnecessary tech jargon.
24
33
6
149
38,225
Common Knowledge Brother retweeted
This gets at the core of why the bitcoin quantum FUD is overblown. There certainly seems to be some progress on the theoretical front, but how close are we to actually building quantum computers with persistent uptime that can wage these attacks? Not saying it will never happen, but the leap from theoretical possibilities to application at scale is still unclear to me.
Replying to @apruden08
This is an obvious fallacy. Nothing about this chart indicates how fast we are getting there. You’re highlighting progress in theoretical algorithm optimization. None of this indicates actual rate of progress in the system needed to run these algos.
27
8
2
137
19,421
Common Knowledge Brother retweeted
Basically Google is saying "We've got a lot of ink on a whiteboard that says really threatening stuff...better hope we never take it seriously enough to try building the Hawaii-sized facility we'd need to pull it off!"
Google is basically saying: “We’ve cut the quantum resources needed to break Bitcoin’s encryption by 20x. We can now break it. We can prove it. We’re just not going to tell you how. We’ve slowed down research to give crypto a chance. You have until 2029 to figure out a solution. Good luck.”
1
1
160
Common Knowledge Brother retweeted
Going from ~1,000 noisy qubits to 500k fault-tolerant ones by 2029 isn’t just a "roadmap",… it’s a **physical miracle** or a massive bluff.
Replying to @nic_carter
Specifically, this paper. It's a brand new resource estimate that's wildly lower than prior estimates of what it would take to break ECC-256. Featuring the Google Quantum AI team + Justin Drake + Dan Boneh quantumai.google/static/site…
38
51
9
456
68,632
Common Knowledge Brother retweeted
When evaluating the claim of deep bag-biased Quantum agitpropagandists, it’s always more useful to look at what they are NOT telling you. Recent claims suggest a Quantum computer using neutral atom arrays would require only (!) ~20,000 logical qubits to break Bitcoin. What they tell you is that this is significant because researchers at Caltech recently demonstrated a 6000 (!) logical qubits array. What they do NOT tell you is that those qubits weren’t not entangled, which is a requirement to run Shor’s algorithm. So what is the state of the art in terms of actually entangled logical qubits under the neutral atoms architecture? NINETY SIX (96) qubits. How long did they maintain coherence? 1-2 seconds. How long did the new Oratomic paper suggest the algorithm they designed should run? DAYS! So not only must state of the art in SIMPLE qubits entanglement increase more than 2 orders of magnitude, their ability to maintain coherence across circuit depth must be preserved ONE HUNDRED THOUSAND times longer than they currently do. Suffice to say they have no idea how to even get there but that shouldn’t get in the way of a headline worthy paper!
35
129
32
715
58,632
Common Knowledge Brother retweeted
Please welcome SHRIMPS🦐 to the family of stateful PQ signatures: 2.5 KB hash-based sigs across multiple devices. SHRINCS🛋️ gave ~324-byte sigs but is single-device. SHRIMPS🦐 addresses multi-device; any device loaded from the same seed creates sigs 3x smaller than SLH-DSA
42
127
27
550
151,048
🫡 CKB VM: 0 precompiles, 0 compromises Pure RISC-V: Infinite possibilities Learn more 👉github.com/nervosnetwork/ckb…
They say quantum computer attacks on blockchain is 10 years away. I sat down with @matt_bitcoin Director of @NervosNetwork at @MiningDisrupt last week. We had a serious discussion on this topic and how $CKB has positioned itself in a unique way that even @VitalikButerin admires.
2
14
97
4,925
Common Knowledge Brother retweeted
Splicing is now officially ratified in the lightning spec. Let’s gooooooo 🎉
16
31
1
224
15,007
Common Knowledge Brother retweeted
lnget v1.1.0 has just been released! it now supports both MPP+L402 for agentic payments on the Lightning Network the CLI is now more agent friendly w/ JSON input+output, context management feats + support for an MCP server via `lnget mcp serve` many bug fixes also included!
LND now supports MPP! With the latest lnget release, you can use both L402 and the Machine Payments Protocol (by @tempo @stripe) for agentic payments on Lightning. ⚡  lnget auto-detects what the server supports and pays in the same request. One tool that supports both protocols.  This release also includes an agent-native CLI with JSON i/o, MCP server support, and context management features.  github.com/lightninglabs/lng…
5
9
1
40
5,572
Common Knowledge Brother retweeted
looks like the Tempo devs have finally internalized what Bitcoin devs have known for sometime: payment channels like Lightning are the ideal construct for real time machine-to-machine payments ⚡️ channels update off-chain so minimal latency streaming payments come naturally
I’ve spent most of my career scaling payments. From 2017-2021, we poured years into building state channels on Ethereum The tech worked, but nobody used it. People used blockchains for trading tokens, not for making payments, and that's why L2s had to come first Agents are the users we were waiting for, and that's why we're stewarding the launch of the Machine Payments Protocol (MPP) with channels baked in
9
23
3
133
33,541