r/NervosNetwork

A New Chapter for CKB

A New Chapter for CKB

https://preview.redd.it/fwr15uov5p0h1.png?width=1920&format=png&auto=webp&s=6727aafad6dcac15606687abb7c3340d4e07f205

Today, we’re announcing the establishment of the Common Knowledge Base Association (CKBA): a Swiss Verein registered in Baar, Switzerland, created to serve as the new coordination layer for the CKB ecosystem.

This marks the natural progression of the Nervos Foundation into a more durable, participatory, and contributor-driven structure.

The people, the mission, and the commitment to CKB remain the same.

What changes is the structure around that work.

For years, the Foundation model helped steward CKB through a period of regulatory uncertainty, where separation between the network, its founders, contributors, and coordinating entities was necessary.

That distance served an important purpose: it gave CKB room to mature as neutral and resilient public infrastructure.

Over time, however, it also became a source of operational friction.

Today, the circumstances have changed.

Both CKB and the broader regulatory landscape have matured, creating the opportunity to bring the teams and people who have spent the last eight years contributing to CKB into a more aligned structure.

CKBA is that structure.

It is a membership-based, contributor-driven non-profit association with two membership tiers:

  • General Members can participate in the Association’s activities and meetings.
  • Contributing Members have formal governance rights, including voting and electing the Board.

Importantly, this does not change CKB itself.

CKB remains a permissionless and neutral network governed by its own PoW consensus rules and maintained by independent participants across the ecosystem.

CKBA does not own or control CKB. Its role is to support contributors and improve coordination around CKB’s long-term development, adoption, and resilience.

If you have been contributing to CKB, join us 👇

https://www.ckba.build/

This is not a reinvention of CKB.

It is the next stage in its evolution.

Read the full announcement on Nervos Talk: https://talk.nervos.org/t/a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association/10249

reddit.com
u/Mysterious-Ask-835 — 2 days ago

CKB Open Community Meeting” “CKB Open Q&A Session”

I believe CKB needs to hold an open and direct discussion session, with a clear commitment to answering all questions honestly and transparently. There are many rumors and unanswered concerns circulating, yet there are no direct responses that clarify the situation for investors and the community.

Among the most important questions many investors have are:

  1. What is the real current state of CKB? And what are the actual challenges facing the project today?

  2. What is CKB’s future plan? Is there a clear roadmap with measurable and achievable goals?

  3. Does CKB intend to build actual companies, products, and applications on top of the network, or will it remain focused only on building the base layer and leave everything else to the community?

  4. Did the Force Bridge hack truly damage the confidence of partners and investors? Were there any companies or projects that left because of that incident?

  5. Did Cipher Wang’s departure contribute to worsening some of the project’s issues, or weaken its leadership and media presence?

  6. CKB clearly suffers from a liquidity problem, and this is not something ordinary users can solve. So what is the realistic plan to address this issue? Are there any efforts to secure partnerships, attract market makers, or bring institutional liquidity?

  7. Is CKB truly ready for the wave of AI Agents and smart payment systems, or is it still behind and at risk of missing the opportunity?

  8. The marketing and media presence of CKB is extremely weak compared to other projects. In fact, its visibility is among the weakest of well-known blockchain networks. How does CKB plan to solve this problem? Is there a real strategy to improve media presence and communication with the market?

  9. How does CKB view real adoption? Are there clear goals to attract actual users, companies, and projects instead of focusing only on technical development?

These questions — and many others — deserve honest and transparent answers, because clarity and transparency are what build trust, especially for long-term projects.

Best regards.

reddit.com
u/Agile-Eye6172 — 7 days ago

The CKB Bi-Weekly

https://preview.redd.it/z3he0zz8lh0h1.jpg?width=1200&format=pjpg&auto=webp&s=185f16da06c03793d78079fdc188dad3de099d4d

CKB Ecosystem Biweekly Update #16

Welcome to the latest CKB Ecosystem Biweekly Update. Here’s a quick summary of key dev and ecosystem progress from the past two weeks.

Infrastructure; Tooling

Web5; DAO;

Ecosystem Projects; Community;

Nervos Community Catalyst

Spark Program

Every step forward in CKB is powered by the community. Let’s keep building!

Thanks to u/JackyLHH for his contribution to the edition of the bi-weekly report.

reddit.com
u/djminger007 — 3 days ago

ByteRent early stage CKB leasing protocol

A couple weeks ago I began working on a protocol that enables the Onchain leasing/renting of CKB. This is an initial attempt at implementing the long theorised concept of byte leasing on Nervos.

Each CKB on Nervos is literally one byte of on-chain storage. ByteRent turns that fungibility into a market: anyone holding unused CKB can publish a listing, and anyone needing short-term on-chain storage can lease it in discrete amounts. Settlement is upfront; the lessor is paid in full at FillLease; the principal returns to them at ExpireReturn once the lock script's absolute-epoch sincegate fires.

This release is a POC while not yet fully usable as a genuine leasing mechanism it establishes a pathway towards this. This on chain leasing service will create an avenue for agentic/autonomous acquisition of CKB for a range of purposes.

https://byterent.xyz

https://github.com/toastmanAu/byterent

https://github.com/toastmanAu/byterent-ui

u/aintLifeaBTC — 6 days ago

The Fiber Network AMA

https://preview.redd.it/0un30m6hw2zg1.png?width=1928&format=png&auto=webp&s=823eb98ceed3128a9fdb9a74769df2ae5b354b5c

12th May 11 GMT on Reddit

Hello, ladies and gentlemen of the CKB variety. Another Nervos community AMA is rolling out on May 12th, and this time it’s with one of CKB’s DevRel engineers Retric.

Retric is focused on documentation and developer tooling for the CKB ecosystem. Recently, he has been exploring community-driven experiments around the Fiber Network (CKB’s private, interoperable, multi-asset payment channel network), including projects such as Fiber Audio Player and Fiber L402 blog prototype. These demonstrate a paywalled publishing architecture powered by the Fiber Network.

The Fiber Audio Player is a lightweight demo app that puts the idea into practice, showing how content access can be gated behind a Fiber payment flow.

The Fiber L402 blog prototype explores a paywalled publishing model using L402-style authentication patterns, paired with Fiber as the payment rail, to unlock posts once payment conditions are met.

Links: https://talk.nervos.org/u/retricsu/summary

Got any questions for Retric about CKB, developer tooling, or building paywalled experiences on Fiber? Drop them below ahead of time, and join us live on May 12th for the AMA.

reddit.com
u/djminger007 — 10 days ago

New Community DAO proposal- Quantir Risk Intelligence for CKB Ecosystem and Cross-Chain Monitoring

This proposal in in the first discussion stage. Have a look. If its something you want to see moved ti the vote stage give it a ♥️. 30 are needed to move it forward or feel free to question and challenge the OP in the reply section if you want more clarity from them. https://talk.nervos.org/t/dis-quantir-risk-intelligence-for-ckb-ecosystem-and-cross-chain-monitoring/10218

Quantir proposes to build a CKB-aware risk intelligence and monitoring layer for the Nervos ecosystem. The system will monitor selected public CKB ecosystem activity, detect abnormal behavior, compute normalized risk signals, and deliver explainable alerts for developers, ecosystem operators, dashboards, and community monitoring workflows.

Quantir is an existing DeFi and on-chain risk monitoring platform with live collectors, transaction monitoring, risk scoring, alert delivery, API/WebSocket interfaces, and explainability services. This proposal adapts the existing Quantir architecture to CKB-specific ecosystem signals rather than building a monitoring system from scratch.

Requested budget: $30,000 equivalent in CKB.
Estimated duration: 10 weeks.
Payment structure: milestone-based.

Project Motivation
CKB is a flexible and interoperable Layer 1 with a unique Cell model, xUDT/token capabilities, cross-chain potential, Bitcoin-related infrastructure, payment-channel development, and a growing application ecosystem. This flexibility is valuable, but it also makes ecosystem monitoring harder.

Developers and operators can inspect raw activity through explorers, dashboards, and individual tools, but there is no unified layer that turns ecosystem activity into structured, explainable risk signals. Important conditions such as unusual token flows, bridge-related stress, abnormal contract or cell activity, liquidity pressure, payment-channel anomalies, or DAO fund-flow risks may be noticed only after they become obvious.

Quantir aims to provide earlier and clearer visibility by converting fragmented public signals into normalized scores, alerts, and explanations.

Proposal Overview
Quantir will build a CKB-specific monitoring module focused on public ecosystem signals. The system will collect and normalize selected CKB activity, detect abnormal patterns, score risk conditions, and generate alerts that can be consumed by dashboards, bots, APIs, or ecosystem monitoring tools.

The proposed module will focus on:

CKB ecosystem activity monitoring.
xUDT/token-flow anomaly detection.
Bridge and cross-chain activity monitoring.
CKB DeFi and liquidity-risk signals.
Abnormal contract/cell activity detection.
DAO/community fund activity monitoring.
Fiber/payment-channel risk signals where public data is available.
API/WebSocket-ready alert outputs.
Human-readable explanations for risk events.
Validation examples and technical documentation.

This work will not modify CKB consensus, CKB-VM, core protocol code, or wallet infrastructure. It will operate as an external monitoring and intelligence layer using public or reviewable ecosystem signals.

Technical Approach
The implementation will reuse Quantir’s existing multi-service architecture and adapt it to the Nervos ecosystem.

Core components:

Data ingestion layer
Collects selected public CKB ecosystem signals, including token activity, contract/cell behavior, DAO-related activity, DeFi signals, bridge-related events, and other supported public data sources.

Signal normalization layer
Transforms raw activity into comparable risk features such as flow intensity, concentration, repeated address patterns, abnormal activity spikes, liquidity changes, and risk-score deltas.

Risk scoring layer
Computes normalized risk scores and score changes for monitored entities.

Strategy layer
Detects abnormal activity patterns and triggers alert conditions.

Explanation layer
Generates human-readable explanations describing why an alert was triggered, what evidence supports it, and what changed.

Delivery layer
Outputs structured alert payloads suitable for APIs, WebSocket streams, dashboards, and bots.

Example alert output:

Alert category: xUDT flow anomaly
Severity: medium
Risk score: 71
Reason codes: sudden transfer spike, repeated address pattern, abnormal concentration
Evidence: transaction hashes, token identifier, addresses, timestamps
Explanation: “This token activity was flagged because transfer frequency increased sharply while repeated address patterns and concentrated flows appeared within the same monitoring window.”

Deliverables
CKB-specific monitoring scope and architecture document.
Public signal taxonomy for CKB ecosystem risk.
Structured alert schema.
CKB-aware ingestion prototype.
Risk scoring and anomaly detection logic.
Explainable alert generation.
API/WebSocket-ready output format.
Reference consumer or integration example.
At least 5 alert categories.
At least 10 sample alert scenarios.
Setup guide and testing documentation.
Final validation report.

Key Performance Indicators
At least 5 CKB-specific risk categories documented.
At least 10 sample alert scenarios produced.
Working prototype that generates structured CKB ecosystem alerts.
Alerts include severity, score, reason codes, evidence, and explanation.
Reference consumer can read or display alert outputs.
Documentation allows reviewers or developers to understand and test the prototype.
At least 3 validation examples completed.
Final report delivered to the Nervos community.

Milestones and Timeline
Total duration: 10 weeks.

Milestone 1: Scope, CKB Signal Taxonomy, and Architecture
Timeline: Weeks 1-2
Funding requested: $6,000 equivalent in CKB

Deliverables:
CKB-specific monitoring scope.
Public data-source mapping.
Risk category taxonomy.
Initial alert schema.
Technical architecture document.
Implementation plan.

Success criteria:
At least 5 risk categories are defined.
Initial alert schema is complete.
Data-source assumptions and technical scope are documented.

Milestone 2: Ingestion Prototype and Normalized Risk Signals
Timeline: Weeks 3-5
Funding requested: $9,000 equivalent in CKB

Deliverables:
CKB-aware ingestion prototype.
Normalized signal generation.
Initial scoring logic.
Sample alert generation.
Basic test coverage for core signal processing.

Success criteria:
Prototype can process selected public CKB ecosystem signals.
Structured alerts are generated from sample or public data.
At least 5 alert categories are implemented in sample form.

Milestone 3: Explainable Alerts and Integration Outputs
Timeline: Weeks 6-8
Funding requested: $8,000 equivalent in CKB

Deliverables:
Explanation logic for alert events.
API/WebSocket-ready alert format.
Reference consumer or integration example.
Sample documentation for external consumers.

Success criteria:
Alerts contain severity, score, evidence, reason codes, and explanation.
Reference integration can consume alert outputs.
Documentation explains how ecosystem tools can use the outputs.

Milestone 4: Validation, Documentation, and Final Delivery
Timeline: Weeks 9-10
Funding requested: $7,000 equivalent in CKB

Deliverables:
At least 3 validation examples.
At least 10 sample alert scenarios.
Final setup guide.
Testing guide.
Final technical report.
Public or reviewable repository with schemas, prototype code, examples, and documentation.

Success criteria:
Reviewers can inspect or run the prototype.
All milestone deliverables are documented.
Final report summarizes results, limitations, and recommended next steps.

Budget
Total funding requested: $30,000 equivalent in CKB.

Budget breakdown:

Engineering and CKB-specific integration: $12,000
Risk signal design and scoring logic: $5,000
API/WebSocket-ready outputs and reference integration: $4,000
Validation, testing, and documentation: $4,000
Infrastructure, data access, storage, and monitoring: $3,000
Grant reporting and contingency: $2,000

Payment structure: milestone-based.
Suggested initial payment: 20% of total budget, with the remaining amount distributed after milestone review.

Team
The project will be delivered by the Quantir core team.

Ilya Berdar — Senior Blockchain Developer / Project Lead
Responsible for technical architecture, CKB integration scope, risk engine adaptation, grant communication, and final delivery.

Andriy Boichuk — Senior Software Developer
Responsible for backend services, data ingestion, infrastructure, normalization logic, tests, and deployment workflows.

Alex Grishenko — Senior Software Developer
Responsible for alert schemas, explanation outputs, reference integration, documentation, validation examples, and product implementation.

Relevant Links
Quantir landing page: https://landing.quantirintelligence.com/
Quantir app: https://app.quantirintelligence.com/
Quantir GitHub repository: https://github.com/quantirintelligence/quantir-risk-engine

Long-Term Plan
If the pilot is successful, Quantir can expand CKB ecosystem monitoring to additional applications, bridges, tokens, DAO fund flows, DeFi systems, and payment-channel infrastructure. The long-term goal is to provide an explainable risk intelligence layer that helps the Nervos ecosystem improve visibility, resilience, and integration readiness.

Additional Notes
Quantir’s differentiator is that it combines monitoring, scoring, explainability, and alert delivery in one workflow. It does not only show charts or raw events; it translates ecosystem behavior into actionable, interpretable, machine-readable outputs.

This proposal is implementation-focused and designed to deliver reusable monitoring infrastructure for the Nervos ecosystem.

u/kevtam515 — 9 days ago

Fiber Pulse Updates

https://preview.redd.it/2iw94g7nlh0h1.jpg?width=1066&format=pjpg&auto=webp&s=6304f5e5c4ba28272c2b1458bb323f8a80055158

Fiber Pulse Updates

The Linkdn Nervos Community Account is also a good place to follow this news and subscribe to email bulletin updates (link below)

The most exciting work happens when builders take the lead.

Fiber Link: From Prototype to Product-Ready

Fiber Link has published its latest product delivery report, marking its transition from an engineering prototype toward a product-ready, deployable release.

Built as an open-source tipping layer for online communities, Fiber Link lets users tip posts or replies directly from familiar forum interfaces (starting with Discourse), without requiring members to run their own Fiber nodes.

This milestone includes a video demo with comprehensive documentation for administrators and operators to deploy the service.

Fiber-Pay v0.2.5: Simplified Connect Flow & New Demos

Fiber Pay is a toolkit that allows AI agents to manage Fiber Network operations like opening channels and making payments. Its latest release introduces ConnectButton, a simplified way for frontend apps to connect to a Fiber browser node using passkey or password authentication with minimal setup.

This update also includes stability fixes for useFiberNode under React StrictMode, a refreshed browser-wallet demo with the new connect flow, and a quick-card demo showing payment integration and UI customization.

Decentralized AI Agent Calling Experiment via Fiber

Built on top of the latest Fiber-Pay release, this experiment explores a decentralized AI Agent calling platform. Users can invoke agents running on remote hardware from their browsers, with peer-to-peer payments, similar in experience to cloud-based agent services.

Key aspects include:

  • Instant Micropayments: L402-style payment flow currently with per-call pricing (currently 0.1 CKB on testnet) via Fiber.
  • Decentralized design: Agents are hosted by anonymous operators, reducing reliance on centralized APIs and allowing users to access the latest agent capabilities by updating their local clients.
  • Technical Implementation: Focuses on containerized agent runtime for isolation, the acpx library to support multiple agent types, and environment variable control to prevent sensitive API key leakage.
  • Try the Demo: https://calling-agent-kappa.vercel.app/
  • Check it out: Forum link

Spark Proposal: Dular—Mobile Money Stablecoin Wallet

Dular is a stablecoin wallet designed to bridge Fiber with the mobile money ecosystem. It replaces hex addresses with phone number identities and supports USSD access for feature phones. It leverages Fiber’s low-fee, native multi-asset channels to enable instant payments, with integrated M-Pesa on/off ramps.

  • Status: Additional evidence and documentation submitted; currently under committee review.
  • Check it out: Forum link

Upcoming Reddit AMA on Fiber

The latest Nervos AMA focuses on the Fiber Network! Join us to chat with DevRel engineer Retric about his recent experiments with paywalled applications, including the Fiber Audio Player and L402 blog prototype.

Join the discussion or drop questions in advance here before May 12th at 11 GMT!

Got an idea? Let’s see it take shape.

Fiber Network is a community-driven ecosystem with real support behind its builders. If you’re thinking about building something, here is how we can help:

  • Spark Program: A fast-track path for early prototypes, offering up to $2,000 in funding to help turn ideas into working MVPs within 1–2 months.
  • CKB Community Fund: A DAO-backed grant program supporting a wide range of ecosystem work, from core development to tools, content, and community initiatives.

Share your idea on the Nervos Talk forum and reach out to the programs above. We’d love to see what you build show up in our next update!

reddit.com
u/djminger007 — 3 days ago

From Polycrypt:

Cross-chain DeFi between Ethereum and CKB is coming and is powered by Perun!

There will be liquidity pools on both chains with an integrated AMM. You will be able to deposit CKB or ETH and earn yield from cross-chain swaps.

We built smart contracts on both Ethereum and CKB that hold liquidity pools. You deposit assets on whichever chain you are on, earning fee revenue as soon as users swap assets between the chains, using the liquidity you provided.

Unlike most cross-chain bridges, no validator committees or trusted relays needed. Swaps are secured by Perun, our formally verified OSS state channel protocol. No additional setup or trust into intermediaries required. Swaps are settled on ETH and CKB smart contracts.

The AMM handles pricing, Perun channels handle settlement, and the contracts make sure LPs get their principal back plus fees. You deposit and earn. More updates are coming soon!

reddit.com
u/kevtam515 — 14 days ago