←
tea1,150 posts
tea avatar

tea

@teaplusplus11
◷ Joined February 2021▧ 20 Photos and videos
Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Nov 17

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.

AI made hacking free. Bitcoin is about to make it expensive. Proof of work is the firewall of the AI age. Mark the date. White Swan incoming.

Common Knowledge Base Association (CKBA) avatar
⟳ tea 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
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Nov 12

"A blockchain keeps public keys and signed history visible forever, so we can't quietly rotate the past." That line from @wj_beaumont's new blog post explains why crypto-agility matters even more for blockchains than for banks. A chain can't reissue cards after a breach, so it has to move before the threat arrives, and nobody can agree on when that will be. So how do you prepare for the switch to post-quantum cryptography when the deadline doesn't come with a date? Will's answer: "The order matters more than the choice." Build the ability to swap cryptography first. Then pick the schemes. @Algorand shows it working. LogicSignatures, small programs that authorize transactions, were already live on its mainnet, so last year Falcon accounts arrived through them with no consensus upgrade. CKB was designed for crypto-agility from launch. Every signature check runs in a lock script: ordinary software on its RISC-V VM. Even the default lock that guards most coins on CKB today works this way. A post-quantum lock based on SPHINCS+ is already live on mainnet. Adding it took no fork. Will is clear that "adding a scheme is the easy half." The other half, retiring the old scheme and getting people to move, is hard on every chain, CKB included. But CKB holders already have somewhere to move, and they can start today.

Quantum resilience is more than adopting post-quantum cryptography today; it means being able to adapt as cryptographic standards evolve. Our CPO, @wj_beaumont, explains how we're building crypto agility into Algorand's protocol to make that possible 👇 algorand.co/blog/crypto-agil…

Rypto avatar
⟳ tea retweeted
Rypto@RyptoCrypto·Oct 25

This is what real growth looks like. If you really want to know if a project's healthy, you don't look at the chart. You look at who's building on it. And on that front, CKB just had a brilliant quarter. Their community developer programme has grown to nearly a hundred active builders, with over 25 new ones joining just this quarter. Their project tracker jumped from 45 projects to 59. And they ran a hackathon focused on Fiber, their payments tech, that pulled in around a hundred participants and 66 submissions. But here's the part I love most. Look at where this growth is coming from. Not just the usual Silicon Valley crowd. We're talking real, in-person meetups in Kenya, Nigeria, and Vietnam. Nairobi, Mombasa, Hanoi. Developers in emerging markets, where fast, cheap payments can really make an impact. And it's not just solo devs either. Teams from other ecosystems, Cardano, Bitcoin, Lightning, are now showing up to explore building on CKB too. A lot of these are still early prototypes and there is still a lot of work to do. But a growing, global, grassroots community of actual builders? That's the strongest foundation any project can have. Price comes and goes. But people building, all over the world? That's how something lasts. $CKB @NervosNetwork @ckba_build

1:03
Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Oct 22

CKB can add quantum-resistant signatures without a network upgrade, and one is already live. But a quantum-safe lock does little if your wallet can't use it or your exchange won't accept the deposit. On the road to quantum safety, that is where most of the work remains. Part 1 covered Jan Xie's (@busyforking) notes from a @FraunhoferSG talk on where post-quantum migrations stall. His follow-up scores CKB against the same picture. By design, CKB never faced the protocol hurdle Bitcoin is still stuck on, and what's left looks like the work facing everyone else 👇 👉 The core protocol is already quantum-safe. Mining on CKB relies on hashing, a kind of cryptography quantum computers aren't known to break. Signature checks sit outside the core rules, in lock scripts, so a new signature scheme can be added as a new lock with no network upgrade. The live lock, SPHINCS+, is audited, and so is Quantum Purse, the wallet built on it. Three more schemes are running on testnet, and we broke down all four last week. 👉 The cost of bigger signatures is block space. Post-quantum signatures are much larger than today's. With the largest SPHINCS+ signatures, a block that holds about 1,000 ordinary transactions holds about a dozen. That's a real throughput cost. If demand grows while signatures get bigger, blocks fill sooner and fees rise as users compete for space. At CKB's minimum fee rate, a SPHINCS+ transaction costs under 0.0001 CKB, but the minimum only holds while blocks have room. What doesn't grow is the cost of running a node. CKB caps the bytes and computation in every block, so bigger signatures mean fewer transactions per block, not heavier blocks. That answers the worry about centralization. Capacity is the trade-off, and it's why smaller schemes matter: the lattice-based locks on testnet produce much smaller signatures than the largest SPHINCS+ options. 👉 A quantum-safe lock is only as safe as whoever can upgrade it. On CKB, the code that checks your signature lives in its own cell, and locks point to that cell. They can point to it in a way that allows upgrades, so whoever controls the code cell can replace the code. If that cell is guarded by a classical key, funds behind a post-quantum lock still depend on classical cryptography. The SPHINCS+ lock works this way: its code cell sits under a multisig lock with classical keys. The code hasn't changed since it went live, so what runs today is the audited original. For now, though, those classical keys are still part of what protects the funds. The alternative is for a lock to point to its code by its hash, a unique fingerprint of the code itself. Then nobody can mess with it, because any change would produce a different hash. As Jan puts it, quantum resistance "has to cover the whole authorization path." 👉 The hard part now is adoption. Post-quantum locks are already on CKB. Getting them used is the work now: wallets that can sign with them, hardware wallets that can hold the keys, and exchanges and custodians that will accept the deposits. In Jan's words, an exchange that can't credit a SPHINCS+ deposit is "a hard stop, whatever the chain allows." Some of that software needs rebuilding, not just updating. Exchanges often generate a fresh deposit address for every customer from a single public key, and today's standard post-quantum schemes can't do that. CKB's peer-to-peer protocol and Fiber, its payment channel network, still use classical cryptography too. But both can be upgraded without touching the core rules, so neither has to wait for a network-wide vote. 👉 A new lock only protects the funds moved into it. Funds under the default lock stay on today's cryptography until their owners move them, and some never will. That's true on every chain. On chains that need a protocol upgrade, the upgrade gives owners somewhere safe to go, but it can't move funds on their behalf. No upgrade will move Satoshi's coins for Satoshi. @coinbase's recent blog post on Bitcoin's quantum migration starts from the same fact. It urges the community to begin the work now, and treats coins that may never move as a separate problem that needn't hold that work up. What CKB changes is the timeline. Bitcoin is still debating the upgrade that would let owners migrate. On CKB, the door to migration is already open. Whether and when to walk through it is each owner's call. The ecosystem's job is to make sure it works, end to end, when they do.

Crypto faces a binary future: migrate to quantum-resistant cryptography before a cryptographically relevant quantum computer arrives, or scramble to rebuild after the security of today's systems has been compromised. The problem is that nobody knows when that day will come. Some researchers assign significant odds to such a machine emerging around 2030, potentially without the public knowing it exists. A sufficiently powerful quantum computer could break the public-key cryptography securing everything from online banking and private messages to cryptocurrency wallets. Governments, including the US and EU, are already preparing for this threat, with official timelines targeting the phaseout of vulnerable cryptographic algorithms beginning around 2030. Project Eleven’s @apruden08 describes this as crypto’s binary future. The timing remains a known unknown, somewhat like Schrödinger’s cat: until the box is opened, nobody knows for sure. But cryptographic migrations take years, and uncertainty about when the threat will materialize is no reason to postpone preparing for it. That was the backdrop to a recent talk by @FraunhoferSG researchers Prof. Daniel Loebenberger and Prof. Marc Stöttinger, attended last month by Jan Xie, Chief Architect and co-founder of @NervosNetwork. The researchers presented a study evaluating six widely used security systems, including OpenSSL 3.0 and AWS KMS, against measurable criteria for post-quantum migration readiness. ⚠️ Not a single system met the required thresholds. ⚠️ For public blockchains, the challenge is even greater. Banks and cloud providers have central authorities that can audit their systems, allocate resources, and enforce migration deadlines. Decentralized blockchains have no such authority. Major protocol changes require coordination and broad agreement among independent participants, making an already difficult migration even more complicated. The following is a breakdown of Jan's six key takeaways from the talk in plain English 👇 👉 "Algorithms are ready; the bottleneck has moved to bytes." For many post-quantum signature schemes, size is a bigger obstacle than speed. A typical blockchain signature is around 65 bytes, whereas post-quantum signatures can range from roughly 0.7 KB to 50 KB, depending on the scheme. That difference matters enormously on a blockchain, where signatures must be transmitted and verified across the network. Larger signatures mean fewer transactions per block or larger blocks. And larger blocks increase the cost of running a node, potentially making the network more centralized. 👉 "Plan for costs that grow with the message." Today's signing hardware typically receives a 32-byte hash rather than the full message. Some post-quantum schemes, in their standard form, require the entire message to be passed to the signing device. For a 1 MB message, that's roughly 31,250 times more data. Exchanges, custodians, and hardware wallet manufacturers may therefore face substantial infrastructure changes, potentially including hardware replacements. 👉 "Crypto-agility can be measured." Crypto-agility is the ability to replace cryptographic algorithms without rebuilding the underlying system. The researchers proposed a framework for scoring this capability. All six systems fell short, particularly in three areas: generating keys for specific purposes, enforcing centrally managed algorithm policies, and migrating existing keys to new algorithms. The important takeaway is that crypto-agility doesn't have to remain an abstract promise. It can be scored. 👉 "Governance decides where to cut." A company can mandate a cryptographic migration. Bitcoin cannot. As Jan puts it, Bitcoin "has no authority that can make those decisions." Changes require broad agreement across the ecosystem. Meanwhile, per @projecteleven’s data, more than 7 million BTC, over a third of the supply, sit in addresses whose public key is already exposed. The coins most at risk are waiting on a process that can take years. 👉 "The biggest gap is organizational." The talk highlighted the familiar reasons why cryptographic migrations fail: critical knowledge concentrated in one person, incomplete or outdated system inventories, dependence on vendor roadmaps, and rushed deployments. None of these problems are specific to quantum computing, yet they can determine whether a post-quantum migration succeeds or fails. 👉 "Verification runs through the whole thing." The researchers call this failure mode "The Algorithm Nobody Used": an upgrade goes live, but nobody verifies whether the new protection is actually being applied. The solution is to decide what success looks like before migration begins, then continuously verify that systems remain functional and that the intended cryptographic protections are actually in place. Next: What these findings mean for public blockchains, and how CKB's architecture addresses the challenge of cryptographic migration.

Post attachment
CKB Dev↾⇃ avatar
⟳ tea 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
Nervos Community Catalyst avatar
⟳ tea retweeted
Nervos Community Catalyst@NervosCatalyst·Sep 3

CKB Off-Chain is coming to Vietnam! 🇻🇳 In collaboration with @bps_club, we will be hosting a builder-focused event involving CKBuilders, local blockchain developers and students for an evening of education, exploration and networking! We will discuss what makes CKB interesting and unique for blockchain developers, ways to get started on CKB, as well as presentations from current CKBuilders about their own experiences. It promises to be an enlightening event!

Post attachment
Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Sep 2

A forgotten HTTP status code from the 1990s is becoming a checkout layer for machines. 402 Payment Required was reserved for digital payments long before the web had money software could actually use. Now it does. x402 turns a 402 response into something an AI agent can understand: here’s the price, here’s how to pay, send proof and get the resource. L402 applies the same basic idea to Lightning: pay the invoice, prove payment, access the service. Different protocols, same shift. Instead of sending software to a checkout page, the web itself can tell it what something costs and how to pay for it. That makes payment part of the HTTP request, not a separate workflow that necessitates a human in the loop. What still matters underneath is the rail that actually moves the money. That’s where Fiber comes in: settling the tiny, frequent payments these protocols are designed to create 👉fiber.world/showcase

Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Aug 31

One of the more encouraging things this year is that CKB’s builder ecosystem kept expanding while much of the industry was doing the opposite. Teams were shrinking, budgets were being cut, and a lot of speculative activity disappeared. Meanwhile, more developers kept showing up to experiment on CKB. Today, over 100 are working on or exploring the network: - 70 formal CKBuilders working through a structured program - ~40 more coming in through Build on CKB, an open group for developers curious about the chain - 45 projects now listed on the CKBuilder tracker, with 23 added in a single quarter and 15 submitted for technical review by core CKB developers Claw & Order, a two-week AI Agent hackathon, closed with 22 open-source submissions; 16 came from CKBuilders, including the top two prize winners - The work spans a surprisingly wide range: ZK key recovery for AI agents, a Groth16 zkSNARK verifier, a Fiber desktop client, an ML-DSA post-quantum implementation, a DID reference dashboard, lending primitives, prediction pools, and more Some of these builders are now graduating from experimentation into independent projects. But the more important signal is that all of this happened during one of the bleakest periods for the industry. If this is what the builder pipeline looks like when capital and attention are scarce…what happens when they aren’t? 👀

Post attachment
Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Aug 21

Quantum computing stopped being a science project somewhere along the way, and announcements like this are how you can tell. Helios is being deployed through Oracle Cloud Infrastructure. Quantinuum has signed a manufacturing partnership to help build future systems at scale. Revenue grew 279% year-over-year. Sol is on the roadmap for 2027, Apollo for 2029. For years, the skeptical case was that quantum computing might never escape the research phase; that the papers, prototypes, and laboratory demonstrations would never become machines that can be error-corrected, manufactured at scale, deployed reliably, and improved generation after generation. Announcements like this chip away at that argument. Quantinuum has not built a cryptographically relevant quantum computer. But more of the obstacles between today’s machines and a CRQC are becoming engineering problems: fault tolerance, manufacturing, systems integration, cloud deployment, and successive hardware generations with explicit roadmaps. Enormous hurdles remain, but betting the security of long-lived cryptographic systems on those hurdles never being cleared is becoming harder to defend. For blockchains, the relevant timeline is not the date a quantum computer can break secp256k1. It is that date minus the time required to replace secp256k1 across a live network. Replacement cryptography has to be selected, implemented, audited, integrated into wallets and infrastructure, and adopted by users whose assets remain protected by vulnerable keys. None of that happens instantly. There is another problem too: we do not yet know which post-quantum schemes will prove durable enough to rely on for decades. That is exactly what makes CKB different. CKB does not need to wait for the industry to settle on a single post-quantum winner. Cryptographic verification lives in programmable Lock Scripts running on CKB-VM, so new schemes can be introduced without changing CKB’s consensus rules. SPHINCS+ is already live on mainnet. If a better scheme emerges, it can be added alongside it. If cryptanalysis weakens one, users can migrate again without redesigning the protocol underneath them. For CKB, the post-quantum migration does not start when Q-Day gets close. It has already started, and if circumstances change, we can change direction on the go instead of starting over.

We believe the future of enterprise computing will bring AI, HPC, and quantum together. That’s why, today, Quantinuum and @Oracle have announced a multi-year strategic partnership to bring quantum computing to Oracle Cloud Infrastructure customers and accelerate the commercial adoption of hybrid quantum-AI computing. As part of the collaboration, our Helios quantum computer will be deployed in a U.S.-based Oracle AI data center, alongside OCI’s HPC and GPU infrastructure, and made available through OCI’s quantum service to give OCI customers a practical and secure way to explore how high-fidelity quantum computing can complement existing AI and HPC workloads—using the governance and access controls they already rely on. Read the joint announcement: quantinuum.com/press-release…

0:16
Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Aug 19

There’s an interesting connection between two of the biggest changes in Vitalik’s updated Ethereum roadmap. The first is that quantum safety has clearly moved up the priority list. The work being discussed is substantial: leanSPHINCS, signature aggregation, zkzk frames to make post-quantum signatures economical, and formal verification as part of the path toward getting there. The second is architectural. Vitalik suggests that those zkzk frames could eventually expose a simpler ISA such as leanISA or RISC-V, with the EVM becoming an IR on top rather than something permanently enshrined in the base protocol. These may look like separate roadmap items, but they point toward the same underlying lesson: the less you permanently bake into the base protocol, the easier it is to change the things above it. That is especially relevant now that quantum safety is becoming a concrete engineering priority rather than a abstract concern. CKB was designed around this idea from the beginning. CKB-VM has used RISC-V since mainnet launch, but RISC-V itself is only part of the story. The VM is deliberately crypto-agnostic, so cryptographic verification can be implemented as ordinary executable code in Scripts rather than hard-coded into the protocol. That’s what gives CKB crypto agility. A new signature scheme such as SPHINCS+ can be deployed as a Lock Script without changing CKB’s consensus rules, and users can migrate when they need to. Interestingly, when Vitalik first proposed replacing the EVM with RISC-V in 2025, he pointed to CKB-VM as one of the precedents. Ethereum is now treating quantum safety as a major protocol priority. Different architectures and different paths, but the direction is familiar: Keep the base protocol simple, general and stable. Make everything that may need to evolve programmable.

I updated my 2023 roadmap diagram to overlay where the items that were there sit in the current Strawmap ( strawmap.org/ ). In general, a lot of overlap, but: * Some things got reshuffled in order (eg. quantum safety up-prioritized) * Some things deprioritized (eg. VDFs; many EVM improvements) * Some things replaced with superior constructions (eg. Verkle -> unified BT -> PBT; state expiry -> new state types) What's most striking, however, is that some completely new things are in the strawmap that are NOT in this diagram, because they were not in the 2023 roadmap at all. These reflect changing priorities. Notably: * First-class attention to strong privacy. This covers: keyed nonces and recent roots, aspects of FOCIL, lean privacy pool & wormholes * Aggressive scaling in the context of post-quantum. This covers: leanSPHINCS signatures and aggregation, zkzk frames (see ethereum-magicians.org/t/eip… ) * Lean-ification of the spec, to assist in formal verification (full FV of everything is only possible because of modern AI) * Blob and gas futures (this idea just didn't exist back in 2023) * Native rollups (SNARKs were nowhere near mature enough to even consider this back in 2023) * A more open design space for the "future of the EVM". zkzk frames already implies that the protocol will expose to users some ISA that's not the EVM - current leading candidates are leanISA and RISC-V. These ISAs are more simple, modern and efficient than the EVM. Once they're there, why not expose them to developers everywhere? (And then, why not turn the EVM into being an IR on top of that ISA, instead of an enshrined feature massively complicating the base protocol?) Though much of the deeper exploration here is too early even for the strawmap. * New state types are not just a replacement for expiry, they're a fundamentally different paradigm to how Ethereum does scaling A common theme in scaling, found in both state types and zkzk frames (both new ideas), is that instead of trying to maximally scale ALL ethereum activity, we try to create specialized mechanisms that have more restrictive properties that make them more scaling-friendly, while supporting the heaviest loads incurred by users and applications today (eg. token transfers, swaps) and tomorrow (eg. privacy protocols). The other common theme is treating STARKs and AI-accelerated FV as first-class objects, that we are okay betting the technical future of Ethereum on. There are recursive STARKs in many layers of the protocol, one particular primitive (the "aggregate to union verified dependencies" primitive) is expected to be used in *three* places in the protocol: EL, CL and DL. This can only be safe with formal verification, which is itself only feasible with modern AI tools. In general, many steps forward in maturity. And a huge amount of hard work by many dozens of Ethereum researchers and developers on all of these features. Ethereum will be quantum-safe. Ethereum will put users' privacy first. Ethereum will be secure. Ethereum will be censorship-resistant. Ethereum will be highly performant and scalable while satisfying the above. And Ethereum will be Lean.

Post attachmentPost attachment
vitalik.eth avatar
⟳ tea retweeted
vitalik.eth@VitalikButerin·Aug 16

Bitcoiners deserve a lot of credit for pioneering many of these ideas (see Utreexo). But yes, this is what the current proposed Ethereum scaling strategy looks like in action. We want Ethereum to have the best of UTXO-style state, dynamic state, and everything in between, allowing the great majority of Ethereum's activity to be hyperscaled without sacrifice to decentralization, ease of node running and censorship resistance. firefly.social/post/x/208898…

Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Aug 7

The easiest payment infrastructure to use is often the infrastructure that puts one company in control. And, if we’re being honest, the convenience and UX benefits are real. So are the trade-offs. A managed provider can abstract away liquidity, settlement, compliance, and technical complexity while offering businesses a predictable experience, customer support, and a single accountable counterparty. For many businesses, that is precisely what makes new payment rails usable in the first place. But convenience comes with dependency. Businesses rely on the provider to keep supporting the assets, markets, and payment flows they need. If the provider changes its pricing, restricts access, suffers an outage, or discontinues the service, users cannot simply route around it. Fiber explores a different model. Fiber is open payment infrastructure that anyone can use, build on, or help operate. Connect to the network and pay across it. Or strengthen the network by opening channels, providing liquidity, routing payments, running watchtowers, and helping connect Fiber with other payment networks. There is no single company controlling every payment, route, or service. Fiber grows through the independent participants who use it, operate it, and build businesses on top of it. It is less like a product owned by one company and more like a living economic network—one that becomes more useful, resilient, and valuable as more people contribute to it. Try Fiber today 👉 fiber.world/docs/build/inter… Or, build on it 👉 fiber.world/docs/build/toolc…

FiberDevs avatar
⟳ tea retweeted
FiberDevs@FiberDevs·Aug 6

🚴 Fiber Dev Log 34 🚴 v0.9.0 is live 🟢 After weeks of release hardening, the final milestone cleanup is complete, and Fiber v0.9.0 is released, making nodes more reliable, recoverable, and easier to operate. Highlights: - A unified database migration system with backup and restore support - Stronger payment recovery with Cross-Chain Hub improvements - More reliable reconnect and channel recovery flows - Smoother node onboarding with new install and quick-start scripts Full dev log: github.com/nervosnetwork/fib…

Common Knowledge Base Association (CKBA) avatar
⟳ tea retweeted
Common Knowledge Base Association (CKBA)@ckba_build·Aug 6

The payments industry is arriving at a shared conclusion, and it is worth stating plainly: the digital economy needs faster, smaller, more frequent, and more flexible ways to move value than either legacy rails or individual onchain transactions can provide. Look at what is being built. Circle Gateway offers gas-free USDC nanopayments through offchain authorizations and batched settlement. Stripe and Bridge are building stablecoin infrastructure for payments, payouts, treasury, and global money movement. Tempo’s MPP Sessions let customers pay continuously through offchain vouchers, while x402 gives applications and agents an open standard for requesting payments over the internet. Different projects, different approaches, one direction: more value is moving offchain, into smaller and more programmable payment flows. Fiber belongs to this movement, but tackles a different layer of the problem. x402 and MPP help software request and authorize payments. Tempo makes repeated payments inside a bilateral service relationship more efficient. Circle and Stripe make stablecoin payments operationally convenient through managed infrastructure. Fiber is building the open network those payments can travel through. Rather than requiring a separately funded relationship with every recipient, Fiber routes payments through shared network liquidity. Anyone can connect, run a node, provide liquidity, route payments, or build applications on top—and payers can reach recipients across the network without opening a direct channel with each one. The simplest way to understand Fiber: Connect to the network. Pay across it. Read how Fiber routes value, what open payment infrastructure changes, and what becomes possible when payments become programmable 👇 nervos.org/knowledge-base/fi…

Post attachment