<?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, 12 May 2026 17:24:20 +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-05-13</title>
    <link>https://chainte.github.io/ckb-talk-radar/</link>
    <guid>tag:ckb-talk-radar,2026-05-12:daily-brief</guid>
    <pubDate>Tue, 12 May 2026 18:55:00 +0000</pubDate>
    <description>## 今日发生了什么 今天社区论坛最热闹的是围绕 Rosen Bridge 集成提案的拨款结算出现分歧：协调员 zz_tovarishch 按新价格发放了 877 万 CKB 作为第一期里程碑付款 [S01]，但开发者 phroi 认为数额有误，质疑为何不沿用申请时约定的旧计价方式 [S02]，双方就"过渡政策"的适用边界展开多轮争辩 [S03, S04, S05, S06]。与此同时，Bitcoin Renegade 正式撤回了其 6 个月社区媒体推广提案 [S09]，表示要先与 Neon 讨论"双重策略"后再重新提交 [S09, S12]。 ## 重点话题 **Rosen Bridge 拨款计价争议持续发酵** — phroi 指出按原始申请比例计算，M1 应发约 631 万 CKB 而非 877 万 [S02]，zz_tovarishch 解释自 2025 年 10 月起实际执行已改用 CKB 新价格以缓解开发者汇率风险 [S03]；phroi 则搬出《过渡政策声明》和 CKBoost 先例反驳，强调该笔拨款应固定比例而非按新价结算 [S04, S06]，双方仍未达成一致 [S03, S04, S05, S06] **Bitcoin Renegade 撤回媒体推广提案** — 原本申请 6 万美元等值 CKB 的社区媒体 Campaign 提案 [S08]，经协调员确认流程后 [S07]，提案人主动声明撤回 [S09]，打算 refine 方向（考虑加入丹佛本地 meetup 或 Rare Evo 类似活动）[S12]，后续将重开新帖申请 [S10, S12]...</description>
  </item>
  <item>
    <title>[DIS] CKB Integration for Rosen Bridge (9 posts)</title>
    <link>https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756</link>
    <guid>https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756#recent-9</guid>
    <pubDate>Tue, 12 May 2026 17:24:20 +0000</pubDate>
    <description>M1 Payout https://explorer.nervos.org/transaction/0x0c59bdaedb9be76e4682c75a254dafc35713cbe136d158a444d18dfa5b96c3dc 8,777,063 CKB (representing the 23% of full grants) Hey @zz_tovarishch &amp; Commission, thank you for the payment Just there seems to be a misunderstanding: x / 27,356,903 CKB = 15k USD / 65k USD ~ x = 27356903 CKB * 15 / 65 ~ x = 6,313,131 CKB Please, could you double check this? If you can confirm, could you give us guidance on what should be done about these additional 8,777,063 - 6,313,131 = 2,463,932 CKB ? Sending them back should be doable, allocating them towards the next Milestone is doable too, no trouble on our side Phroi Hi...</description>
  </item>
  <item>
    <title>[DIS] Bitcoin Renegade CKB Media Campaign (6 posts)</title>
    <link>https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239</link>
    <guid>https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239#recent-6</guid>
    <pubDate>Tue, 12 May 2026 14:57:43 +0000</pubDate>
    <description>Hi Bitcoin_Renegada, 想跟你确认一下，目前这份提案，你是已经决定撤回，不在继续申请流程了吗？亦或者是你修改了它（看到有修改记录），继续进行申请？ 因为这涉及我作为协调员，对流程进行同步以及给DAO委员会提醒，感谢你的回复 Grant Proposal: 6-Month Community Media Campaign Submitted by: Bitcoin Renegade Proposal Overview My name is Bitcoin Renegade, a crypto content creator, blockchain marketer, and long-time community advocate focused on educating audiences, driving adoption, and building strong communities within Web3. Through my Bitcoin Renegade YouTube channel, I have consistently covered blockchain ecosystems through livestreams, educational content, interviews, and community engagement. My focus is creating authentic content that turns awareness into adoption and keeps communities...</description>
  </item>
  <item>
    <title>A New Chapter for CKB: Introducing the Common Knowledge Base Association (2 posts)</title>
    <link>https://talk.nervos.org/t/a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association/10249</link>
    <guid>https://talk.nervos.org/t/a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association/10249#recent-2</guid>
    <pubDate>Tue, 12 May 2026 12:35:28 +0000</pubDate>
    <description>ckbaann1920×1080 385 KB From the beginning, CKB has been guided by a simple principle: a truly decentralized network should not depend on any single person, group, or organization to survive and thrive. Blockchains are public infrastructure—open, permissionless systems designed to outlive the inventors, teams and companies that help bring them into existence. They evolve through the collective efforts of communities, adapting as new contributors, ideas, and technologies emerge. To reach their full potential, these systems require room to grow without unnecessary constraints. Today, we take a deliberate step toward that vision. Formation of the Common Knowledge Base Association The Common...</description>
  </item>
  <item>
    <title>关于 `ccc/fiber-sdk` 的一些想法和进展 (1 posts)</title>
    <link>https://talk.nervos.org/t/ccc-fiber-sdk/10126</link>
    <guid>https://talk.nervos.org/t/ccc-fiber-sdk/10126#recent-1</guid>
    <pubDate>Tue, 12 May 2026 12:01:32 +0000</pubDate>
    <description>github.com/nervosnetwork/fiber-docs feat: fiber example game adaptation for fiber-sdk and recent fiber updates catch-up master ← ashuralyk:master 已打开 11:58AM - 12 May 26 UTC ashuralyk +2768 -2788 fiber has upgraded into v0.8.1, however, the example game is still behind with e…arlier version, by the way, `fiber-sdk` has been upgraded to v0.8.1 as well 我重新提交了新的 PR，根据之前的 PR 的反馈，再加上 fiber-sdk 已经更新到了最新的 0.8.1 版本，所以重新提交了新的更新</description>
  </item>
  <item>
    <title>Discussion about an alternative to the protocol treasury (5 posts)</title>
    <link>https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246</link>
    <guid>https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246#recent-5</guid>
    <pubDate>Tue, 12 May 2026 10:28:57 +0000</pubDate>
    <description>jimi-winehouse: the solution I am proposing is to activate the treasury and just make it centralized and focus on high impact projects. Taking a year of work to decentralize a treasury is resource mismanagement. I actually wouldn’t have too much of a problem with the Foundation managing the treasury in the early days, but that was never the plan and I don’t think this can even happen. But even if it was possible, I doubt they would even want to do it, you can imagine how every single CKB they spent would be endlessly questioned and argued about by everyone, it would be a nightmare. jimi-winehouse: The whole dilution thing is a meme I don’t think anyone is even talking about or worried...</description>
  </item>
  <item>
    <title>[DIS] Decentralized privacy order-book appchain based on CKB L1 - 2026.phase-1 (1 posts)</title>
    <link>https://talk.nervos.org/t/dis-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1/10015</link>
    <guid>https://talk.nervos.org/t/dis-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1/10015#recent-1</guid>
    <pubDate>Tue, 12 May 2026 09:02:23 +0000</pubDate>
    <description>M1 Payout https://explorer.nervos.org/transaction/0x88241cad0617d2ca5f1482217d557c89ea34429c55c61cf1cf34e637e412c286 3,127,036 CKB (representing the 20% of full grants)</description>
  </item>
  <item>
    <title>[DIS] Mobile-Ready CKB Light Client (Pocket Node) for Android (1 posts)</title>
    <link>https://talk.nervos.org/t/dis-mobile-ready-ckb-light-client-pocket-node-for-android/9879</link>
    <guid>https://talk.nervos.org/t/dis-mobile-ready-ckb-light-client-pocket-node-for-android/9879#recent-1</guid>
    <pubDate>Tue, 12 May 2026 08:59:43 +0000</pubDate>
    <description>M3 Payout https://explorer.nervos.org/transaction/0x03274cedea0cc5c39bcf669ad4d238d21e52267e9ee8ac60194ae6cbb730cb16 2,198,697 CKB (representing the 22.5% of full grants)</description>
  </item>
  <item>
    <title>Pre-RFC Discussion: Activating the Nervos DAO Treasury (1 posts)</title>
    <link>https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143</link>
    <guid>https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143#recent-1</guid>
    <pubDate>Tue, 12 May 2026 07:51:06 +0000</pubDate>
    <description>chenyukang: The use of the treasury funds will be fully open, transparent, and verifiable on-chain for everyone to see. Will this be user-friendly, will it be easy for a non-technical person to understand what’s going on? chenyukang: the governance protocol could direct the treasury to burn unused funds Can you elaborate? Does this mean that the community will have to vote to burn these funds or will this happen automatically?</description>
  </item>
  <item>
    <title>Is there any good reason for allowing hidden profiles? (1 posts)</title>
    <link>https://talk.nervos.org/t/is-there-any-good-reason-for-allowing-hidden-profiles/10243</link>
    <guid>https://talk.nervos.org/t/is-there-any-good-reason-for-allowing-hidden-profiles/10243#recent-1</guid>
    <pubDate>Tue, 12 May 2026 07:04:15 +0000</pubDate>
    <description>感谢各位的反馈，我觉得有道理。已经关掉了这个设置 allow_users_to_hide_profile 以前设置的值是论坛系统的默认，我们之前其实没有做任何设计。</description>
  </item>
  <item>
    <title>Fiber Desktop — run Fiber (FNN) on your laptop without the “public node” headache (2 posts)</title>
    <link>https://talk.nervos.org/t/fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache/10247</link>
    <guid>https://talk.nervos.org/t/fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache/10247#recent-2</guid>
    <pubDate>Tue, 12 May 2026 01:36:19 +0000</pubDate>
    <description>Hi everyone, If you follow Nervos, you may have heard of Fiber — a way to move value quickly on top of CKB using channel-style payments, routing, and invoices. To use it, you normally need a small program running in the background: the official Fiber Network Node (often called fnn). That program is the “engine” that opens channels, listens for payments, and creates invoices. The awkward part is not the idea of Fiber. It is where that engine is supposed to live. Many people end up looking at rented servers, router settings, always-on home machines, and security checklists just to feel like they can participate. That is a lot of work for something that should feel closer to “install an app...</description>
  </item>
  <item>
    <title>Spark Program | Nervos Brain - A Global Developer Onboarding Engine and Cross-Language Hub Powered by Agentic RAG (1 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-1</guid>
    <pubDate>Mon, 11 May 2026 19:14:06 +0000</pubDate>
    <description>第九周周报 一、本周目标 本周重点承接 Telegram 群内测反馈，继续修复真实使用中暴露出来的回答质量、检索覆盖、消息格式和部署可复现问题。 相比第八周，本周不再只关注“Bot 能否在群里稳定跑起来”，而是进一步关注： 面向真实用户问题时，Agent 是否会主动检索足够资料。 技术教程是否能优先使用现成框架和真实 API，而不是给出空泛 TODO。 Telegram / Discord 长回复、代码块、链接和引用格式是否稳定。 模型路由是否过于保守，是否需要更多 medium/high 档参与复杂任务。 检索数据和 Qdrant 数据库是否能被其他人快速重建和部署。 二、本周完成 2.1 Telegram Markdown 长消息格式修复 本周修复了 Telegram 长回答在分段发送时容易破坏 Markdown 格式的问题。 之前系统主要依赖 MarkdownV2 字符串切分，长代码块或复杂格式在接近 Telegram 4096 字符限制时容易被硬切，导致代码块、链接、引用等格式错乱。 本周改为使用 telegramify-markdown，将 Markdown 转成 Telegram Bot API 的 text + entities 结构，再按实体边界安全分段发送。这样 Telegram 端不再主要依赖 parse_mode=MarkdownV2，长回复中的代码块、标题、列表、链接、引用和中英文混排都更稳定。 同时保留了 plain text fallback：如果 Telegram 发送 entities 失败，会移除 entities 和...</description>
  </item>
</channel>
</rss>
