{
  "base_url": "https://talk.nervos.org",
  "generated_at": "2026-05-12T18:55:00.242384+00:00",
  "since": "2026-05-11T18:54:52.221584+00:00",
  "until": "2026-05-12T18:54:52.221584+00:00",
  "window_hours": 24,
  "topics": [
    {
      "topic_id": 9756,
      "title": "[DIS] CKB Integration for Rosen Bridge",
      "slug": "dis-ckb-integration-for-rosen-bridge",
      "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756",
      "created_at": "2025-12-23T22:59:15.907000+00:00",
      "last_posted_at": "2026-05-12T17:24:20.349000+00:00",
      "category_id": 65,
      "tags": [],
      "posters": [
        "Original Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24297,
          "post_number": 133,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T09:06:00.031000+00:00",
          "updated_at": "2026-05-12T09:06:00.031000+00:00",
          "reply_to_post_number": 115,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/133",
          "content_text": "M1 Payout\nhttps://explorer.nervos.org/transaction/0x0c59bdaedb9be76e4682c75a254dafc35713cbe136d158a444d18dfa5b96c3dc\n8,777,063 CKB (representing the 23% of full grants)",
          "content_html": "<p>M1 Payout</p>\n<p><a href=\"https://explorer.nervos.org/transaction/0x0c59bdaedb9be76e4682c75a254dafc35713cbe136d158a444d18dfa5b96c3dc\" class=\"onebox\" target=\"_blank\" rel=\"noopener\">https://explorer.nervos.org/transaction/0x0c59bdaedb9be76e4682c75a254dafc35713cbe136d158a444d18dfa5b96c3dc</a></p>\n<p>8,777,063 CKB (representing the 23% of full grants)</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24307,
          "post_number": 134,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "phroi",
          "created_at": "2026-05-12T15:24:38.411000+00:00",
          "updated_at": "2026-05-12T15:24:38.411000+00:00",
          "reply_to_post_number": 133,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/134",
          "content_text": "Hey @zz_tovarishch & Commission, thank you for the payment\nJust there seems to be a misunderstanding:\nx / 27,356,903 CKB = 15k USD / 65k USD\n~ x = 27356903 CKB * 15 / 65\n~ x = 6,313,131 CKB\nPlease, could you double check this?\nIf 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 ?\nSending them back should be doable, allocating them towards the next Milestone is doable too, no trouble on our side\nPhroi",
          "content_html": "<p>Hey <a class=\"mention\" href=\"/u/zz_tovarishch\">@zz_tovarishch</a> &amp; Commission, thank you for the payment <img src=\"https://talk.nervos.org/images/emoji/apple/folded_hands.png?v=15\" title=\":folded_hands:\" class=\"emoji\" alt=\":folded_hands:\" loading=\"lazy\" width=\"20\" height=\"20\"></p>\n<p>Just there seems to be a misunderstanding:</p>\n<p><code>x / 27,356,903 CKB = 15k USD / 65k USD</code><br>\n~ <code>x = 27356903 CKB * 15 / 65</code><br>\n~ <a href=\"https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/115\"><code>x = 6,313,131 CKB</code></a></p>\n<p>Please, could you double check this?</p>\n<p>If you can confirm, could you give us guidance on what should be done about these additional <code>8,777,063 - 6,313,131 = 2,463,932 CKB</code> ?</p>\n<p>Sending them back should be doable, allocating them towards the next Milestone is doable too, no trouble on our side</p>\n<p>Phroi</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24308,
          "post_number": 135,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T15:43:02.421000+00:00",
          "updated_at": "2026-05-12T15:56:12.511000+00:00",
          "reply_to_post_number": 134,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/135",
          "content_text": "Hi Phroi，CKB数量的差异是因为自25年10月以来，在实际执行中，打款都是按照CKB新的价格进行，一定程度上缓解价格波动对开发者的影响",
          "content_html": "<p>Hi Phroi，CKB数量的差异是因为自<a href=\"https://talk.nervos.org/t/dis-ckboost-gamified-community-engagement-platform-proposal/8832/23\">25年10月</a>以来，在实际执行中，打款都是按照CKB新的价格进行，一定程度上缓解价格波动对开发者的影响</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24309,
          "post_number": 136,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "phroi",
          "created_at": "2026-05-12T16:40:42.407000+00:00",
          "updated_at": "2026-05-12T16:40:42.407000+00:00",
          "reply_to_post_number": 135,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/136",
          "content_text": "zz_tovarishch:\nthe difference in CKB amount is because since October '25, in actual execution, payments have been made according to the new CKB price\nLinked CKBoost payment was a special case:\nTransitional Policy Statement (Community Fund DAO v1.1)\nV. Special Cases: Approved Proposals with Unfinished Milestones\nThere is one particularly important and complex issue that requires clarification:\nWhether already approved proposals can adopt stablecoin-based pricing.\nAt present, this situation mainly involves two projects: CKBoost and DAO v1.1.\nThis issue has been discussed internally at length and presents a genuine dilemma:\nAllowing stablecoin-based pricing would clearly violate Principle 1 (rule integrity)\nTaking no action at all could result in insufficient funding for these projects, potentially preventing completion, which would violate Principle 3\nVI. Temporary Off-Rule Solution (Personal Action Statement)\nAs this issue cannot be resolved within the existing rules, we can only seek a temporary solution outside the rule framework.\nOn a personal basis, I will:\nDonate a portion of CKB\nReach out to a small number of other donors to help alleviate the funding pressure faced by the above projects during the transitional period\nIt must be clearly stated that:\nThis is my personal action and does not form part of DAO rules\nThis action is limited in scope and responsibility\nThere is no guarantee it will be expanded\nThere is no guarantee it will fully offset the impact of price fluctuations\nIf the funds raised are insufficient, that outcome will have to be accepted\nAny surplus funds will be fully donated back to the DAO treasury\nAdditional clarifications:\nThis personal subsidy applies only to proposals that have passed final voting (Voting Stage) but have not yet been paid\nIt does not apply to new proposals submitted during the transitional period\nProjects with a strong requirement for stablecoin-based pricing are advised to wait until v1.1 officially goes live",
          "content_html": "<aside class=\"quote no-group quote-modified\" data-username=\"zz_tovarishch\" data-post=\"135\" data-topic=\"9756\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/zz_tovarishch/48/8925_2.png\" class=\"avatar\"> zz_tovarishch:</div>\n<blockquote>\n<p>the difference in CKB amount is because since <a href=\"https://talk.nervos.org/t/dis-ckboost-gamified-community-engagement-platform-proposal/8832/23\">October '25</a>, in actual execution, payments have been made according to the new CKB price</p>\n</blockquote>\n</aside>\n<p>Linked CKBoost payment was a special case:</p>\n<aside class=\"quote no-group\" data-username=\"terrytai\" data-post=\"1\" data-topic=\"9736\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/terrytai/48/327_2.png\" class=\"avatar\"><a href=\"https://talk.nervos.org/t/transitional-policy-statement-community-fund-dao-v1-1/9736/1\">Transitional Policy Statement (Community Fund DAO v1.1)</a></div>\n<blockquote>\n<h3><strong>V. Special Cases: Approved Proposals with Unfinished Milestones</strong></h3>\n<p>There is one particularly important and complex issue that requires clarification:</p>\n<p>Whether <strong>already approved proposals</strong> can adopt <strong>stablecoin-based pricing</strong>.</p>\n<p>At present, this situation mainly involves two projects: <a href=\"https://talk.nervos.org/t/dis-ckboost-gamified-community-engagement-platform-proposal/8832\">CKBoost</a> and <a href=\"https://talk.nervos.org/t/dis-community-fund-dao-v1-1-web5-community-fund-dao-v1-1-web5-optimization-proposal/8973\">DAO v1.1</a>.</p>\n<p>This issue has been discussed internally at length and presents a genuine dilemma:</p>\n<ul>\n<li>Allowing stablecoin-based pricing would clearly <strong>violate Principle 1</strong> (rule integrity)</li>\n<li>Taking no action at all could result in insufficient funding for these projects, potentially preventing completion, which would <strong>violate Principle 3</strong></li>\n</ul>\n<hr>\n<h3><strong>VI. Temporary Off-Rule Solution (Personal Action Statement)</strong></h3>\n<p>As this issue cannot be resolved within the existing rules, we can only seek a <strong>temporary solution outside the rule framework</strong>.</p>\n<p>On a personal basis, I will:</p>\n<ul>\n<li>Donate a portion of <strong>CKB</strong></li>\n<li>Reach out to a small number of other donors to help alleviate the funding pressure faced by the above projects during the transitional period</li>\n</ul>\n<p>It must be clearly stated that:</p>\n<ul>\n<li>This is <strong>my personal action</strong> and <strong>does not form part of DAO rules</strong></li>\n<li>This action is <strong>limited in scope and responsibility</strong>\n<ul>\n<li>There is no guarantee it will be expanded</li>\n<li>There is no guarantee it will fully offset the impact of price fluctuations</li>\n</ul>\n</li>\n<li>If the funds raised are insufficient, that outcome will have to be accepted</li>\n<li>Any surplus funds will be <strong>fully donated back to the DAO treasury</strong></li>\n</ul>\n<p>Additional clarifications:</p>\n<ul>\n<li>This personal subsidy <strong>applies only to proposals that have passed final voting (Voting Stage) but have not yet been paid</strong></li>\n<li>It <strong>does not apply to new proposals submitted during the transitional period</strong></li>\n<li>Projects with a strong requirement for stablecoin-based pricing are advised to <strong>wait until v1.1 officially goes live</strong></li>\n</ul>\n</blockquote>\n</aside>",
          "like_count": 0,
          "quote_count": 1
        },
        {
          "post_id": 24310,
          "post_number": 137,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T17:07:04.684000+00:00",
          "updated_at": "2026-05-12T17:09:28.007000+00:00",
          "reply_to_post_number": 136,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/137",
          "content_text": "Transitional Policy Statement (Community Fund DAO v1.1) 发布在2025年12月\n但CKBoost在2025年7月的申请中提出：\n[DIS] CKBoost Gamified Community Engagement Platform Proposal\nAmount requested: $20,000 USD (around 4635652.81 CKB at current price. Should use the latest price at the time of issuance)\n通过投票后，其两笔发生在2025年8月和2025年10月的打款，实际是采用的the latest price 计算CKB进行打款\n此后，多个项目在申请时均提出使用the latest price计算打款时的CKB数量，如Pocket Node 2026年2月\nimage2032×1228 380 KB\nInvisibook 2026年4月\nimage2038×546 62.6 KB\n且都通过了投票\n所以目前在实际操作中，各个项目的打款都进行了重新计算",
          "content_html": "<p><a href=\"https://talk.nervos.org/t/transitional-policy-statement-community-fund-dao-v1-1/9736\">Transitional Policy Statement (Community Fund DAO v1.1)</a> 发布在2025年12月</p>\n<p>但CKBoost在2025年7月的申请中提出：</p>\n<aside class=\"quote no-group\" data-username=\"Alive24\" data-post=\"1\" data-topic=\"8832\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/alive24/48/8777_2.png\" class=\"avatar\"><a href=\"https://talk.nervos.org/t/dis-ckboost-gamified-community-engagement-platform-proposal/8832/1\">[DIS] CKBoost Gamified Community Engagement Platform Proposal</a></div>\n<blockquote>\n<p>Amount requested: $20,000 USD (around 4635652.81 CKB at current price. Should use the latest price at the time of issuance)</p>\n</blockquote>\n</aside>\n<p>通过投票后，其<a href=\"https://talk.nervos.org/t/dis-ckboost-gamified-community-engagement-platform-proposal/8832/23\">两笔</a>发生在2025年8月和2025年10月的打款，实际是采用的the latest price 计算CKB进行打款</p>\n<p>此后，多个项目在申请时均提出使用the latest price计算打款时的CKB数量，如<a href=\"https://dao.ckb.community/thread/vot-mobile-ready-ckb-light-client-pocket-node-for-android-67494\">Pocket Node</a> 2026年2月<br>\n<div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://talk.nervos.org/uploads/default/original/2X/b/b666eff5b7633263d3db7dc8f34a53d2b597ea6e.png\" data-download-href=\"https://talk.nervos.org/uploads/default/b666eff5b7633263d3db7dc8f34a53d2b597ea6e\" title=\"image\"><img src=\"https://talk.nervos.org/uploads/default/optimized/2X/b/b666eff5b7633263d3db7dc8f34a53d2b597ea6e_2_690x416.png\" alt=\"image\" data-base62-sha1=\"q1Brow7FIHZJilzBEf7U9krW6nA\" width=\"690\" height=\"416\" srcset=\"https://talk.nervos.org/uploads/default/optimized/2X/b/b666eff5b7633263d3db7dc8f34a53d2b597ea6e_2_690x416.png, https://talk.nervos.org/uploads/default/optimized/2X/b/b666eff5b7633263d3db7dc8f34a53d2b597ea6e_2_1035x624.png 1.5x, https://talk.nervos.org/uploads/default/optimized/2X/b/b666eff5b7633263d3db7dc8f34a53d2b597ea6e_2_1380x832.png 2x\" data-dominant-color=\"2B2C2E\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">2032×1228 380 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p><a href=\"https://dao.ckb.community/thread/vot-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1-69184\">Invisibook</a> 2026年4月<br>\n<div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://talk.nervos.org/uploads/default/original/2X/5/52f98669669f4d6e5694e1edd4a98ac0c16b4d2a.png\" data-download-href=\"https://talk.nervos.org/uploads/default/52f98669669f4d6e5694e1edd4a98ac0c16b4d2a\" title=\"image\"><img src=\"https://talk.nervos.org/uploads/default/optimized/2X/5/52f98669669f4d6e5694e1edd4a98ac0c16b4d2a_2_690x184.png\" alt=\"image\" data-base62-sha1=\"bQ1KXUFsmihLfSImYHFZBpn1ko2\" width=\"690\" height=\"184\" srcset=\"https://talk.nervos.org/uploads/default/optimized/2X/5/52f98669669f4d6e5694e1edd4a98ac0c16b4d2a_2_690x184.png, https://talk.nervos.org/uploads/default/optimized/2X/5/52f98669669f4d6e5694e1edd4a98ac0c16b4d2a_2_1035x276.png 1.5x, https://talk.nervos.org/uploads/default/optimized/2X/5/52f98669669f4d6e5694e1edd4a98ac0c16b4d2a_2_1380x368.png 2x\" data-dominant-color=\"26272D\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">image</span><span class=\"informations\">2038×546 62.6 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>且都通过了投票<br>\n所以目前在实际操作中，各个项目的打款都进行了重新计算</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24311,
          "post_number": 138,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "phroi",
          "created_at": "2026-05-12T17:09:39.175000+00:00",
          "updated_at": "2026-05-12T17:09:39.175000+00:00",
          "reply_to_post_number": 135,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/138",
          "content_text": "Additionally, payment target is CKBoost is not last price, it was: Fixed Milestone Percentage in CKB + reimbursement of any loss inccurred to CKB price",
          "content_html": "<p>Additionally, payment target is CKBoost is not last price, it was: <em>Fixed Milestone Percentage in CKB + reimbursement of any loss inccurred to CKB price</em></p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24312,
          "post_number": 139,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "phroi",
          "created_at": "2026-05-12T17:12:25.785000+00:00",
          "updated_at": "2026-05-12T17:21:36.219000+00:00",
          "reply_to_post_number": 137,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/139",
          "content_text": "Now the issue is this:\nSonami:\nGrant Amount: $65,000 USD (CKB price: $0.002376; CKB requested: 27,356,903)\nNote how we did not specify equivalent value in CKB at the time of disbursement",
          "content_html": "<p>Now the issue is this:</p>\n<aside class=\"quote no-group\" data-username=\"Sonami\" data-post=\"1\" data-topic=\"9756\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/sonami/48/10369_2.png\" class=\"avatar\"> Sonami:</div>\n<blockquote>\n<p><strong>Grant Amount:</strong> $65,000 USD (CKB price: $0.002376; CKB requested: 27,356,903)</p>\n</blockquote>\n</aside>\n<p>Note how we did not specify <strong>equivalent value in CKB at the time of disbursement</strong></p>",
          "like_count": 0,
          "quote_count": 1
        },
        {
          "post_id": 24313,
          "post_number": 140,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "phroi",
          "created_at": "2026-05-12T17:19:05.348000+00:00",
          "updated_at": "2026-05-12T17:28:09.465000+00:00",
          "reply_to_post_number": 137,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/140",
          "content_text": "zz_tovarishch:\nTherefore, in current practice, the disbursements for each project have been recalculated accordingly.\nNope nope, that’s a MetaRule change in itself.\nAll this said:\nIf it’s opt-in, I don’t mind and it could indeed be beneficial.\nIf it’s forced upon DAO projects, I need to raise the question.\nPhroi",
          "content_html": "<aside class=\"quote no-group quote-modified\" data-username=\"zz_tovarishch\" data-post=\"137\" data-topic=\"9756\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/zz_tovarishch/48/8925_2.png\" class=\"avatar\"> zz_tovarishch:</div>\n<blockquote>\n<p>Therefore, in current practice, the disbursements for each project have been recalculated accordingly.</p>\n</blockquote>\n</aside>\n<p>Nope nope, that’s a MetaRule change in itself.</p>\n<p>All this said:</p>\n<ul>\n<li>If it’s opt-in, I don’t mind and it could indeed be beneficial.</li>\n<li>If it’s forced upon DAO projects, I need to raise the question.</li>\n</ul>\n<p>Phroi</p>",
          "like_count": 0,
          "quote_count": 1
        },
        {
          "post_id": 24314,
          "post_number": 141,
          "topic_id": 9756,
          "topic_title": "[DIS] CKB Integration for Rosen Bridge",
          "topic_slug": "dis-ckb-integration-for-rosen-bridge",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T17:24:20.349000+00:00",
          "updated_at": "2026-05-12T17:24:20.349000+00:00",
          "reply_to_post_number": 140,
          "url": "https://talk.nervos.org/t/dis-ckb-integration-for-rosen-bridge/9756/141",
          "content_text": "谢谢你的指正。后续会按照通过投票的项目的实际情况通知委员会打款。\n具体到CKB integration for Rosen Bridge, 这次多打的CKB数量，我会在下次需要打款时告知委员会减掉相应数额。",
          "content_html": "<p>谢谢你的指正。后续会按照通过投票的项目的实际情况通知委员会打款。</p>\n<p>具体到CKB integration for Rosen Bridge, 这次多打的CKB数量，我会在下次需要打款时告知委员会减掉相应数额。</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 10239,
      "title": "[DIS] Bitcoin Renegade CKB Media Campaign",
      "slug": "dis-bitcoin-renegade-ckb-media-campaign",
      "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239",
      "created_at": "2026-05-09T04:51:41.673000+00:00",
      "last_posted_at": "2026-05-12T14:57:43.638000+00:00",
      "category_id": 65,
      "tags": [],
      "posters": [
        "Original Poster, Most Recent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24284,
          "post_number": 33,
          "topic_id": 10239,
          "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign",
          "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T01:28:16.584000+00:00",
          "updated_at": "2026-05-12T01:31:47.454000+00:00",
          "reply_to_post_number": 31,
          "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/33",
          "content_text": "Hi Bitcoin_Renegada, 想跟你确认一下，目前这份提案，你是已经决定撤回，不在继续申请流程了吗？亦或者是你修改了它（看到有修改记录），继续进行申请？\n因为这涉及我作为协调员，对流程进行同步以及给DAO委员会提醒，感谢你的回复",
          "content_html": "<p>Hi Bitcoin_Renegada, 想跟你确认一下，目前这份提案，你是已经决定撤回，不在继续申请流程了吗？亦或者是你修改了它（看到有修改记录），继续进行申请？</p>\n<p>因为这涉及我作为协调员，对流程进行同步以及给DAO委员会提醒，感谢你的回复</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24286,
          "post_number": 34,
          "topic_id": 10239,
          "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign",
          "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign",
          "author": "Bitcoin_Renegade",
          "created_at": "2026-05-12T03:30:00.059000+00:00",
          "updated_at": "2026-05-12T03:30:00.059000+00:00",
          "reply_to_post_number": 33,
          "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/34",
          "content_text": "Grant Proposal: 6-Month Community Media Campaign\nSubmitted by: Bitcoin Renegade\nProposal Overview\nMy 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.\nThrough 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 engaged during key moments of ecosystem growth.\nI am seeking funding for a 6-month livestream media campaign** designed to increase ecosystem visibility, educate the community, and drive adoption through consistent livestream content and social media engagement.\nCampaign Deliverables\nOver six months I will deliver:\n*Livestream Content\n3 livestreams per month\n18 livestreams total\nDistributed on YouTube and X\nCoverage includes ecosystem updates, project spotlights, educational discussions, interviews, AMAs, ecosystem commentary, and community engagement\n*Social Media Promotion\nMinimum 2 supporting posts per month on X\n12+ posts total\nPromotional content, ecosystem highlights, and community engagement posts\nX: 3315 - https://x.com/bitcoinr3negade\nYouTube: 4607 - Bitcoin Renegade - YouTube\nWhy do you want to do this? (Why?)\nI want to do this because strong ecosystems need strong media presence. Community education, awareness, and consistent conversation are major drivers of adoption in Web3. Even the best technology needs advocates who can communicate its value, explain developments, and keep the broader community engaged.\nMy goal is to create recurring livestream content that educates audiences, highlights ecosystem developments, and helps bring new users into the ecosystem while keeping current community members informed and excited about what is being built.\nThis campaign is about turning visibility into adoption and strengthening long-term ecosystem momentum.\nWhy are you the right person to do it? (Why you?)\nI am the right person because I already actively do this work and have years of experience building communities and producing blockchain-focused content.\nMy qualifications include:\nFounder of Bitcoin Renegade\nEstablished YouTube creator and livestream host\nBlockchain marketer and crypto investment strategist\nParticipant in the Community Catalyst Program for approximately 8 months\nLed conferences and community events that helped drive adoption to Nervos\nExperience hosting interviews, AMAs, livestreams, and ecosystem discussions\nStrong relationships across Web3 communities and project founders\nAbility to communicate technical blockchain developments in a way that is understandable and engaging\nI bring both media experience and ecosystem knowledge, which positions me well to effectively represent and amplify important developments.\nWhy do you want to do it now? (Why now?)\nNow is the ideal time because the ecosystem is entering an important growth phase.\nWith developments like Fiber Network, continued progress in RGB++, expanding Bitcoin Layer 2 infrastructure, cross-chain innovation, and growing builder activity, there is increasing momentum that deserves consistent coverage and public discussion.\nThis is exactly when strong media support matters most—during moments of ecosystem acceleration.\nConsistent livestreams and community engagement can help:\nIncrease awareness of new developments\nEducate users on new tools and infrastructure\nHighlight builders and innovation\nBring in fresh attention from outside audiences\nStrengthen community confidence during key growth periods\nMomentum is building now, and this is the time to amplify it.\nWhat is the budget you are applying for? Why is it reasonable? (Budget)\nFunding Request: $500 per month for 6 months\nTotal Request: $3,000\nThis is a modest and reasonable budget considering the amount of consistent content being delivered.\nFor $500 monthly, I will provide:\n3 livestream broadcasts\n2+ supporting posts on X\nTopic research and preparation\nScheduling and outreach for guests/interviews when applicable\nSocial promotion and community engagement\nConsistent ecosystem coverage over a six-month period\nAt 18 livestreams + 12+ X posts, this provides efficient value compared to traditional marketing campaigns while offering direct community engagement and authentic ecosystem exposure.\nHow do you plan to do the work? (How?)\nThe work will be carried out through a consistent monthly content schedule over six months.\nEach month I will:\nHost 3 livestream broadcasts focused on ecosystem news, product updates, interviews, educational topics, and community discussions\nPublish at least 2 supporting posts on X to promote broadcasts, highlight important developments, and engage the wider community\nResearch ecosystem developments and prepare discussion topics for each stream\nInvite guests, builders, or community members when relevant to create valuable discussion\nEngage directly with the community through livestream chat, comments, and social media discussion\nMaintain consistent visibility around major ecosystem milestones, launches, and updates\nThis approach keeps content authentic, timely, and community-centered while creating a reliable media presence over the full six-month campaign.\nFinal Statement\nI have already invested years into building community, educating audiences, and supporting ecosystem growth. This grant would allow me to dedicate structured time and consistent energy toward amplifying one of the most exciting growth periods in the ecosystem.\nMy goal is simple: increase awareness, strengthen community, and help drive adoption through consistent media presence.\nSubmitted by: Bitcoin Renegade\nRequested Funding: $3,000\nBitcoin Renegade CKB Media Campaign Powerpoint",
          "content_html": "<p>Grant Proposal: 6-Month Community Media Campaign<br>\nSubmitted by: Bitcoin Renegade</p>\n<p>Proposal Overview<br>\nMy 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.</p>\n<p>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 engaged during key moments of ecosystem growth.</p>\n<p>I am seeking funding for a 6-month livestream media campaign** designed to increase ecosystem visibility, educate the community, and drive adoption through consistent livestream content and social media engagement.</p>\n<p>Campaign Deliverables<br>\nOver six months I will deliver:</p>\n<p>*Livestream Content</p>\n<ul>\n<li>3 livestreams per month</li>\n<li>18 livestreams total</li>\n<li>Distributed on YouTube and X</li>\n<li>Coverage includes ecosystem updates, project spotlights, educational discussions, interviews, AMAs, ecosystem commentary, and community engagement</li>\n</ul>\n<p>*Social Media Promotion</p>\n<ul>\n<li>Minimum 2 supporting posts per month on X</li>\n<li>12+ posts total</li>\n<li>Promotional content, ecosystem highlights, and community engagement posts</li>\n<li>X: 3315 - <a href=\"https://x.com/bitcoinr3negade\" rel=\"noopener nofollow ugc\">https://x.com/bitcoinr3negade</a></li>\n<li>YouTube: 4607 - <a href=\"https://youtube.com/@bitcoinrenegade?si=Qn0R7Yu_5YAVWZdA\" class=\"inline-onebox\" rel=\"noopener nofollow ugc\">Bitcoin Renegade - YouTube</a></li>\n</ul>\n<p>Why do you want to do this? (Why?)<br>\nI want to do this because strong ecosystems need strong media presence. Community education, awareness, and consistent conversation are major drivers of adoption in Web3. Even the best technology needs advocates who can communicate its value, explain developments, and keep the broader community engaged.</p>\n<p>My goal is to create recurring livestream content that educates audiences, highlights ecosystem developments, and helps bring new users into the ecosystem while keeping current community members informed and excited about what is being built.</p>\n<p>This campaign is about turning visibility into adoption and strengthening long-term ecosystem momentum.</p>\n<p>Why are you the right person to do it? (Why you?)<br>\nI am the right person because I already actively do this work and have years of experience building communities and producing blockchain-focused content.</p>\n<p>My qualifications include:</p>\n<ul>\n<li>Founder of Bitcoin Renegade</li>\n<li>Established YouTube creator and livestream host</li>\n<li>Blockchain marketer and crypto investment strategist</li>\n<li>Participant in the Community Catalyst Program for approximately 8 months</li>\n<li>Led conferences and community events that helped drive adoption to Nervos</li>\n<li>Experience hosting interviews, AMAs, livestreams, and ecosystem discussions</li>\n<li>Strong relationships across Web3 communities and project founders</li>\n<li>Ability to communicate technical blockchain developments in a way that is understandable and engaging</li>\n</ul>\n<p>I bring both media experience and ecosystem knowledge, which positions me well to effectively represent and amplify important developments.</p>\n<p>Why do you want to do it now? (Why now?)<br>\nNow is the ideal time because the ecosystem is entering an important growth phase.</p>\n<p>With developments like Fiber Network, continued progress in RGB++, expanding Bitcoin Layer 2 infrastructure, cross-chain innovation, and growing builder activity, there is increasing momentum that deserves consistent coverage and public discussion.</p>\n<p>This is exactly when strong media support matters most—during moments of ecosystem acceleration.</p>\n<p>Consistent livestreams and community engagement can help:</p>\n<ul>\n<li>Increase awareness of new developments</li>\n<li>Educate users on new tools and infrastructure</li>\n<li>Highlight builders and innovation</li>\n<li>Bring in fresh attention from outside audiences</li>\n<li>Strengthen community confidence during key growth periods</li>\n</ul>\n<p>Momentum is building now, and this is the time to amplify it.</p>\n<p>What is the budget you are applying for? Why is it reasonable? (Budget)<br>\n<strong>Funding Request:</strong> $500 per month for 6 months<br>\n<strong>Total Request:</strong> $3,000</p>\n<p>This is a modest and reasonable budget considering the amount of consistent content being delivered.</p>\n<p>For $500 monthly, I will provide:</p>\n<ul>\n<li>3 livestream broadcasts</li>\n<li>2+ supporting posts on X</li>\n<li>Topic research and preparation</li>\n<li>Scheduling and outreach for guests/interviews when applicable</li>\n<li>Social promotion and community engagement</li>\n<li>Consistent ecosystem coverage over a six-month period</li>\n</ul>\n<p>At 18 livestreams + 12+ X posts, this provides efficient value compared to traditional marketing campaigns while offering direct community engagement and authentic ecosystem exposure.</p>\n<p>How do you plan to do the work? (How?)<br>\nThe work will be carried out through a consistent monthly content schedule over six months.</p>\n<p>Each month I will:</p>\n<ul>\n<li>Host 3 livestream broadcasts focused on ecosystem news, product updates, interviews, educational topics, and community discussions</li>\n<li>Publish at least 2 supporting posts on X to promote broadcasts, highlight important developments, and engage the wider community</li>\n<li>Research ecosystem developments and prepare discussion topics for each stream</li>\n<li>Invite guests, builders, or community members when relevant to create valuable discussion</li>\n<li>Engage directly with the community through livestream chat, comments, and social media discussion</li>\n<li>Maintain consistent visibility around major ecosystem milestones, launches, and updates</li>\n</ul>\n<p>This approach keeps content authentic, timely, and community-centered while creating a reliable media presence over the full six-month campaign.</p>\n<p>Final Statement<br>\nI have already invested years into building community, educating audiences, and supporting ecosystem growth. This grant would allow me to dedicate structured time and consistent energy toward amplifying one of the most exciting growth periods in the ecosystem.</p>\n<p>My goal is simple: increase awareness, strengthen community, and help drive adoption through consistent media presence.</p>\n<p>Submitted by: Bitcoin Renegade<br>\nRequested Funding: $3,000</p>\n<hr>\n<p><a href=\"https://docs.google.com/presentation/d/1xRRN8xV8eyiQcu-zvM_amVqx6KZAP5C3VrwrwWW-Hj4/edit?usp=sharing\" rel=\"noopener nofollow ugc\">Bitcoin Renegade CKB Media Campaign Powerpoint</a></p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24287,
          "post_number": 35,
          "topic_id": 10239,
          "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign",
          "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign",
          "author": "Bitcoin_Renegade",
          "created_at": "2026-05-12T03:32:31.214000+00:00",
          "updated_at": "2026-05-12T03:32:31.214000+00:00",
          "reply_to_post_number": 33,
          "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/35",
          "content_text": "I would like to withdraw the proposal for now and discuss further with Neon on a few key points on his dual approach which I think I would fit perfectly. So yes please inform me of the steps to withdraw",
          "content_html": "<p>I would like to withdraw the proposal for now and discuss further with Neon on a few key points on his dual approach which I think I would fit perfectly. So yes please inform me of the steps to withdraw</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24288,
          "post_number": 36,
          "topic_id": 10239,
          "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign",
          "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T04:07:22.767000+00:00",
          "updated_at": "2026-05-12T04:08:28.853000+00:00",
          "reply_to_post_number": 35,
          "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/36",
          "content_text": "Hi 感谢你的坦诚和对提案精益求精的追求\n虽然目前没有标准化的提案撤回流程，但在不违背DAO 1.0规则的前提下，我建议这样操作：\n请您在本帖中发布一条撤回该提案的确认声明，当然也欢迎您在其中简述后续打算改进提案的大致方向\n作为协调员，我会把信息同步到社区\n等您和Neon以及其他社区成员讨论完善提案后，欢迎新开一个[DIS]提案贴进行提交",
          "content_html": "<p>Hi 感谢你的坦诚和对提案精益求精的追求</p>\n<p>虽然目前没有标准化的提案撤回流程，但在不违背DAO 1.0规则的前提下，我建议这样操作：</p>\n<ol>\n<li>请您在本帖中发布一条撤回该提案的确认声明，当然也欢迎您在其中简述后续打算改进提案的大致方向</li>\n<li>作为协调员，我会把信息同步到社区</li>\n<li>等您和Neon以及其他社区成员讨论完善提案后，欢迎新开一个[DIS]提案贴进行提交</li>\n</ol>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24305,
          "post_number": 37,
          "topic_id": 10239,
          "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign",
          "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign",
          "author": "Bitcoin_Renegade",
          "created_at": "2026-05-12T14:54:47.272000+00:00",
          "updated_at": "2026-05-12T14:54:47.272000+00:00",
          "reply_to_post_number": 36,
          "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/37",
          "content_text": "Ok thank you and i will do",
          "content_html": "<p>Ok thank you and i will do</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24306,
          "post_number": 38,
          "topic_id": 10239,
          "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign",
          "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign",
          "author": "Bitcoin_Renegade",
          "created_at": "2026-05-12T14:57:43.638000+00:00",
          "updated_at": "2026-05-12T14:57:43.638000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/38",
          "content_text": "I am formally withdrawing my proposal set before you to refine and progress the approach used to have the best outcome possible. I will refine the approach to either add a meet up locally to the Denver area or a future event like rare evo for me and my team of Renegades after discussing the best approach. So thank you all for your consideration we will return with a modified proposal.",
          "content_html": "<p>I am formally withdrawing my proposal set before you to refine and progress the approach used to have the best outcome possible. I will refine the approach to either add a meet up locally to the Denver area or a future event like rare evo for me and my team of Renegades after discussing the best approach. So thank you all for your consideration we will return with a modified proposal.</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 10249,
      "title": "A New Chapter for CKB: Introducing the Common Knowledge Base Association",
      "slug": "a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association",
      "url": "https://talk.nervos.org/t/a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association/10249",
      "created_at": "2026-05-12T12:01:31.059000+00:00",
      "last_posted_at": "2026-05-12T12:35:28.592000+00:00",
      "category_id": 40,
      "tags": [
        "CKB"
      ],
      "posters": [
        "Original Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24301,
          "post_number": 1,
          "topic_id": 10249,
          "topic_title": "A New Chapter for CKB: Introducing the Common Knowledge Base Association",
          "topic_slug": "a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association",
          "author": "CKBA",
          "created_at": "2026-05-12T12:01:31.126000+00:00",
          "updated_at": "2026-05-12T12:03:47.306000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association/10249/1",
          "content_text": "ckbaann1920×1080 385 KB\nFrom 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.\nBlockchains 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.\nToday, we take a deliberate step toward that vision.\nFormation of the Common Knowledge Base Association\nThe Common Knowledge Base Association (CKBA) is a Swiss Verein—a membership-based, non-profit legal entity registered in Baar, Switzerland.\nIt represents the natural evolution of the Nervos Foundation into a structure suited for a growing decentralized ecosystem. The Association brings together the teams and individuals who have spent the past eight years building CKB—researchers, engineers, storytellers, and operational personnel—into a single, more open, coordinated, and collaborative organization.\nCKBA will assume stewardship of the ecosystem. Assets previously held by the Foundation are being transferred to this association through a structured process, ensuring continuity of funding for ongoing initiatives, grants, and ecosystem support programs.\nThis transition is designed to be seamless, preserving operational stability while aligning resource allocation more closely with rapidly evolving priorities.\nWhy Now?\nAs both the regulatory environment and CKB have matured, it has become clear that a traditional foundation structure is no longer the optimal coordination model.\nA Swiss association provides a natural fit. As a membership-based structure, it enables broader participation by stakeholders across the ecosystem while creating a more effective coordination layer among technical development, ecosystem growth, and communication. At the same time, it offers a stable and widely recognized legal framework, grounded in regulatory clarity and political neutrality.\nThis change also unites core contributors who were previously separated into distinct entities with different mandates, management teams, and regulatory requirements. Coordination at the heart of the project is becoming tighter, ensuring that execution across functions is aligned.\nImportantly, this change is not about introducing centralization but about improving coherence at the coordination layer—ensuring that research, development, and ecosystem efforts move in sync, while preserving the network’s decentralized nature.\nCore Priorities\nThe Common Knowledge Base Association will focus on three primary areas:\nAwareness of CKB: Expanding global understanding of CKB through education, research, events, and narrative development.\nDeveloper Relations: Supporting developers building on CKB through documentation, technical education, and community engagement.\nLongevity: Ensuring a smooth transition toward a future in which a vibrant ecosystem operates increasingly autonomously\nGovernance Structure\nThe Association operates under Swiss association law, a well-established and politically neutral framework designed for membership-driven organizations.\nMembership is structured in two tiers:\nGeneral Members are community members who can participate and engage in Association meetings.\nContributing Members are long-standing contributors to CKB and hold formal governance rights, including voting on key matters such as the election of the Board and the approval of major decisions affecting the Association.\nThe governance of the Association itself is organized around two primary bodies: the General Assembly and the Board.\nThe General Assembly is the highest governing body of the Association and consists of all Contributing Members. It is responsible for setting the Association’s overall direction and exercising ultimate oversight of its operations. This includes approving budgets, ratifying major strategic decisions, admitting new Contributing Members, and electing or removing Board members.\nThe Board serves as the supervisory body of the Association. It is elected by the General Assembly and is accountable to it. The Board is responsible for overseeing the Association’s strategy and ensuring that execution aligns with the priorities approved by the membership.\nDay-to-day operations such as communications, software development and testing are conducted by various operational teams, coordinated by the Office of Association Operations, led by the Operations Director, a position appointed by and accountable to the Board.\nThis structure establishes a clear separation between strategic oversight and execution. Authority ultimately rests with Contributing Members (through the General Assembly); the Board is tasked with supervision and operational personnel focus on day-to-day execution toward board-decided goals.\nIn practice, this distributes decision-making power among active contributors, ensures leadership accountability, and creates a governance system that can evolve and scale with the ecosystem while remaining decentralized and transparent.\nWhat Stays the Same\nThis transition does not change the fundamentals of CKB.\nThe mission, protocol, and tokenomics remain the same. Core contributors continue their work without interruption, and all ongoing initiatives are proceeding as planned.\nThis is a change in coordination structure—not in the project itself. Development continues on the same trajectory, now supported by a governance model designed to evolve alongside the ecosystem.\nHow to Get Involved\nIf you have been contributing to CKB as a developer, researcher, infrastructure operator, or community member, we encourage you to apply as a Contributing Member.\nThis is an opportunity to participate directly in the governance and direction of the ecosystem, at a time when the road to CKB’s future is being paved.\nThe membership portal will be available at https://ckba.build/, with full application details provided at launch.",
          "content_html": "<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://talk.nervos.org/uploads/default/original/2X/e/ed35a69c92f1e387ca297e794023f5f55a69f46f.jpeg\" data-download-href=\"https://talk.nervos.org/uploads/default/ed35a69c92f1e387ca297e794023f5f55a69f46f\" title=\"ckbaann\"><img src=\"https://talk.nervos.org/uploads/default/optimized/2X/e/ed35a69c92f1e387ca297e794023f5f55a69f46f_2_690x388.jpeg\" alt=\"ckbaann\" data-base62-sha1=\"xQs6CMi1NSap3tMHluyoSfQge7B\" width=\"690\" height=\"388\" srcset=\"https://talk.nervos.org/uploads/default/optimized/2X/e/ed35a69c92f1e387ca297e794023f5f55a69f46f_2_690x388.jpeg, https://talk.nervos.org/uploads/default/optimized/2X/e/ed35a69c92f1e387ca297e794023f5f55a69f46f_2_1035x582.jpeg 1.5x, https://talk.nervos.org/uploads/default/optimized/2X/e/ed35a69c92f1e387ca297e794023f5f55a69f46f_2_1380x776.jpeg 2x\" data-dominant-color=\"09090B\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">ckbaann</span><span class=\"informations\">1920×1080 385 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>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.</p>\n<p>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.</p>\n<p>Today, we take a deliberate step toward that vision.</p>\n<h2><a name=\"p-24301-formation-of-the-common-knowledge-base-association-1\" class=\"anchor\" href=\"#p-24301-formation-of-the-common-knowledge-base-association-1\" aria-label=\"Heading link\"></a>Formation of the Common Knowledge Base Association</h2>\n<p>The Common Knowledge Base Association (CKBA) is a Swiss Verein—a membership-based, non-profit legal entity registered in Baar, Switzerland.</p>\n<p>It represents the natural evolution of the Nervos Foundation into a structure suited for a growing decentralized ecosystem. The Association brings together the teams and individuals who have spent the past eight years building CKB—researchers, engineers, storytellers, and operational personnel—into a single, more open, coordinated, and collaborative organization.</p>\n<p>CKBA will assume stewardship of the ecosystem. Assets previously held by the Foundation are being transferred to this association through a structured process, ensuring continuity of funding for ongoing initiatives, grants, and ecosystem support programs.</p>\n<p>This transition is designed to be seamless, preserving operational stability while aligning resource allocation more closely with rapidly evolving priorities.</p>\n<h2><a name=\"p-24301-why-now-2\" class=\"anchor\" href=\"#p-24301-why-now-2\" aria-label=\"Heading link\"></a>Why Now?</h2>\n<p>As both the regulatory environment and CKB have matured, it has become clear that a traditional foundation structure is no longer the optimal coordination model.</p>\n<p>A Swiss association provides a natural fit. As a membership-based structure, it enables broader participation by stakeholders across the ecosystem while creating a more effective coordination layer among technical development, ecosystem growth, and communication. At the same time, it offers a stable and widely recognized legal framework, grounded in regulatory clarity and political neutrality.</p>\n<p>This change also unites core contributors who were previously separated into distinct entities with different mandates, management teams, and regulatory requirements. Coordination at the heart of the project is becoming tighter, ensuring that execution across functions is aligned.</p>\n<p>Importantly, this change is not about introducing centralization but about improving coherence at the coordination layer—ensuring that research, development, and ecosystem efforts move in sync, while preserving the network’s decentralized nature.</p>\n<h2><a name=\"p-24301-core-priorities-3\" class=\"anchor\" href=\"#p-24301-core-priorities-3\" aria-label=\"Heading link\"></a>Core Priorities</h2>\n<p>The Common Knowledge Base Association will focus on three primary areas:</p>\n<ul>\n<li>\n<p><strong>Awareness of CKB:</strong> Expanding global understanding of CKB through education, research, events, and narrative development.</p>\n</li>\n<li>\n<p><strong>Developer Relations:</strong> Supporting developers building on CKB through documentation, technical education, and community engagement.</p>\n</li>\n<li>\n<p><strong>Longevity:</strong> Ensuring a smooth transition toward a future in which a vibrant ecosystem operates increasingly autonomously</p>\n</li>\n</ul>\n<p>Governance Structure</p>\n<p>The Association operates under Swiss association law, a well-established and politically neutral framework designed for membership-driven organizations.</p>\n<p>Membership is structured in two tiers:</p>\n<ul>\n<li>\n<p><strong>General Members</strong> are community members who can participate and engage in Association meetings.</p>\n</li>\n<li>\n<p><strong>Contributing Members</strong> are long-standing contributors to CKB and hold formal governance rights, including voting on key matters such as the election of the Board and the approval of major decisions affecting the Association.</p>\n</li>\n</ul>\n<p>The governance of the Association itself is organized around two primary bodies: the <strong>General Assembly</strong> and the <strong>Board</strong>.</p>\n<p>The <strong>General Assembly</strong> is the highest governing body of the Association and consists of all Contributing Members. It is responsible for setting the Association’s overall direction and exercising ultimate oversight of its operations. This includes approving budgets, ratifying major strategic decisions, admitting new Contributing Members, and electing or removing Board members.</p>\n<p>The <strong>Board</strong> serves as the supervisory body of the Association. It is elected by the General Assembly and is accountable to it. The Board is responsible for overseeing the Association’s strategy and ensuring that execution aligns with the priorities approved by the membership.</p>\n<p>Day-to-day operations such as communications, software development and testing are conducted by various operational teams, coordinated by the Office of Association Operations, led by the Operations Director, a position appointed by and accountable to the Board.</p>\n<p>This structure establishes a clear separation between strategic oversight and execution. Authority ultimately rests with Contributing Members (through the General Assembly); the Board is tasked with supervision and operational personnel focus on day-to-day execution toward board-decided goals.</p>\n<p>In practice, this distributes decision-making power among active contributors, ensures leadership accountability, and creates a governance system that can evolve and scale with the ecosystem while remaining decentralized and transparent.</p>\n<h2><a name=\"p-24301-what-stays-the-same-4\" class=\"anchor\" href=\"#p-24301-what-stays-the-same-4\" aria-label=\"Heading link\"></a>What Stays the Same</h2>\n<p>This transition does not change the fundamentals of CKB.</p>\n<p>The mission, protocol, and tokenomics remain the same. Core contributors continue their work without interruption, and all ongoing initiatives are proceeding as planned.</p>\n<p>This is a change in coordination structure—not in the project itself. Development continues on the same trajectory, now supported by a governance model designed to evolve alongside the ecosystem.</p>\n<h2><a name=\"p-24301-how-to-get-involved-5\" class=\"anchor\" href=\"#p-24301-how-to-get-involved-5\" aria-label=\"Heading link\"></a>How to Get Involved</h2>\n<p>If you have been contributing to CKB as a developer, researcher, infrastructure operator, or community member, we encourage you to apply as a Contributing Member.</p>\n<p>This is an opportunity to participate directly in the governance and direction of the ecosystem, at a time when the road to CKB’s future is being paved.</p>\n<p>The membership portal will be available at <a href=\"https://ckba.build/\" rel=\"noopener nofollow ugc\">https://ckba.build/</a>, with full application details provided at launch.</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24304,
          "post_number": 2,
          "topic_id": 10249,
          "topic_title": "A New Chapter for CKB: Introducing the Common Knowledge Base Association",
          "topic_slug": "a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T12:35:28.592000+00:00",
          "updated_at": "2026-05-12T12:35:28.592000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/a-new-chapter-for-ckb-introducing-the-common-knowledge-base-association/10249/2",
          "content_text": "",
          "content_html": "",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 10126,
      "title": "关于 `ccc/fiber-sdk` 的一些想法和进展",
      "slug": "ccc-fiber-sdk",
      "url": "https://talk.nervos.org/t/ccc-fiber-sdk/10126",
      "created_at": "2026-03-23T03:25:06.193000+00:00",
      "last_posted_at": "2026-05-12T12:01:32.945000+00:00",
      "category_id": 35,
      "tags": [],
      "posters": [
        "Original Poster, Most Recent Poster",
        "Frequent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24303,
          "post_number": 7,
          "topic_id": 10126,
          "topic_title": "关于 `ccc/fiber-sdk` 的一些想法和进展",
          "topic_slug": "ccc-fiber-sdk",
          "author": "Ckroamer",
          "created_at": "2026-05-12T12:01:32.945000+00:00",
          "updated_at": "2026-05-12T12:01:32.945000+00:00",
          "reply_to_post_number": 6,
          "url": "https://talk.nervos.org/t/ccc-fiber-sdk/10126/7",
          "content_text": "github.com/nervosnetwork/fiber-docs\nfeat: fiber example game adaptation for fiber-sdk and recent fiber updates catch-up\nmaster ← ashuralyk:master\n已打开 11:58AM - 12 May 26 UTC\nashuralyk\n+2768\n-2788\nfiber 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\n我重新提交了新的 PR，根据之前的 PR 的反馈，再加上 fiber-sdk 已经更新到了最新的 0.8.1 版本，所以重新提交了新的更新",
          "content_html": "<aside class=\"onebox githubpullrequest\" data-onebox-src=\"https://github.com/nervosnetwork/fiber-docs/pull/65\">\n  <header class=\"source\">\n\n      <a href=\"https://github.com/nervosnetwork/fiber-docs/pull/65\" target=\"_blank\" rel=\"noopener nofollow ugc\">github.com/nervosnetwork/fiber-docs</a>\n  </header>\n\n  <article class=\"onebox-body\">\n    <div class=\"github-row\" data-github-private-repo=\"false\">\n\n\n\n    <div class=\"github-icon-container\" title=\"拉取请求\">\n      <svg width=\"60\" height=\"60\" class=\"github-icon\" viewBox=\"0 0 12 16\" aria-hidden=\"true\"><path fill-rule=\"evenodd\" d=\"M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z\"></path></svg>\n    </div>\n\n  <div class=\"github-info-container\">\n\n\n\n      <h4>\n        <a href=\"https://github.com/nervosnetwork/fiber-docs/pull/65\" target=\"_blank\" rel=\"noopener nofollow ugc\">feat: fiber example game adaptation for fiber-sdk and recent fiber updates catch-up</a>\n      </h4>\n\n    <div class=\"branches\">\n      <code>master</code> ← <code>ashuralyk:master</code>\n    </div>\n\n      <div class=\"github-info\">\n        <div class=\"date\">\n          已打开 <span class=\"discourse-local-date\" data-format=\"ll\" data-date=\"2026-05-12\" data-time=\"11:58:08\" data-timezone=\"UTC\">11:58AM - 12 May 26 UTC</span>\n        </div>\n\n        <div class=\"user\">\n          <a href=\"https://github.com/ashuralyk\" target=\"_blank\" rel=\"noopener nofollow ugc\">\n            <img alt=\"\" src=\"https://talk.nervos.org/uploads/default/original/2X/d/dcdc503779acf72f6119db5046e8f68c250b03e6.png\" class=\"onebox-avatar-inline\" width=\"20\" height=\"20\" data-dominant-color=\"E2AFCB\">\n            ashuralyk\n          </a>\n        </div>\n\n        <div class=\"lines\" title=\"1 提交了更改的 7 文件，其中包含 2768 项增加和 2788 项删除\">\n          <a href=\"https://github.com/nervosnetwork/fiber-docs/pull/65/files\" target=\"_blank\" rel=\"noopener nofollow ugc\">\n            <span class=\"added\">+2768</span>\n            <span class=\"removed\">-2788</span>\n          </a>\n        </div>\n      </div>\n  </div>\n</div>\n\n  <div class=\"github-row\">\n    <p class=\"github-body-container\">fiber has upgraded into v0.8.1, however, the example game is still behind with e<span class=\"show-more-container\"><a href=\"https://github.com/nervosnetwork/fiber-docs/pull/65\" target=\"_blank\" rel=\"noopener nofollow ugc\" class=\"show-more\">…</a></span><span class=\"excerpt hidden\">arlier version, by the way, `fiber-sdk` has been upgraded to v0.8.1 as well</span></p>\n  </div>\n\n  </article>\n\n  <div class=\"onebox-metadata\">\n    \n    \n  </div>\n\n  <div style=\"clear: both\"></div>\n</aside>\n\n<p>我重新提交了新的 PR，根据之前的 PR 的反馈，再加上 <code>fiber-sdk</code> 已经更新到了最新的 0.8.1 版本，所以重新提交了新的更新</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 10246,
      "title": "Discussion about an alternative to the protocol treasury",
      "slug": "discussion-about-an-alternative-to-the-protocol-treasury",
      "url": "https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246",
      "created_at": "2026-05-07T23:16:34.543000+00:00",
      "last_posted_at": "2026-05-12T10:28:57.799000+00:00",
      "category_id": 31,
      "tags": [],
      "posters": [
        "Original Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24282,
          "post_number": 19,
          "topic_id": 10246,
          "topic_title": "Discussion about an alternative to the protocol treasury",
          "topic_slug": "discussion-about-an-alternative-to-the-protocol-treasury",
          "author": "Yeti",
          "created_at": "2026-05-11T23:29:41.225000+00:00",
          "updated_at": "2026-05-11T23:29:41.225000+00:00",
          "reply_to_post_number": 12,
          "url": "https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246/19",
          "content_text": "jimi-winehouse:\nthe 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.\nI 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.\nBut 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.\njimi-winehouse:\nThe whole dilution thing is a meme\nI don’t think anyone is even talking about or worried about the dilution, it’s not even a consideration imo.\nThe only downside to activating the treasury is that most of these extra CKB emitted every year will also be sold immediately upon being paid out, so there will be a constant sell pressure on the price that hopefully will be offset by the positive things that the treasury funds will achieve.\nAlso, the Foundation funding the development of the treasury system with some of their remaining funds is part of the deal I think.\nIf they weren’t doing this then treasury itself would have to fund this development in the future, then we’d all be complaining about spending the treasury funds on something that should have been developed with the ICO funding.",
          "content_html": "<aside class=\"quote no-group quote-modified\" data-username=\"jimi-winehouse\" data-post=\"12\" data-topic=\"10246\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/letter_avatar_proxy/v4/letter/j/4491bb/48.png\" class=\"avatar\"> jimi-winehouse:</div>\n<blockquote>\n<p>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.</p>\n</blockquote>\n</aside>\n<p>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.</p>\n<p>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.</p>\n<aside class=\"quote no-group\" data-username=\"jimi-winehouse\" data-post=\"12\" data-topic=\"10246\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/letter_avatar_proxy/v4/letter/j/4491bb/48.png\" class=\"avatar\"> jimi-winehouse:</div>\n<blockquote>\n<p>The whole dilution thing is a meme</p>\n</blockquote>\n</aside>\n<p>I don’t think anyone is even talking about or worried about the dilution, it’s not even a consideration imo.</p>\n<p>The only downside to activating the treasury is that most of these extra CKB emitted every year will also be sold immediately upon being paid out, so there will be a constant sell pressure on the price that hopefully will be offset by the positive things that the treasury funds will achieve.</p>\n<p>Also, the Foundation funding the development of the treasury system with some of their remaining funds is part of the deal I think.</p>\n<p>If they weren’t doing this then treasury itself would have to fund this development in the future, then we’d all be complaining about spending the treasury funds on something that should have been developed with the ICO funding.</p>",
          "like_count": 0,
          "quote_count": 1
        },
        {
          "post_id": 24291,
          "post_number": 20,
          "topic_id": 10246,
          "topic_title": "Discussion about an alternative to the protocol treasury",
          "topic_slug": "discussion-about-an-alternative-to-the-protocol-treasury",
          "author": "d3fus7.bit",
          "created_at": "2026-05-12T07:16:09.027000+00:00",
          "updated_at": "2026-05-12T07:16:09.027000+00:00",
          "reply_to_post_number": 19,
          "url": "https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246/20",
          "content_text": "Yeti:\nwill be offset by the positive things that the treasury funds will achieve.\nCall me toxic, but I have hard time seeing this..",
          "content_html": "<aside class=\"quote no-group\" data-username=\"Yeti\" data-post=\"19\" data-topic=\"10246\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/yeti/48/9533_2.png\" class=\"avatar\"> Yeti:</div>\n<blockquote>\n<p>will be offset by the positive things that the treasury funds will achieve.</p>\n</blockquote>\n</aside>\n<p>Call me toxic, but I have hard time seeing this..</p>",
          "like_count": 0,
          "quote_count": 1
        },
        {
          "post_id": 24296,
          "post_number": 21,
          "topic_id": 10246,
          "topic_title": "Discussion about an alternative to the protocol treasury",
          "topic_slug": "discussion-about-an-alternative-to-the-protocol-treasury",
          "author": "Yeti",
          "created_at": "2026-05-12T09:05:49.311000+00:00",
          "updated_at": "2026-05-12T09:05:49.311000+00:00",
          "reply_to_post_number": 20,
          "url": "https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246/21",
          "content_text": "Nah, I don’t think you’re toxic mate, you don’t beat around the bush though haha.\nBut I think the positives of the treasury will far outweigh the downsides of the sell pressure. It won’t really be any different than how other projects and even how Nervos has been funding a lot of stuff in the past.\nThere will always be tokens being used as payment that will then be sold, I just think there needs to be some sort of system in place to prevent huge amounts of CKB are being payed out all at once.",
          "content_html": "<p>Nah, I don’t think you’re toxic mate, you don’t beat around the bush though haha.</p>\n<p>But I think the positives of the treasury will far outweigh the downsides of the sell pressure.  It won’t really be any different than how other projects and even how Nervos has been funding a lot of stuff in the past.</p>\n<p>There will always be tokens being used as payment that will then be sold, I just think there needs to be some sort of system in place to prevent huge amounts of CKB are being payed out all at once.</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24298,
          "post_number": 22,
          "topic_id": 10246,
          "topic_title": "Discussion about an alternative to the protocol treasury",
          "topic_slug": "discussion-about-an-alternative-to-the-protocol-treasury",
          "author": "d3fus7.bit",
          "created_at": "2026-05-12T10:20:23.042000+00:00",
          "updated_at": "2026-05-12T10:20:49.988000+00:00",
          "reply_to_post_number": 21,
          "url": "https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246/22",
          "content_text": "I hope that happens.\nThe difference, though, is that the money will come from the secondary issuance.. anyway, it might turn out to be for the best in the end. : )\nYeti:\nI just think there needs to be some sort of system in place to prevent huge amounts of CKB are being payed out all at once\nI support this idea and in combination with the burning mechanism if some proposal is not good enough is a step in the right direction. Otherwise, I don’t see any point in accumulating funds in this account/contract aimlessly.",
          "content_html": "<p>I hope that happens.</p>\n<p>The difference, though, is that the money will come from the secondary issuance.. anyway, it might turn out to be for the best in the end. : )</p>\n<aside class=\"quote no-group\" data-username=\"Yeti\" data-post=\"21\" data-topic=\"10246\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/yeti/48/9533_2.png\" class=\"avatar\"> Yeti:</div>\n<blockquote>\n<p>I just think there needs to be some sort of system in place to prevent huge amounts of CKB are being payed out all at once</p>\n</blockquote>\n</aside>\n<p>I support this idea and in combination with the burning mechanism if some proposal is not good enough is a step in the right direction. Otherwise, I don’t see any point in accumulating funds in this account/contract aimlessly.</p>",
          "like_count": 0,
          "quote_count": 1
        },
        {
          "post_id": 24299,
          "post_number": 23,
          "topic_id": 10246,
          "topic_title": "Discussion about an alternative to the protocol treasury",
          "topic_slug": "discussion-about-an-alternative-to-the-protocol-treasury",
          "author": "Yeti",
          "created_at": "2026-05-12T10:28:57.799000+00:00",
          "updated_at": "2026-05-12T10:28:57.799000+00:00",
          "reply_to_post_number": 22,
          "url": "https://talk.nervos.org/t/discussion-about-an-alternative-to-the-protocol-treasury/10246/23",
          "content_text": "d3fus7.bit:\nI support this idea and in combination with the burning mechanism if some proposal is not good enough is a step in the right direction. Otherwise, I don’t see any point in accumulating funds in this account/contract aimlessly.\nYeah, I think I’ve seen it mentioned a couple of times that the whole secondary issuance wont be minted if unneeded.\nBut I don’t mind the idea of having a decent stockpile, just not to ridiculous levels.",
          "content_html": "<aside class=\"quote no-group\" data-username=\"d3fus7.bit\" data-post=\"22\" data-topic=\"10246\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/d3fus7.bit/48/7232_2.png\" class=\"avatar\"> d3fus7.bit:</div>\n<blockquote>\n<p>I support this idea and in combination with the burning mechanism if some proposal is not good enough is a step in the right direction. Otherwise, I don’t see any point in accumulating funds in this account/contract aimlessly.</p>\n</blockquote>\n</aside>\n<p>Yeah, I think I’ve seen it mentioned a couple of times that the whole secondary issuance wont be minted if unneeded.</p>\n<p>But I don’t mind the idea of having a decent stockpile, just not to ridiculous levels.</p>",
          "like_count": 0,
          "quote_count": 1
        }
      ]
    },
    {
      "topic_id": 10015,
      "title": "[DIS] Decentralized privacy order-book appchain based on CKB L1 - 2026.phase-1",
      "slug": "dis-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1",
      "url": "https://talk.nervos.org/t/dis-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1/10015",
      "created_at": "2026-02-28T04:17:08.724000+00:00",
      "last_posted_at": "2026-05-12T09:02:23.025000+00:00",
      "category_id": 65,
      "tags": [
        "appchain"
      ],
      "posters": [
        "Original Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24295,
          "post_number": 26,
          "topic_id": 10015,
          "topic_title": "[DIS] Decentralized privacy order-book appchain based on CKB L1 - 2026.phase-1",
          "topic_slug": "dis-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T09:02:23.025000+00:00",
          "updated_at": "2026-05-12T09:02:23.025000+00:00",
          "reply_to_post_number": 23,
          "url": "https://talk.nervos.org/t/dis-decentralized-privacy-order-book-appchain-based-on-ckb-l1-2026-phase-1/10015/26",
          "content_text": "M1 Payout\nhttps://explorer.nervos.org/transaction/0x88241cad0617d2ca5f1482217d557c89ea34429c55c61cf1cf34e637e412c286\n3,127,036 CKB (representing the 20% of full grants)",
          "content_html": "<p>M1 Payout</p>\n<p><a href=\"https://explorer.nervos.org/transaction/0x88241cad0617d2ca5f1482217d557c89ea34429c55c61cf1cf34e637e412c286\" class=\"onebox\" target=\"_blank\" rel=\"noopener\">https://explorer.nervos.org/transaction/0x88241cad0617d2ca5f1482217d557c89ea34429c55c61cf1cf34e637e412c286</a></p>\n<p>3,127,036 CKB (representing the 20% of full grants)</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 9879,
      "title": "[DIS] Mobile-Ready CKB Light Client (Pocket Node) for Android",
      "slug": "dis-mobile-ready-ckb-light-client-pocket-node-for-android",
      "url": "https://talk.nervos.org/t/dis-mobile-ready-ckb-light-client-pocket-node-for-android/9879",
      "created_at": "2026-01-27T09:25:31.938000+00:00",
      "last_posted_at": "2026-05-12T08:59:43.084000+00:00",
      "category_id": 65,
      "tags": [
        "CKB",
        "light-client"
      ],
      "posters": [
        "Original Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24294,
          "post_number": 42,
          "topic_id": 9879,
          "topic_title": "[DIS] Mobile-Ready CKB Light Client (Pocket Node) for Android",
          "topic_slug": "dis-mobile-ready-ckb-light-client-pocket-node-for-android",
          "author": "zz_tovarishch",
          "created_at": "2026-05-12T08:59:43.084000+00:00",
          "updated_at": "2026-05-12T08:59:43.084000+00:00",
          "reply_to_post_number": 39,
          "url": "https://talk.nervos.org/t/dis-mobile-ready-ckb-light-client-pocket-node-for-android/9879/42",
          "content_text": "M3 Payout\nhttps://explorer.nervos.org/transaction/0x03274cedea0cc5c39bcf669ad4d238d21e52267e9ee8ac60194ae6cbb730cb16\n2,198,697 CKB (representing the 22.5% of full grants)",
          "content_html": "<p><strong>M3 Payout</strong></p>\n<p><a href=\"https://explorer.nervos.org/transaction/0x03274cedea0cc5c39bcf669ad4d238d21e52267e9ee8ac60194ae6cbb730cb16\" class=\"onebox\" target=\"_blank\" rel=\"noopener\">https://explorer.nervos.org/transaction/0x03274cedea0cc5c39bcf669ad4d238d21e52267e9ee8ac60194ae6cbb730cb16</a></p>\n<p>2,198,697 CKB (representing the 22.5% of full grants)</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 10143,
      "title": "Pre-RFC Discussion: Activating the Nervos DAO Treasury",
      "slug": "pre-rfc-discussion-activating-the-nervos-dao-treasury",
      "url": "https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143",
      "created_at": "2026-03-31T03:10:02.859000+00:00",
      "last_posted_at": "2026-05-12T07:51:06.097000+00:00",
      "category_id": 31,
      "tags": [
        "CKB"
      ],
      "posters": [
        "Original Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24292,
          "post_number": 14,
          "topic_id": 10143,
          "topic_title": "Pre-RFC Discussion: Activating the Nervos DAO Treasury",
          "topic_slug": "pre-rfc-discussion-activating-the-nervos-dao-treasury",
          "author": "d3fus7.bit",
          "created_at": "2026-05-12T07:51:06.097000+00:00",
          "updated_at": "2026-05-12T07:51:06.097000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143/14",
          "content_text": "chenyukang:\nThe use of the treasury funds will be fully open, transparent, and verifiable on-chain for everyone to see.\nWill this be user-friendly, will it be easy for a non-technical person to understand what’s going on?\nchenyukang:\nthe governance protocol could direct the treasury to burn unused funds\nCan you elaborate? Does this mean that the community will have to vote to burn these funds or will this happen automatically?",
          "content_html": "<aside class=\"quote no-group\" data-username=\"chenyukang\" data-post=\"1\" data-topic=\"10143\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/chenyukang/48/10087_2.png\" class=\"avatar\"> chenyukang:</div>\n<blockquote>\n<p>The use of the treasury funds will be fully open, transparent, and verifiable on-chain for everyone to see.</p>\n</blockquote>\n</aside>\n<p>Will this be user-friendly, will it be easy for a non-technical person to understand what’s going on?</p>\n<aside class=\"quote no-group\" data-username=\"chenyukang\" data-post=\"1\" data-topic=\"10143\">\n<div class=\"title\">\n<div class=\"quote-controls\"></div>\n<img alt=\"\" width=\"24\" height=\"24\" src=\"https://talk.nervos.org/user_avatar/talk.nervos.org/chenyukang/48/10087_2.png\" class=\"avatar\"> chenyukang:</div>\n<blockquote>\n<p>the governance protocol could direct the treasury to <strong>burn</strong> unused funds</p>\n</blockquote>\n</aside>\n<p>Can you elaborate? Does this mean that the community will have to vote to burn these funds or will this happen automatically?</p>",
          "like_count": 0,
          "quote_count": 1
        }
      ]
    },
    {
      "topic_id": 10243,
      "title": "Is there any good reason for allowing hidden profiles?",
      "slug": "is-there-any-good-reason-for-allowing-hidden-profiles",
      "url": "https://talk.nervos.org/t/is-there-any-good-reason-for-allowing-hidden-profiles/10243",
      "created_at": "2026-05-10T12:08:22.218000+00:00",
      "last_posted_at": "2026-05-12T07:04:15.917000+00:00",
      "category_id": 67,
      "tags": [],
      "posters": [
        "Original Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24290,
          "post_number": 7,
          "topic_id": 10243,
          "topic_title": "Is there any good reason for allowing hidden profiles?",
          "topic_slug": "is-there-any-good-reason-for-allowing-hidden-profiles",
          "author": "terrytai",
          "created_at": "2026-05-12T07:04:15.917000+00:00",
          "updated_at": "2026-05-12T07:04:15.917000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/is-there-any-good-reason-for-allowing-hidden-profiles/10243/7",
          "content_text": "感谢各位的反馈，我觉得有道理。已经关掉了这个设置 allow_users_to_hide_profile\n以前设置的值是论坛系统的默认，我们之前其实没有做任何设计。",
          "content_html": "<p>感谢各位的反馈，我觉得有道理。已经关掉了这个设置 allow_users_to_hide_profile</p>\n<p>以前设置的值是论坛系统的默认，我们之前其实没有做任何设计。</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 10247,
      "title": "Fiber Desktop — run Fiber (FNN) on your laptop without the “public node” headache",
      "slug": "fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache",
      "url": "https://talk.nervos.org/t/fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache/10247",
      "created_at": "2026-05-12T00:43:09.654000+00:00",
      "last_posted_at": "2026-05-12T01:36:19.973000+00:00",
      "category_id": 32,
      "tags": [
        "fiber",
        "testnet"
      ],
      "posters": [
        "Original Poster",
        "Most Recent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24283,
          "post_number": 1,
          "topic_id": 10247,
          "topic_title": "Fiber Desktop — run Fiber (FNN) on your laptop without the “public node” headache",
          "topic_slug": "fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache",
          "author": "ebubedev",
          "created_at": "2026-05-12T00:43:09.719000+00:00",
          "updated_at": "2026-05-12T00:43:09.719000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache/10247/1",
          "content_text": "Hi everyone,\nIf 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.\nThe 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 and use the network.”\nThere is a second wall that hits even on your own laptop: setup is often CLI-heavy. Getting from zero to a working node can mean a long chain of terminal commands — right binary, paths, config, key material, then RPC-style steps for connecting to peers, opening channels, creating invoices, and so on. That is fine for power users, but it filters out anyone who wants to try the network without treating the docs like a daily homework assignment.\nI built Fiber Desktop to narrow both gaps: less hosting pressure and less death-by-CLI. This post explains what it is and how it fits together for people who are not deep into ops or protocol details.\nScreenshot 2026-05-12 at 01.31.472078×1380 228 KB\nWhat Fiber Desktop is\nFiber Desktop is a desktop application for Mac or PC (tested properly for Mac). It does not replace the official Fiber software. It wraps it: it helps you install and run the same official node (fnn) on the machine you already use, with clearer steps, start/stop controls, and safer handling of secrets.\nIn plain roles:\nTour guide — walks you through setup in order (network, data folder, configuration, where to put your key material).\nDashboard — start and stop the node, see logs, and use the network from one place.\nVault assistant — stores the node’s encryption password in your operating system’s built-in secure storage (keychain / credential manager) instead of scattering it in random files.\nScreenshot 2026-05-12 at 01.32.182074×1368 401 KB\nWhere you would otherwise juggle many CLI commands and hand-built RPC calls, the app pushes you toward guided flows and in-app actions (for example connecting to documented relays or trying channel and invoice steps from the UI) so you are not memorizing command order on day one.\nUnder the hood it is a native app (Tauri + React, etc.). If you are not technical, you can ignore that: what matters is that it is a normal desktop app controlling the official Fiber node on your desk or laptop.\nSource: github.com/chukwuma619/fiber-desktop\nThe problem it tries to solve\nUsing Fiber seriously usually means keeping that engine running and connected enough to be useful on the network. That often pushes people toward:\nA VPS they must maintain and lock down\nA small home server that must stay on\nNetworking questions (ports, public addresses, who can reach my machine)\nOperational questions (updates, backups, monitoring)\nOn top of that, day-one onboarding is often a long sequence of CLI and JSON-RPC steps: easy to get stuck on one wrong path, flag, or payload even when you are not trying to self-host.\nFiber Desktop is aimed at a different default: run the official node locally, on hardware you already own, with a user experience closer to consumer software — guided setup instead of a wall of commands — while still following how the Fiber ecosystem expects nodes to connect and discover each other, including documented public relay nodes.\nHow you join the network (without turning your PC into a “public hosting project”)\nFiber nodes talk to each other peer-to-peer. Public relay nodes are well-known peers listed in the official docs. They act like on-ramps: you connect out to them so your node is no longer isolated.\nIn Fiber Desktop that shows up as actions like connecting to relay 1 or relay 2 for your chosen network, using the same public keys the Fiber project documents — see public nodes.\nYou are not inventing a custom bridge; you are joining the same mesh the docs describe. That is different from “I must run a public website that exposes my wallet.” You are participating in a network of nodes, not necessarily running a personal datacenter as the default onboarding story.\nChannels, invoices, and how a payment reaches your machine\nChannels are the “pipes”\nAfter you are connected, the next big step is usually opening a channel with another node (often one of the public relays when you are learning). A channel is a rules-based pipe between two nodes.\nImportant nuance: payments usually do not flow as “one big public server receives everything and then downloads it to your laptop.” They move hop by hop across many channels when needed. Public relays help you plug in and become part of that map, but a payment route can be longer than a single hop.\nInvoices are created on your computer\nWhen you create an invoice, that request is generated by your local node. You share it (text / QR) with whoever pays. You do not need a public payment website for that step.\nRouting is how money crosses the mesh\nWhen someone pays your invoice, their software searches for a path across the network — a chain of channel hops from them to you. If a valid path exists and every hop has enough capacity pointing the right way, the payment settles on your node — the one running under Fiber Desktop.\nSo this high-level picture is right: the payment is routed across the Fiber network until it reaches my local node. The small correction is: it is not always “only the public relay sends it down to me”; it is often several hops across different nodes, with yours as the final stop.\nA honest note on receiving\nReceiving reliably in channel-based networks usually needs incoming capacity (liquidity and channel layout that allow value to flow toward your node). If someone tries to receive before channels are set up sensibly, they may see “no route” even when the app is working. Fiber Desktop makes the machinery easier; the economics of the graph are still part of the real network.\nUseful links\nFiber Desktop: github.com/chukwuma619/fiber-desktop\nOfficial Fiber / FNN: github.com/nervosnetwork/fiber\nPublic nodes: public-nodes.md\nTestnet / key setup: testnet-nodes.md\nFiber Desktop does not change what Fiber is. It changes how painful it is to run the real thing on a normal computer: official software first, local control, less accidental sysadmin, and less reliance on a long CLI checklist just to get started.\nIf you try it, feedback is welcome — especially first-time setup, key handling, connectivity to public relays, and whether the guided flows replace the commands you used to need.",
          "content_html": "<p>Hi everyone,</p>\n<p>If you follow Nervos, you may have heard of <strong>Fiber</strong> — 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 <strong>Fiber Network Node</strong> (often called <strong>fnn</strong>). That program is the “engine” that opens channels, listens for payments, and creates invoices.</p>\n<p>The awkward part is not the idea of Fiber. It is <strong>where</strong> that engine is supposed to live. Many people end up looking at <strong>rented servers</strong>, <strong>router settings</strong>, <strong>always-on home machines</strong>, and <strong>security checklists</strong> just to feel like they can participate. That is a lot of work for something that should feel closer to “install an app and use the network.”</p>\n<p>There is a second wall that hits even on your own laptop: <strong>setup is often CLI-heavy</strong>. Getting from zero to a working node can mean a long chain of <strong>terminal commands</strong> — right binary, paths, config, key material, then RPC-style steps for connecting to peers, opening channels, creating invoices, and so on. That is fine for power users, but it filters out anyone who wants to <strong>try the network</strong> without treating the docs like a daily homework assignment.</p>\n<p>I built <strong>Fiber Desktop</strong> to narrow both gaps: <strong>less hosting pressure</strong> and <strong>less death-by-CLI</strong>. This post explains what it is and how it fits together for people who are not deep into ops or protocol details.</p>\n<h2><a name=\"p-24283-screenshot-2026-05-12-at-013147690x458upload3nee4gsyawpt8ga9ciird43nsrkjpeg-1\" class=\"anchor\" href=\"#p-24283-screenshot-2026-05-12-at-013147690x458upload3nee4gsyawpt8ga9ciird43nsrkjpeg-1\" aria-label=\"Heading link\"></a><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://talk.nervos.org/uploads/default/original/2X/1/17b312fa5b442db08ea5baf0bafe530cbd3247c8.jpeg\" data-download-href=\"https://talk.nervos.org/uploads/default/17b312fa5b442db08ea5baf0bafe530cbd3247c8\" title=\"Screenshot 2026-05-12 at 01.31.47\"><img src=\"https://talk.nervos.org/uploads/default/optimized/2X/1/17b312fa5b442db08ea5baf0bafe530cbd3247c8_2_690x458.jpeg\" alt=\"Screenshot 2026-05-12 at 01.31.47\" data-base62-sha1=\"3nEE4GsYaWPt8GA9CiirD43nSrK\" width=\"690\" height=\"458\" srcset=\"https://talk.nervos.org/uploads/default/optimized/2X/1/17b312fa5b442db08ea5baf0bafe530cbd3247c8_2_690x458.jpeg, https://talk.nervos.org/uploads/default/optimized/2X/1/17b312fa5b442db08ea5baf0bafe530cbd3247c8_2_1035x687.jpeg 1.5x, https://talk.nervos.org/uploads/default/optimized/2X/1/17b312fa5b442db08ea5baf0bafe530cbd3247c8_2_1380x916.jpeg 2x\" data-dominant-color=\"101113\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">Screenshot 2026-05-12 at 01.31.47</span><span class=\"informations\">2078×1380 228 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></h2>\n<h2><a name=\"p-24283-what-fiber-desktop-is-2\" class=\"anchor\" href=\"#p-24283-what-fiber-desktop-is-2\" aria-label=\"Heading link\"></a>What Fiber Desktop is</h2>\n<p><strong>Fiber Desktop</strong> is a <strong>desktop application</strong> for Mac or PC (tested properly for Mac). It does <strong>not</strong> replace the official Fiber software. It <strong>wraps</strong> it: it helps you install and run the <strong>same official node</strong> (<code>fnn</code>) on <strong>the machine you already use</strong>, with clearer steps, start/stop controls, and safer handling of secrets.</p>\n<p>In plain roles:</p>\n<ol>\n<li><strong>Tour guide</strong> — walks you through setup in order (network, data folder, configuration, where to put your key material).</li>\n<li><strong>Dashboard</strong> — start and stop the node, see logs, and use the network from one place.</li>\n<li><strong>Vault assistant</strong> — stores the node’s encryption password in your operating system’s built-in secure storage (keychain / credential manager) instead of scattering it in random files.</li>\n</ol>\n<p><div class=\"lightbox-wrapper\"><a class=\"lightbox\" href=\"https://talk.nervos.org/uploads/default/original/2X/6/6d89cadf60bb9ce5da4d23f18f3a10df5326bad2.png\" data-download-href=\"https://talk.nervos.org/uploads/default/6d89cadf60bb9ce5da4d23f18f3a10df5326bad2\" title=\"Screenshot 2026-05-12 at 01.32.18\"><img src=\"https://talk.nervos.org/uploads/default/optimized/2X/6/6d89cadf60bb9ce5da4d23f18f3a10df5326bad2_2_690x455.png\" alt=\"Screenshot 2026-05-12 at 01.32.18\" data-base62-sha1=\"fD1gk4xry0DQiYxXnJ5JAftaBO2\" width=\"690\" height=\"455\" srcset=\"https://talk.nervos.org/uploads/default/optimized/2X/6/6d89cadf60bb9ce5da4d23f18f3a10df5326bad2_2_690x455.png, https://talk.nervos.org/uploads/default/optimized/2X/6/6d89cadf60bb9ce5da4d23f18f3a10df5326bad2_2_1035x682.png 1.5x, https://talk.nervos.org/uploads/default/optimized/2X/6/6d89cadf60bb9ce5da4d23f18f3a10df5326bad2_2_1380x910.png 2x\" data-dominant-color=\"0F1113\"><div class=\"meta\"><svg class=\"fa d-icon d-icon-far-image svg-icon\" aria-hidden=\"true\"><use href=\"#far-image\"></use></svg><span class=\"filename\">Screenshot 2026-05-12 at 01.32.18</span><span class=\"informations\">2074×1368 401 KB</span><svg class=\"fa d-icon d-icon-discourse-expand svg-icon\" aria-hidden=\"true\"><use href=\"#discourse-expand\"></use></svg></div></a></div></p>\n<p>Where you would otherwise juggle many <strong>CLI commands</strong> and hand-built RPC calls, the app pushes you toward <strong>guided flows and in-app actions</strong> (for example connecting to documented relays or trying channel and invoice steps from the UI) so you are not memorizing command order on day one.</p>\n<p>Under the hood it is a native app (Tauri + React, etc.). If you are not technical, you can ignore that: what matters is that it is a <strong>normal desktop app</strong> controlling the <strong>official</strong> Fiber node on your desk or laptop.</p>\n<p><strong>Source:</strong> <a href=\"https://github.com/chukwuma619/fiber-desktop\" rel=\"noopener nofollow ugc\">github.com/chukwuma619/fiber-desktop</a></p>\n<hr>\n<h2><a name=\"p-24283-the-problem-it-tries-to-solve-3\" class=\"anchor\" href=\"#p-24283-the-problem-it-tries-to-solve-3\" aria-label=\"Heading link\"></a>The problem it tries to solve</h2>\n<p>Using Fiber seriously usually means keeping that <strong>engine running</strong> and <strong>connected enough</strong> to be useful on the network. That often pushes people toward:</p>\n<ul>\n<li>A <strong>VPS</strong> they must maintain and lock down</li>\n<li>A <strong>small home server</strong> that must stay on</li>\n<li><strong>Networking</strong> questions (ports, public addresses, who can reach my machine)</li>\n<li><strong>Operational</strong> questions (updates, backups, monitoring)</li>\n</ul>\n<p>On top of that, <strong>day-one onboarding</strong> is often a long sequence of <strong>CLI and JSON-RPC</strong> steps: easy to get stuck on one wrong path, flag, or payload even when you are not trying to self-host.</p>\n<p><strong>Fiber Desktop</strong> is aimed at a different default: <strong>run the official node locally</strong>, on hardware you already own, with a user experience closer to consumer software — <strong>guided setup instead of a wall of commands</strong> — while still following how the Fiber ecosystem expects nodes to <strong>connect</strong> and <strong>discover</strong> each other, including documented <strong>public relay nodes</strong>.</p>\n<hr>\n<h2><a name=\"p-24283-how-you-join-the-network-without-turning-your-pc-into-a-public-hosting-project-4\" class=\"anchor\" href=\"#p-24283-how-you-join-the-network-without-turning-your-pc-into-a-public-hosting-project-4\" aria-label=\"Heading link\"></a>How you join the network (without turning your PC into a “public hosting project”)</h2>\n<p>Fiber nodes talk to each other <strong>peer-to-peer</strong>. <strong>Public relay nodes</strong> are well-known peers listed in the official docs. They act like <strong>on-ramps</strong>: you connect <strong>out</strong> to them so your node is no longer isolated.</p>\n<p>In Fiber Desktop that shows up as actions like connecting to <strong>relay 1</strong> or <strong>relay 2</strong> for your chosen network, using the same public keys the Fiber project documents — see <a href=\"https://github.com/nervosnetwork/fiber/blob/develop/docs/public-nodes.md\" rel=\"noopener nofollow ugc\">public nodes</a>.</p>\n<p>You are not inventing a custom bridge; you are <strong>joining the same mesh</strong> the docs describe. That is different from “I must run a public website that exposes my wallet.” You are <strong>participating in a network of nodes</strong>, not necessarily running a personal datacenter as the default onboarding story.</p>\n<hr>\n<h2><a name=\"p-24283-channels-invoices-and-how-a-payment-reaches-your-machine-5\" class=\"anchor\" href=\"#p-24283-channels-invoices-and-how-a-payment-reaches-your-machine-5\" aria-label=\"Heading link\"></a>Channels, invoices, and how a payment reaches your machine</h2>\n<h3><a name=\"p-24283-channels-are-the-pipes-6\" class=\"anchor\" href=\"#p-24283-channels-are-the-pipes-6\" aria-label=\"Heading link\"></a>Channels are the “pipes”</h3>\n<p>After you are connected, the next big step is usually opening a <strong>channel</strong> with another node (often one of the public relays when you are learning). A channel is a <strong>rules-based pipe</strong> between two nodes.</p>\n<p><strong>Important nuance:</strong> payments usually do <strong>not</strong> flow as “one big public server receives everything and then downloads it to your laptop.” They move <strong>hop by hop</strong> across <strong>many channels</strong> when needed. Public relays help you <strong>plug in</strong> and become part of that map, but a payment route can be longer than a single hop.</p>\n<h3><a name=\"p-24283-invoices-are-created-on-your-computer-7\" class=\"anchor\" href=\"#p-24283-invoices-are-created-on-your-computer-7\" aria-label=\"Heading link\"></a>Invoices are created on your computer</h3>\n<p>When you <strong>create an invoice</strong>, that request is generated by <strong>your local node</strong>. You share it (text / QR) with whoever pays. You do not need a public payment website for that step.</p>\n<h3><a name=\"p-24283-routing-is-how-money-crosses-the-mesh-8\" class=\"anchor\" href=\"#p-24283-routing-is-how-money-crosses-the-mesh-8\" aria-label=\"Heading link\"></a>Routing is how money crosses the mesh</h3>\n<p>When someone pays your invoice, <strong>their</strong> software searches for a <strong>path</strong> across the network — a chain of channel hops from them <strong>to you</strong>. If a valid path exists and every hop has enough capacity pointing the right way, the payment <strong>settles on your node</strong> — the one running under Fiber Desktop.</p>\n<p>So this high-level picture is right: <strong>the payment is routed across the Fiber network until it reaches my local node.</strong> The small correction is: it is <strong>not always</strong> “only the public relay sends it down to me”; it is often <strong>several hops</strong> across different nodes, with yours as the <strong>final stop</strong>.</p>\n<h3><a name=\"p-24283-a-honest-note-on-receiving-9\" class=\"anchor\" href=\"#p-24283-a-honest-note-on-receiving-9\" aria-label=\"Heading link\"></a>A honest note on receiving</h3>\n<p>Receiving reliably in channel-based networks usually needs <strong>incoming capacity</strong> (liquidity and channel layout that allow value to flow <strong>toward</strong> your node). If someone tries to receive before channels are set up sensibly, they may see “no route” even when the app is working. Fiber Desktop makes the <strong>machinery</strong> easier; the <strong>economics of the graph</strong> are still part of the real network.</p>\n<hr>\n<h2><a name=\"p-24283-useful-links-10\" class=\"anchor\" href=\"#p-24283-useful-links-10\" aria-label=\"Heading link\"></a>Useful links</h2>\n<ul>\n<li><strong>Fiber Desktop:</strong> <a href=\"https://github.com/chukwuma619/fiber-desktop\" rel=\"noopener nofollow ugc\">github.com/chukwuma619/fiber-desktop</a></li>\n<li><strong>Official Fiber / FNN:</strong> <a href=\"https://github.com/nervosnetwork/fiber\" rel=\"noopener nofollow ugc\">github.com/nervosnetwork/fiber</a></li>\n<li><strong>Public nodes:</strong> <a href=\"https://github.com/nervosnetwork/fiber/blob/develop/docs/public-nodes.md\" rel=\"noopener nofollow ugc\">public-nodes.md</a></li>\n<li><strong>Testnet / key setup:</strong> <a href=\"https://github.com/nervosnetwork/fiber/blob/develop/docs/testnet-nodes.md\" rel=\"noopener nofollow ugc\">testnet-nodes.md</a></li>\n</ul>\n<hr>\n<p>Fiber Desktop does not change what Fiber is. It changes <strong>how painful it is to run the real thing</strong> on a normal computer: <strong>official software first</strong>, <strong>local control</strong>, <strong>less accidental sysadmin</strong>, and <strong>less reliance on a long CLI checklist</strong> just to get started.</p>\n<p>If you try it, feedback is welcome — especially first-time setup, key handling, connectivity to public relays, and whether the guided flows replace the commands you used to need.</p>",
          "like_count": 0,
          "quote_count": 0
        },
        {
          "post_id": 24285,
          "post_number": 2,
          "topic_id": 10247,
          "topic_title": "Fiber Desktop — run Fiber (FNN) on your laptop without the “public node” headache",
          "topic_slug": "fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache",
          "author": "RetricSu",
          "created_at": "2026-05-12T01:36:19.973000+00:00",
          "updated_at": "2026-05-12T01:36:19.973000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/fiber-desktop-run-fiber-fnn-on-your-laptop-without-the-public-node-headache/10247/2",
          "content_text": "Awesome! I had the same thought about desktop app for fiber and so glad that someone built it!",
          "content_html": "<p>Awesome! I had the same thought about desktop app for fiber and so glad that someone built it!</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    },
    {
      "topic_id": 9995,
      "title": "Spark Program | Nervos Brain - A Global Developer Onboarding Engine and Cross-Language Hub Powered by Agentic RAG",
      "slug": "spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag",
      "url": "https://talk.nervos.org/t/spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag/9995",
      "created_at": "2026-02-25T09:58:43.726000+00:00",
      "last_posted_at": "2026-05-11T19:14:06.332000+00:00",
      "category_id": 49,
      "tags": [
        "In-Progress",
        "Spark-Program"
      ],
      "posters": [
        "Original Poster, Most Recent Poster",
        "Frequent Poster",
        "Frequent Poster",
        "Frequent Poster"
      ],
      "recent_posts": [
        {
          "post_id": 24281,
          "post_number": 38,
          "topic_id": 9995,
          "topic_title": "Spark Program | Nervos Brain - A Global Developer Onboarding Engine and Cross-Language Hub Powered by Agentic RAG",
          "topic_slug": "spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag",
          "author": "IrisNeko",
          "created_at": "2026-05-11T19:14:06.332000+00:00",
          "updated_at": "2026-05-11T19:14:06.332000+00:00",
          "reply_to_post_number": null,
          "url": "https://talk.nervos.org/t/spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag/9995/38",
          "content_text": "第九周周报\n一、本周目标\n本周重点承接 Telegram 群内测反馈，继续修复真实使用中暴露出来的回答质量、检索覆盖、消息格式和部署可复现问题。\n相比第八周，本周不再只关注“Bot 能否在群里稳定跑起来”，而是进一步关注：\n面向真实用户问题时，Agent 是否会主动检索足够资料。\n技术教程是否能优先使用现成框架和真实 API，而不是给出空泛 TODO。\nTelegram / Discord 长回复、代码块、链接和引用格式是否稳定。\n模型路由是否过于保守，是否需要更多 medium/high 档参与复杂任务。\n检索数据和 Qdrant 数据库是否能被其他人快速重建和部署。\n二、本周完成\n2.1 Telegram Markdown 长消息格式修复\n本周修复了 Telegram 长回答在分段发送时容易破坏 Markdown 格式的问题。\n之前系统主要依赖 MarkdownV2 字符串切分，长代码块或复杂格式在接近 Telegram 4096 字符限制时容易被硬切，导致代码块、链接、引用等格式错乱。\n本周改为使用 telegramify-markdown，将 Markdown 转成 Telegram Bot API 的 text + entities 结构，再按实体边界安全分段发送。这样 Telegram 端不再主要依赖 parse_mode=MarkdownV2，长回复中的代码块、标题、列表、链接、引用和中英文混排都更稳定。\n同时保留了 plain text fallback：如果 Telegram 发送 entities 失败，会移除 entities 和 parse_mode 后按纯文本重试，保证消息不会因为格式问题整体发送失败。\n2.2 Discord Runtime 与 Markdown 长消息修复\n本周进一步补齐了 Discord 端能力，使其不再只是一个较薄的收发适配层，而是更接近 Telegram 端的完整 runtime。\nDiscord 和 Telegram 的消息格式机制不同，因此本周没有复用 telegramify-markdown，而是为 Discord 引入 markdown-it-py 辅助 Markdown block 解析，并实现 Discord 专用安全分段逻辑。长 fenced code block 会按 Discord 2000 字符限制拆分，同时保证每段代码块闭合，避免长代码、链接、列表和引用在分段时破坏格式。\n同时补齐了 Discord 端多个线上必需能力：\n回复 Bot 消息时携带被回复内容快照，避免“继续说”“改一下”这类短追问丢失上下文。\nguild 默认仍采用 mention-only 策略，普通未提及消息不会触发 graph，也不会写入 memory。\n接入 memory service，处理后的用户消息和 Bot 回复会按 Discord guild/channel/thread/user 维度隔离写入。\n接入 feedback store，支持回答元数据、CSAT button 和 /feedback 文本反馈。\n接入 debug JSONL，用于后续定位检索、反思、引用和响应耗时问题。\n支持下载较小的文本附件，如 .txt、.md、.json、.yaml，并注入 graph 上下文。\n发送 payload 默认禁用 allowed_mentions，避免生成内容误 ping 用户或角色。\nrun_discord_bot.py 也同步补齐了 feedback、debug、memory context、延迟预算、附件大小、allowed guild/channel 等配置入口。Discord 端现在可以作为和 Telegram 平行的线上入口继续测试。\n2.3 模型路由新增 mini_high 档位\n本周发现模型路由过于保守，很多本应需要更认真推理的问题仍停留在 low 档，导致检索规划、反思判断和技术回答质量不稳定。\n为此新增了第四个业务档位：\nlow = gpt-5.4-mini + low\nmini_high = gpt-5.4-mini + high\nmedium = gpt-5.5 + low\nhigh = gpt-5.5 + high\nmini_high 用作低成本深思考档，主要用于 InfoGap 判断、检索规划、轻量反思、引用初筛和公开资料判断。这样简单问题仍可走 low，复杂但不必直接升级到 gpt-5.5 的任务可以走 mini_high，减少 low 和 medium 之间的断层。\n同时更新了 router prompt 和默认 fallback，让技术判断、检索规划和反思节点更容易使用 medium / high 档，而不是几乎全部落到 low。\n2.4 主动统一多库检索修复\n群内测中暴露出一个明显问题：用户提出 TS/JS、CCC、CKB 转账等实际开发问题时，Agent 有时没有主动检索相关文档、代码和论坛讨论，而是基于有限证据给出空泛回答。\n本周将检索策略调整为“默认统一多库检索”。也就是说，在技术教程、SDK/API、真实框架、代码示例、生态项目和用户纠错场景下，Agent 默认应把 docs、github_code、forum 看作一个统一知识库，而不是过早只查单一来源。\n主要调整包括：\nInfoGap prompt 更明确要求技术类问题主动检索。\nRetrieverPlanner prompt 默认使用无 source filter 的 qdrant_search。\n只有用户明确限定来源时，才优先专项查询。\nAnswerComposer 要求新手教程优先使用现成框架、官方示例和可运行路径。\nReflection 会把“用户要 TS/JS，但证据只有 Go SDK”判为偏题或证据不足。\n对“为什么不用 CCC”这类用户纠错，不再直答猜测，而应检索复核。\n这项修复的目标不是写死 CCC 规则，而是让 Agent 在面对真实技术问题时更主动、更全面地检索可用资料。\n2.5 检索数据扩容：CCC、Spore DOB 与 xUDT 相关资料\n为了补齐群内测中暴露的资料缺口，本周新增爬取并入库了多类资料。\n新增文档资料包括：\nCCC 相关 llms 文档。\nSpore / DOB cookbook。\nSpore docs。\nDOB decoder standalone server。\nSpore DOB 0 / DOB 1。\nxUDT logos 相关仓库资料。\n这些资料分别进入 GitHub 文档库和 GitHub 代码库，补强了 CCC、Spore DOB、xUDT、生态项目示例和真实代码检索能力。\n本周也新增了 run_web_text_ingest.py，用于将 llms.txt 这类纯文本 Web 文档规范化入库，避免以后遇到类似资料时只能临时手动处理。\n2.6 Qdrant Server 与三库部署链路完善\n本周进一步完善了 Qdrant server 模式。\n当前 Bot runtime 使用 Docker Qdrant server 作为向量服务，避免 Telegram / Discord 多进程同时访问本地 Qdrant 目录造成锁冲突。\n本周明确了数据发布边界：\nGitHub 仓库存 SQLite archive DB、source JSONL 和必要的大文件 LFS 对象。\ndata/qdrant_server/ 是 Docker 运行时目录，不提交 GitHub。\n其他人 clone 仓库后，通过脚本从 archive DB 重建 Docker Qdrant 三个 collection。\n云端 Qdrant 也可以用同一迁移脚本从 archive DB 重建。\n新增 bootstrap_qdrant_server.sh 后，部署流程更清晰：\ngit lfs pull\nbash bootstrap_qdrant_server.sh\n脚本会启动 Docker Qdrant，并从公开可提交的 archive DB 重建 docs、forum、github_code 三个 collection。\n当前三库验证结果为：\nnervos_docs: 1336\nnervos_talk_user_discussions: 13057\nnervos_github_code: 23247\n这意味着其他人 clone GitHub 仓库后，只需要准备环境、拉取 LFS、填写自己的密钥和 Bot token，就可以较快恢复 Bot 的检索能力。\n2.7 公开仓库部署边界进一步清晰\n本周继续梳理公开仓库和本地私有运行数据之间的边界。\n公开仓库应包含：\n代码、测试、脚本和配置模板。\n可公开的 docs / forum / github_code 检索数据。\nQdrant 重建脚本和部署说明。\nDocker compose 和环境文件。\n公开仓库不包含：\nconfig.yaml\nLLM API key\nTelegram / Discord Bot token\n群聊记录\ndebug events\nruntime logs\nmemory DB\nDocker Qdrant server 运行目录\n这样既能保证项目可复现部署，又不会把甲方或测试群的私密信息带进仓库。\n三、内测反馈带来的主要变化\n本周最典型的内测反馈是：用户并不是只需要“有一个回答”，而是需要“像一个懂开发路径的助手”。\n例如，当 TS/JS 用户想写 CKB 转账小应用时，Agent 不应该让用户从底层 Cell、Lock、OutPoint 全部自己实现，也不应该只给一个全 TODO 的骨架。更合理的方式是主动检索 CCC、官方示例、代码仓库和论坛讨论，然后基于现成框架给出最小可运行路径。\n这类反馈推动本周重点从“回答是否流畅”转向“回答是否真的有帮助”。对应的工程变化包括：\n更主动地检索公开资料。\n默认统一查多库，而不是过早限定来源。\n更激进地使用 medium / high 推理档位。\n对教程类回答提出更高要求，避免空泛 TODO。\n对 Telegram / Discord 格式和长消息发送做稳定性修复。\n四、测试与验证\n本周围绕格式、模型路由、检索和部署进行了多组回归验证。\n重点覆盖：\nTelegram Markdown entities 分段。\nTelegram send payload 中 entities 与 parse_mode 的兼容逻辑。\nDiscord Markdown 安全分段和 2000 字符限制。\nDiscord reply context、CSAT、feedback、debug、memory、文本附件处理。\n长代码块、标题、列表、链接、引用等格式发送。\nmini_high profile 加载和 fallback。\nfull graph router 对 mini_high 的识别。\n统一多库检索 planner 行为。\nQdrant server migration。\nGitHub docs/code ingestion。\nComposite retriever 多库合并。\nclone 后 Qdrant 三库重建流程。\n阶段性验证包括：\ntests/test_qdrant_server_migration.py tests/test_retrieval_unit.py: 12 passed\ntests/test_discord_bot_protocol_adapter.py tests/test_discord_bot_runtime.py tests/test_platform_formatter.py tests/test_telegram_bot_runtime.py tests/test_telegram_bot_protocol_adapter.py: 96 passed\n以及针对 ingestion、retrieval、formatter、Telegram runtime、Discord runtime 和 full graph 的多组专项测试。\n五、阶段性成果\n本周完成后，项目进入了更接近可交付测试的阶段：\nTelegram 长消息格式问题基本解决。\nDiscord runtime 和长消息格式能力基本补齐。\n模型路由不再只有 low / medium / high 三档，新增 mini_high 缓冲层。\nAgent 对技术类问题的主动检索策略更明确。\ndocs / forum / github_code 三库统一检索链路更清晰。\nCCC、Spore DOB、xUDT 等生态资料进入检索库。\nDocker Qdrant server 可以从 GitHub 中的 archive DB 快速重建。\n公开仓库和私密运行数据的边界进一步稳定。\n六、当前问题\n真实用户问题仍需要继续积累 bad case，特别是教程类、代码类和生态项目类问题。\nAgent 是否真的会稳定选用 CCC、Spore 等现成框架，还需要继续通过群内测观察。\nDiscord 端已经补齐核心 runtime，但仍需要真实频道环境继续验证按钮交互、附件和长消息体验。\nQdrant server 部署流程已有脚本，但还可以继续补充健康检查和长期守护方案。\n内测反馈还需要问卷化，否则主观反馈难以量化比较。\n七、下周计划（Week 10）\n下周重点从功能修复转向最终交付前收敛，主线是 Nervos Talk MCP、最终测试和用户反馈收集。\n实现 Nervos Talk MCP。\n将 Nervos Talk / forum 查询能力整理成 MCP 工具，使 Agent 能在需要社区讨论、生态案例、历史争议和用户经验时更直接地调用 Talk 数据，而不是只依赖离线检索库。\n完成最终测试与回归验证。\n对 Telegram、Discord、Qdrant server、三库检索、模型路由、formatter、feedback、memory 和部署脚本做最终集成测试，重点验证 clone 后重建、线上 Bot 长时间运行、长消息格式和真实问答链路。\n收集用户反馈。\n发放内测问卷并整理 Telegram / Discord 真实使用反馈，重点收集回答质量、检索可信度、上下文理解、响应速度、追问体验、引用可信度和整体可用性评价。\n将典型 bad case 沉淀为评测样例。\n把 CCC 教程、TS/JS 转账、Spore DOB、Fiber、xUDT、Nervos Talk 社区讨论等真实问题整理进 evaluation dataset，用于最终回答质量回归。\n继续做回答质量收敛。\n根据最终测试和用户反馈微调主动检索、回答生成、反思和模型路由策略，重点避免空泛 TODO、证据不足却强答、忽略用户技术栈等问题。",
          "content_html": "<h1><a name=\"p-24281-h-1\" class=\"anchor\" href=\"#p-24281-h-1\" aria-label=\"Heading link\"></a>第九周周报</h1>\n<h2><a name=\"p-24281-h-2\" class=\"anchor\" href=\"#p-24281-h-2\" aria-label=\"Heading link\"></a>一、本周目标</h2>\n<p>本周重点承接 Telegram 群内测反馈，继续修复真实使用中暴露出来的回答质量、检索覆盖、消息格式和部署可复现问题。</p>\n<p>相比第八周，本周不再只关注“Bot 能否在群里稳定跑起来”，而是进一步关注：</p>\n<ol>\n<li>\n<p>面向真实用户问题时，Agent 是否会主动检索足够资料。</p>\n</li>\n<li>\n<p>技术教程是否能优先使用现成框架和真实 API，而不是给出空泛 TODO。</p>\n</li>\n<li>\n<p>Telegram / Discord 长回复、代码块、链接和引用格式是否稳定。</p>\n</li>\n<li>\n<p>模型路由是否过于保守，是否需要更多 medium/high 档参与复杂任务。</p>\n</li>\n<li>\n<p>检索数据和 Qdrant 数据库是否能被其他人快速重建和部署。</p>\n</li>\n</ol>\n<h2><a name=\"p-24281-h-3\" class=\"anchor\" href=\"#p-24281-h-3\" aria-label=\"Heading link\"></a>二、本周完成</h2>\n<h3><a name=\"p-24281-h-21-telegram-markdown-4\" class=\"anchor\" href=\"#p-24281-h-21-telegram-markdown-4\" aria-label=\"Heading link\"></a>2.1 Telegram Markdown 长消息格式修复</h3>\n<p>本周修复了 Telegram 长回答在分段发送时容易破坏 Markdown 格式的问题。</p>\n<p>之前系统主要依赖 MarkdownV2 字符串切分，长代码块或复杂格式在接近 Telegram 4096 字符限制时容易被硬切，导致代码块、链接、引用等格式错乱。</p>\n<p>本周改为使用 <code>telegramify-markdown</code>，将 Markdown 转成 Telegram Bot API 的 <code>text + entities</code> 结构，再按实体边界安全分段发送。这样 Telegram 端不再主要依赖 <code>parse_mode=MarkdownV2</code>，长回复中的代码块、标题、列表、链接、引用和中英文混排都更稳定。</p>\n<p>同时保留了 plain text fallback：如果 Telegram 发送 entities 失败，会移除 entities 和 parse_mode 后按纯文本重试，保证消息不会因为格式问题整体发送失败。</p>\n<h3><a name=\"p-24281-h-22-discord-runtime-markdown-5\" class=\"anchor\" href=\"#p-24281-h-22-discord-runtime-markdown-5\" aria-label=\"Heading link\"></a>2.2 Discord Runtime 与 Markdown 长消息修复</h3>\n<p>本周进一步补齐了 Discord 端能力，使其不再只是一个较薄的收发适配层，而是更接近 Telegram 端的完整 runtime。</p>\n<p>Discord 和 Telegram 的消息格式机制不同，因此本周没有复用 <code>telegramify-markdown</code>，而是为 Discord 引入 <code>markdown-it-py</code> 辅助 Markdown block 解析，并实现 Discord 专用安全分段逻辑。长 fenced code block 会按 Discord 2000 字符限制拆分，同时保证每段代码块闭合，避免长代码、链接、列表和引用在分段时破坏格式。</p>\n<p>同时补齐了 Discord 端多个线上必需能力：</p>\n<ol>\n<li>\n<p>回复 Bot 消息时携带被回复内容快照，避免“继续说”“改一下”这类短追问丢失上下文。</p>\n</li>\n<li>\n<p>guild 默认仍采用 mention-only 策略，普通未提及消息不会触发 graph，也不会写入 memory。</p>\n</li>\n<li>\n<p>接入 memory service，处理后的用户消息和 Bot 回复会按 Discord guild/channel/thread/user 维度隔离写入。</p>\n</li>\n<li>\n<p>接入 feedback store，支持回答元数据、CSAT button 和 <code>/feedback</code> 文本反馈。</p>\n</li>\n<li>\n<p>接入 debug JSONL，用于后续定位检索、反思、引用和响应耗时问题。</p>\n</li>\n<li>\n<p>支持下载较小的文本附件，如 <code>.txt</code>、<code>.md</code>、<code>.json</code>、<code>.yaml</code>，并注入 graph 上下文。</p>\n</li>\n<li>\n<p>发送 payload 默认禁用 <code>allowed_mentions</code>，避免生成内容误 ping 用户或角色。</p>\n</li>\n</ol>\n<p><code>run_discord_bot.py</code> 也同步补齐了 feedback、debug、memory context、延迟预算、附件大小、allowed guild/channel 等配置入口。Discord 端现在可以作为和 Telegram 平行的线上入口继续测试。</p>\n<h3><a name=\"p-24281-h-23-mini_high-6\" class=\"anchor\" href=\"#p-24281-h-23-mini_high-6\" aria-label=\"Heading link\"></a>2.3 模型路由新增 <code>mini_high</code> 档位</h3>\n<p>本周发现模型路由过于保守，很多本应需要更认真推理的问题仍停留在 low 档，导致检索规划、反思判断和技术回答质量不稳定。</p>\n<p>为此新增了第四个业务档位：</p>\n<pre><code class=\"lang-plaintext\">\nlow = gpt-5.4-mini + low\n\nmini_high = gpt-5.4-mini + high\n\nmedium = gpt-5.5 + low\n\nhigh = gpt-5.5 + high\n\n</code></pre>\n<p><code>mini_high</code> 用作低成本深思考档，主要用于 InfoGap 判断、检索规划、轻量反思、引用初筛和公开资料判断。这样简单问题仍可走 low，复杂但不必直接升级到 gpt-5.5 的任务可以走 mini_high，减少 low 和 medium 之间的断层。</p>\n<p>同时更新了 router prompt 和默认 fallback，让技术判断、检索规划和反思节点更容易使用 medium / high 档，而不是几乎全部落到 low。</p>\n<h3><a name=\"p-24281-h-24-7\" class=\"anchor\" href=\"#p-24281-h-24-7\" aria-label=\"Heading link\"></a>2.4 主动统一多库检索修复</h3>\n<p>群内测中暴露出一个明显问题：用户提出 TS/JS、CCC、CKB 转账等实际开发问题时，Agent 有时没有主动检索相关文档、代码和论坛讨论，而是基于有限证据给出空泛回答。</p>\n<p>本周将检索策略调整为“默认统一多库检索”。也就是说，在技术教程、SDK/API、真实框架、代码示例、生态项目和用户纠错场景下，Agent 默认应把 docs、github_code、forum 看作一个统一知识库，而不是过早只查单一来源。</p>\n<p>主要调整包括：</p>\n<ol>\n<li>\n<p>InfoGap prompt 更明确要求技术类问题主动检索。</p>\n</li>\n<li>\n<p>RetrieverPlanner prompt 默认使用无 source filter 的 <code>qdrant_search</code>。</p>\n</li>\n<li>\n<p>只有用户明确限定来源时，才优先专项查询。</p>\n</li>\n<li>\n<p>AnswerComposer 要求新手教程优先使用现成框架、官方示例和可运行路径。</p>\n</li>\n<li>\n<p>Reflection 会把“用户要 TS/JS，但证据只有 Go SDK”判为偏题或证据不足。</p>\n</li>\n<li>\n<p>对“为什么不用 CCC”这类用户纠错，不再直答猜测，而应检索复核。</p>\n</li>\n</ol>\n<p>这项修复的目标不是写死 CCC 规则，而是让 Agent 在面对真实技术问题时更主动、更全面地检索可用资料。</p>\n<h3><a name=\"p-24281-h-25-cccspore-dob-xudt-8\" class=\"anchor\" href=\"#p-24281-h-25-cccspore-dob-xudt-8\" aria-label=\"Heading link\"></a>2.5 检索数据扩容：CCC、Spore DOB 与 xUDT 相关资料</h3>\n<p>为了补齐群内测中暴露的资料缺口，本周新增爬取并入库了多类资料。</p>\n<p>新增文档资料包括：</p>\n<ol>\n<li>\n<p>CCC 相关 llms 文档。</p>\n</li>\n<li>\n<p>Spore / DOB cookbook。</p>\n</li>\n<li>\n<p>Spore docs。</p>\n</li>\n<li>\n<p>DOB decoder standalone server。</p>\n</li>\n<li>\n<p>Spore DOB 0 / DOB 1。</p>\n</li>\n<li>\n<p>xUDT logos 相关仓库资料。</p>\n</li>\n</ol>\n<p>这些资料分别进入 GitHub 文档库和 GitHub 代码库，补强了 CCC、Spore DOB、xUDT、生态项目示例和真实代码检索能力。</p>\n<p>本周也新增了 <code>run_web_text_ingest.py</code>，用于将 <code>llms.txt</code> 这类纯文本 Web 文档规范化入库，避免以后遇到类似资料时只能临时手动处理。</p>\n<h3><a name=\"p-24281-h-26-qdrant-server-9\" class=\"anchor\" href=\"#p-24281-h-26-qdrant-server-9\" aria-label=\"Heading link\"></a>2.6 Qdrant Server 与三库部署链路完善</h3>\n<p>本周进一步完善了 Qdrant server 模式。</p>\n<p>当前 Bot runtime 使用 Docker Qdrant server 作为向量服务，避免 Telegram / Discord 多进程同时访问本地 Qdrant 目录造成锁冲突。</p>\n<p>本周明确了数据发布边界：</p>\n<ol>\n<li>\n<p>GitHub 仓库存 SQLite archive DB、source JSONL 和必要的大文件 LFS 对象。</p>\n</li>\n<li>\n<p><code>data/qdrant_server/</code> 是 Docker 运行时目录，不提交 GitHub。</p>\n</li>\n<li>\n<p>其他人 clone 仓库后，通过脚本从 archive DB 重建 Docker Qdrant 三个 collection。</p>\n</li>\n<li>\n<p>云端 Qdrant 也可以用同一迁移脚本从 archive DB 重建。</p>\n</li>\n</ol>\n<p>新增 <code>bootstrap_qdrant_server.sh</code> 后，部署流程更清晰：</p>\n<pre data-code-wrap=\"bash\"><code class=\"lang-bash\">\ngit lfs pull\n\nbash bootstrap_qdrant_server.sh\n\n</code></pre>\n<p>脚本会启动 Docker Qdrant，并从公开可提交的 archive DB 重建 docs、forum、github_code 三个 collection。</p>\n<p>当前三库验证结果为：</p>\n<pre><code class=\"lang-plaintext\">\nnervos_docs: 1336\n\nnervos_talk_user_discussions: 13057\n\nnervos_github_code: 23247\n\n</code></pre>\n<p>这意味着其他人 clone GitHub 仓库后，只需要准备环境、拉取 LFS、填写自己的密钥和 Bot token，就可以较快恢复 Bot 的检索能力。</p>\n<h3><a name=\"p-24281-h-27-10\" class=\"anchor\" href=\"#p-24281-h-27-10\" aria-label=\"Heading link\"></a>2.7 公开仓库部署边界进一步清晰</h3>\n<p>本周继续梳理公开仓库和本地私有运行数据之间的边界。</p>\n<p>公开仓库应包含：</p>\n<ol>\n<li>\n<p>代码、测试、脚本和配置模板。</p>\n</li>\n<li>\n<p>可公开的 docs / forum / github_code 检索数据。</p>\n</li>\n<li>\n<p>Qdrant 重建脚本和部署说明。</p>\n</li>\n<li>\n<p>Docker compose 和环境文件。</p>\n</li>\n</ol>\n<p>公开仓库不包含：</p>\n<ol>\n<li>\n<p><code>config.yaml</code></p>\n</li>\n<li>\n<p>LLM API key</p>\n</li>\n<li>\n<p>Telegram / Discord Bot token</p>\n</li>\n<li>\n<p>群聊记录</p>\n</li>\n<li>\n<p>debug events</p>\n</li>\n<li>\n<p>runtime logs</p>\n</li>\n<li>\n<p>memory DB</p>\n</li>\n<li>\n<p>Docker Qdrant server 运行目录</p>\n</li>\n</ol>\n<p>这样既能保证项目可复现部署，又不会把甲方或测试群的私密信息带进仓库。</p>\n<h2><a name=\"p-24281-h-11\" class=\"anchor\" href=\"#p-24281-h-11\" aria-label=\"Heading link\"></a>三、内测反馈带来的主要变化</h2>\n<p>本周最典型的内测反馈是：用户并不是只需要“有一个回答”，而是需要“像一个懂开发路径的助手”。</p>\n<p>例如，当 TS/JS 用户想写 CKB 转账小应用时，Agent 不应该让用户从底层 Cell、Lock、OutPoint 全部自己实现，也不应该只给一个全 TODO 的骨架。更合理的方式是主动检索 CCC、官方示例、代码仓库和论坛讨论，然后基于现成框架给出最小可运行路径。</p>\n<p>这类反馈推动本周重点从“回答是否流畅”转向“回答是否真的有帮助”。对应的工程变化包括：</p>\n<ol>\n<li>\n<p>更主动地检索公开资料。</p>\n</li>\n<li>\n<p>默认统一查多库，而不是过早限定来源。</p>\n</li>\n<li>\n<p>更激进地使用 medium / high 推理档位。</p>\n</li>\n<li>\n<p>对教程类回答提出更高要求，避免空泛 TODO。</p>\n</li>\n<li>\n<p>对 Telegram / Discord 格式和长消息发送做稳定性修复。</p>\n</li>\n</ol>\n<h2><a name=\"p-24281-h-12\" class=\"anchor\" href=\"#p-24281-h-12\" aria-label=\"Heading link\"></a>四、测试与验证</h2>\n<p>本周围绕格式、模型路由、检索和部署进行了多组回归验证。</p>\n<p>重点覆盖：</p>\n<ol>\n<li>\n<p>Telegram Markdown entities 分段。</p>\n</li>\n<li>\n<p>Telegram send payload 中 entities 与 parse_mode 的兼容逻辑。</p>\n</li>\n<li>\n<p>Discord Markdown 安全分段和 2000 字符限制。</p>\n</li>\n<li>\n<p>Discord reply context、CSAT、feedback、debug、memory、文本附件处理。</p>\n</li>\n<li>\n<p>长代码块、标题、列表、链接、引用等格式发送。</p>\n</li>\n<li>\n<p><code>mini_high</code> profile 加载和 fallback。</p>\n</li>\n<li>\n<p>full graph router 对 <code>mini_high</code> 的识别。</p>\n</li>\n<li>\n<p>统一多库检索 planner 行为。</p>\n</li>\n<li>\n<p>Qdrant server migration。</p>\n</li>\n<li>\n<p>GitHub docs/code ingestion。</p>\n</li>\n<li>\n<p>Composite retriever 多库合并。</p>\n</li>\n<li>\n<p>clone 后 Qdrant 三库重建流程。</p>\n</li>\n</ol>\n<p>阶段性验证包括：</p>\n<pre><code class=\"lang-plaintext\">\ntests/test_qdrant_server_migration.py tests/test_retrieval_unit.py: 12 passed\n\ntests/test_discord_bot_protocol_adapter.py tests/test_discord_bot_runtime.py tests/test_platform_formatter.py tests/test_telegram_bot_runtime.py tests/test_telegram_bot_protocol_adapter.py: 96 passed\n\n</code></pre>\n<p>以及针对 ingestion、retrieval、formatter、Telegram runtime、Discord runtime 和 full graph 的多组专项测试。</p>\n<h2><a name=\"p-24281-h-13\" class=\"anchor\" href=\"#p-24281-h-13\" aria-label=\"Heading link\"></a>五、阶段性成果</h2>\n<p>本周完成后，项目进入了更接近可交付测试的阶段：</p>\n<ol>\n<li>\n<p>Telegram 长消息格式问题基本解决。</p>\n</li>\n<li>\n<p>Discord runtime 和长消息格式能力基本补齐。</p>\n</li>\n<li>\n<p>模型路由不再只有 low / medium / high 三档，新增 mini_high 缓冲层。</p>\n</li>\n<li>\n<p>Agent 对技术类问题的主动检索策略更明确。</p>\n</li>\n<li>\n<p>docs / forum / github_code 三库统一检索链路更清晰。</p>\n</li>\n<li>\n<p>CCC、Spore DOB、xUDT 等生态资料进入检索库。</p>\n</li>\n<li>\n<p>Docker Qdrant server 可以从 GitHub 中的 archive DB 快速重建。</p>\n</li>\n<li>\n<p>公开仓库和私密运行数据的边界进一步稳定。</p>\n</li>\n</ol>\n<h2><a name=\"p-24281-h-14\" class=\"anchor\" href=\"#p-24281-h-14\" aria-label=\"Heading link\"></a>六、当前问题</h2>\n<ol>\n<li>\n<p>真实用户问题仍需要继续积累 bad case，特别是教程类、代码类和生态项目类问题。</p>\n</li>\n<li>\n<p>Agent 是否真的会稳定选用 CCC、Spore 等现成框架，还需要继续通过群内测观察。</p>\n</li>\n<li>\n<p>Discord 端已经补齐核心 runtime，但仍需要真实频道环境继续验证按钮交互、附件和长消息体验。</p>\n</li>\n<li>\n<p>Qdrant server 部署流程已有脚本，但还可以继续补充健康检查和长期守护方案。</p>\n</li>\n<li>\n<p>内测反馈还需要问卷化，否则主观反馈难以量化比较。</p>\n</li>\n</ol>\n<h2><a name=\"p-24281-week-10-15\" class=\"anchor\" href=\"#p-24281-week-10-15\" aria-label=\"Heading link\"></a>七、下周计划（Week 10）</h2>\n<p>下周重点从功能修复转向最终交付前收敛，主线是 Nervos Talk MCP、最终测试和用户反馈收集。</p>\n<ol>\n<li>实现 Nervos Talk MCP。</li>\n</ol>\n<p>将 Nervos Talk / forum 查询能力整理成 MCP 工具，使 Agent 能在需要社区讨论、生态案例、历史争议和用户经验时更直接地调用 Talk 数据，而不是只依赖离线检索库。</p>\n<ol start=\"2\">\n<li>完成最终测试与回归验证。</li>\n</ol>\n<p>对 Telegram、Discord、Qdrant server、三库检索、模型路由、formatter、feedback、memory 和部署脚本做最终集成测试，重点验证 clone 后重建、线上 Bot 长时间运行、长消息格式和真实问答链路。</p>\n<ol start=\"3\">\n<li>收集用户反馈。</li>\n</ol>\n<p>发放内测问卷并整理 Telegram / Discord 真实使用反馈，重点收集回答质量、检索可信度、上下文理解、响应速度、追问体验、引用可信度和整体可用性评价。</p>\n<ol start=\"4\">\n<li>将典型 bad case 沉淀为评测样例。</li>\n</ol>\n<p>把 CCC 教程、TS/JS 转账、Spore DOB、Fiber、xUDT、Nervos Talk 社区讨论等真实问题整理进 evaluation dataset，用于最终回答质量回归。</p>\n<ol start=\"5\">\n<li>继续做回答质量收敛。</li>\n</ol>\n<p>根据最终测试和用户反馈微调主动检索、回答生成、反思和模型路由策略，重点避免空泛 TODO、证据不足却强答、忽略用户技术栈等问题。</p>",
          "like_count": 0,
          "quote_count": 0
        }
      ]
    }
  ]
}