<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>CKB Talk Radar Daily Brief</title>
  <link>https://chainte.github.io/ckb-talk-radar/</link>
  <description>Daily Nervos Talk community briefing and latest active topics.</description>
  <language>zh-cn</language>
  <lastBuildDate>Tue, 28 Apr 2026 17:10:24 +0000</lastBuildDate>
  <atom:link href="https://chainte.github.io/ckb-talk-radar/rss.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>CKB Talk Daily Brief - 2026-04-29</title>
    <link>https://chainte.github.io/ckb-talk-radar/</link>
    <guid>tag:ckb-talk-radar,2026-04-28:daily-brief</guid>
    <pubDate>Tue, 28 Apr 2026 18:16:18 +0000</pubDate>
    <description>None</description>
  </item>
  <item>
    <title>Introducing CKB Kickstarter: Decentralized All-or-Nothing Crowdfunding on Nervos CKB (Testnet MVP Live) (1 posts)</title>
    <link>https://talk.nervos.org/t/introducing-ckb-kickstarter-decentralized-all-or-nothing-crowdfunding-on-nervos-ckb-testnet-mvp-live/10130</link>
    <guid>https://talk.nervos.org/t/introducing-ckb-kickstarter-decentralized-all-or-nothing-crowdfunding-on-nervos-ckb-testnet-mvp-live/10130#recent-1</guid>
    <pubDate>Tue, 28 Apr 2026 17:10:24 +0000</pubDate>
    <description>Update: Automatic Finalization Bot live on testnet Following up on the v1.1 update above: the bot is deployed and end-to-end verified on testnet as of yesterday (2026-04-27). The platform is now fully trustless on testnet, campaigns flow create → pledge → deadline → distribution with zero manual intervention from anyone (creator, backer, or platform operator). What the bot does (each polling cycle, every 10s): Detects expired campaigns still in Active status → submits permissionless finalizeCampaign tx (Success if total pledged ≥ goal, Failed otherwise) For finalized Success campaigns with remaining live pledge cells → submits permissionlessRelease tx (funds → creator) For finalized...</description>
  </item>
  <item>
    <title>Spark Program | Nervos Brain - A Global Developer Onboarding Engine and Cross-Language Hub Powered by Agentic RAG (3 posts)</title>
    <link>https://talk.nervos.org/t/spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag/9995</link>
    <guid>https://talk.nervos.org/t/spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag/9995#recent-3</guid>
    <pubDate>Tue, 28 Apr 2026 14:03:27 +0000</pubDate>
    <description>第七周周报 一、本周目标（工具闭环与评测基线周） 本周承接第六周“多轮可持续交互”阶段的工作，重点从“机制已经具备”推进到“关键路径真正闭环、且后续可以被稳定评测”。核心目标有四个： 继续治理运行时日志噪音，补齐最小可观测性闭环。 让 discourse_query / github_search 从协议层定义走到图执行主路径可调用。 建立第一版多轮评测集，为后续 benchmark 和量化回归提供统一输入。 补齐 Telegram / Discord 两端在长消息与异常路径下的稳定性回归。 二、本周完成 日志治理与诊断视图补齐 已对常见第三方库日志进行了统一降噪处理，补充了 quiet_loggers 与 third_party_level 控制项，降低了测试和运行期的无关日志干扰。同时把工具执行过程的摘要信息接入到图状态与 trace_summary 中，使得一次回答至少可以追踪到“执行了哪些 tool、各自成功/为空/失败”的最小诊断视图，而不再只能看到最终回答文本。 工具执行闭环推进到运行时主路径 本周把 discourse_query 与 github_search 从“schema 已存在但主路径未接通”的状态推进到了可被 RetrieverPlanner -&gt; RetrievalExecutor -&gt; ToolRuntime 实际调用的状态。具体包括： RetrieverPlanner 归一化阶段已允许这两个 tool 保留，不再强制回退到 qdrant_search。 ToolRuntime 为二者补齐了 handler。 handler...</description>
  </item>
  <item>
    <title>Discontinuation of the DAO v1.1 project (1 posts)</title>
    <link>https://talk.nervos.org/t/discontinuation-of-the-dao-v1-1-project/10204</link>
    <guid>https://talk.nervos.org/t/discontinuation-of-the-dao-v1-1-project/10204#recent-1</guid>
    <pubDate>Tue, 28 Apr 2026 11:56:27 +0000</pubDate>
    <description>In consideration of Terry’s advice, the following updates are provided regarding the closure of DAO v1.1: Payment: The proposal team will retain the payment corresponding to the already‑delivered Milestone 1. Code: The code will remain open source and is accessible at this repository. A total of eight repositories encompass all code for the DAO v1.1 platform (excluding Web5 services, which are available here). Additionally, the community may access the open‑source vote auditor tool here. Contract: The voting contract deployed on the mainnet has been terminated, whereas the testnet voting contract continues to operate. The did:ckb contracts remain active on both the mainnet and the...</description>
  </item>
  <item>
    <title>Cellora — designing a production indexing and query service for CKB (feedback welcome) (1 posts)</title>
    <link>https://talk.nervos.org/t/cellora-designing-a-production-indexing-and-query-service-for-ckb-feedback-welcome/10199</link>
    <guid>https://talk.nervos.org/t/cellora-designing-a-production-indexing-and-query-service-for-ckb-feedback-welcome/10199#recent-1</guid>
    <pubDate>Tue, 28 Apr 2026 08:40:25 +0000</pubDate>
    <description>Just came across this thread and found it interesting, so I’ll try to offer a few suggestions. I think the honest answer is: For tx inclusion proofs, the practical first step is likely not Flyclient, but exposing CKB’s existing get_transaction_proof / verify_transaction_proof path through Cellora. That lets clients verify that a transaction is committed under a particular block header, rather than merely trusting Cellora’s indexed result. This easily moves Cellora from a purely trusted indexer toward an inclusion-verifiable indexer. For full historical / chain-tip trust minimisation, my narrower point is that I’m not sure there is a canonical Rust/TS wallet-side verifier package that app...</description>
  </item>
  <item>
    <title>Spark Program | CKB-VM Sail Formal Verification — Proving CKB-VM RISC-V Instruction Equivalence via Sail Specification and Coq Theorem Prover / CKB-VM Sail 形式化验证 — 基于 Sail 规范与 Coq 定理证明器的 CKB-VM RISC-V 指令等价性证明 (3 posts)</title>
    <link>https://talk.nervos.org/t/spark-program-ckb-vm-sail-formal-verification-proving-ckb-vm-risc-v-instruction-equivalence-via-sail-specification-and-coq-theorem-prover-ckb-vm-sail-sail-coq-ckb-vm-risc-v/10214</link>
    <guid>https://talk.nervos.org/t/spark-program-ckb-vm-sail-formal-verification-proving-ckb-vm-risc-v-instruction-equivalence-via-sail-specification-and-coq-theorem-prover-ckb-vm-sail-sail-coq-ckb-vm-risc-v/10214#recent-3</guid>
    <pubDate>Tue, 28 Apr 2026 03:13:16 +0000</pubDate>
    <description># [Spark Program] CKB-VM Sail Formal Verification — Proving CKB-VM RISC-V Instruction Equivalence via Sail Specification and Coq Theorem Prover / CKB-VM Sail 形式化验证 — 基于 Sail 规范与 Coq 定理证明器的 CKB-VM RISC-V 指令等价性证明 -– ## English Version ### 1. Project Name and Summary **Project Name:** ckb-vm-sail-verify **One-line Summary:** Formally verify that CKB-VM’s RISC-V instruction execution semantics are mathematically equivalent to the official Sail RISC-V specification, using Coq theorem proofs and differential testing as dual verification. ### 2. Team / Individual Introduction **Applicant:** Tinyueng ([GitHub](TinyuengKwan (Tinyueng) · GitHub)) **Core Competencies:** Currently interning at PLCT...</description>
  </item>
  <item>
    <title>Spark Program: Mini-Grant Initiative (1 posts)</title>
    <link>https://talk.nervos.org/t/spark-program-mini-grant-initiative/8752</link>
    <guid>https://talk.nervos.org/t/spark-program-mini-grant-initiative/8752#recent-1</guid>
    <pubDate>Mon, 27 Apr 2026 21:19:29 +0000</pubDate>
    <description>由于论坛已经全面接入AI翻译工具 后续Spark项目的提案、周更新、总结等在Nervos Talk沉淀的内容，不再强制要求双语版本 Zhouzhou On Behalf of the Spark Committee</description>
  </item>
</channel>
</rss>
