Implementation, Rollout, and Steward Recruitment
舟舟 tovarishch (2025-12-01T06:08:43, Nervos Nation, edited 2025-12-01T06:51:01)
DAO v1.1 Milestone 1 (Testnet MVP) delivered 
Test environment: https://ccfdao.dev
Code repos: CKB Community Fund DAO 1.1 · GitHub
Thank you for your support and trust. Welcome to explore and share feedback.
Details
[DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #85 by zz_tovarishch
georgiev ↾⇃ (2025-12-01T09:53:22, Nervos Nation, edited 2025-12-01T10:04:11)
Replying to this message from 舟舟 tovarishch:
DAO v1.1 Milestone 1 (Testnet MVP) delivered
Test environment: https://ccfdao.dev
Code repos: CKB Community Fund DAO 1.1 · GitHub
Thank you for your support and trust. Welcome to explore and share feedback…
If I may ask.. what is the reason first property team to serve for one year, after that for a half?
舟舟 tovarishch (2025-12-01T09:59:26, Nervos Nation, edited 2025-12-01T09:59:50)
Replying to this message from georgiev ↾⇃:
If I may ask.. what is the reason first property team to serve for one year, after that for a half?
oh it’s a typo. Based on the proposal, each team will serve for one year. Thanks for pointing out this problem. I’ll have the front end modify it.
舟舟 tovarishch (2025-12-04T15:54:52, Nervos Nation, edited 2025-12-04T16:44:58)
Replying to this message from 舟舟 tovarishch:
DAO v1.1 Milestone 1 (Testnet MVP) delivered
Test environment: https://ccfdao.dev
Code repos: CKB Community Fund DAO 1.1 · GitHub
Thank you for your support and trust. Welcome to explore and share feedback…
DAO v1.1 Milestone 1 Infrastructure Expense Disclosure 
Domains: $19.7
Servers: Test environment currently shares with BBS; dedicated test and production servers will be purchased before Milestone 2
Total expenses: $19.7 (0.2% of $10,000 infrastructure budget)
As committed, all savings will be returned to DAO treasury.
Full report[DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #86 by zz_tovarishch
舟舟 tovarishch (2025-12-13T05:34:20, Nervos Nation, edited 2025-12-13T08:16:06)
DAO Transitional Period Policy Announcement
DAO Funds Management Committee releases transitional arrangements (until v1.1 takes effect):
Proposals accepted during transition, processed under v1.0 rules
Metaforo vulnerability being fixed; manual verification if needed
No new meta-rule proposals during transition
@zz_tovarishch (Talk account) is responsible for daily coordination
*Terry will personally donate CKB and reach out to other donors to help v1.0-approved projects navigate price volatility.
舟舟 tovarishch (2025-12-20T09:28:20, Nervos Nation, edited 2025-12-21T02:54:47)
Replying to this message from 舟舟 tovarishch:
Following community scrutiny and a rigorous investigation by the DAO Multisig Committee, the DAO v1.1 proposal has passed with 75.2% approval: https://talk.nervos.org/t/dis-community-fund-dao-v1-1-web5-community-f…
Recruitment | DAO v1.1 Inaugural Steward Team Members
Seeking community members to provide professional services to the DAO:
Proposal process coordination
Milestone verification
Governance communication
$500 USD/month
Deadline: Jan 15, 2025
Stewards serve, not decide. We expect and appreciate your enthusiasm, expertise and neutrality.
Apply here 招募 Recruitment | DAO v1.1 首届物业团队成员 Inaugural Steward Team Members
舟舟 tovarishch (2025-12-20T17:53:29, Nervos Nation, edited 2025-12-20T22:01:28)
Replying to this message from 舟舟 tovarishch:
DAO v1.1 Milestone 1 Infrastructure Expense Disclosure
Domains: $19.7
Servers: Test environment currently shares with BBS; dedicated test and production servers will be purchased before Milestone 2
Total expenses: $1…
Dear community, a quick update, DAO V1.1’s kick-off (10%) and M1 (52%) funds have been paid by the DAO Treasury:
Kick-off: https://explorer.nervos.org/transaction/0x1cc067b60fe869704d48ab537b36f15ecdf8851b27b93b6bb2e67be79681675b
Details: 29,231,218*0.1 = 2,923,121.8 CKB
M1: https://explorer.nervos.org/transaction/0x2238842cbff411e10c63c316ca9bd4efabcd0e3861d29d1cf9a483b6631eb97e
Details: 29,231,218*0.52 = 15,200,233.36 CKB
Additionally, according to Transitional Policy Statement (Community Fund DAO v1.1), Terry subsidized the funds:
Details: (100000*(10%+52%)-(2,923,121.8+15,200,233.36)*0.002287)/0.002287 = 8,986,395.61 CKB
木南Lynna App5 (2025-12-23T07:49:42, Nervos Nation)
https://x.com/CKBEcoFund/status/2003357027448602943?s=20
Alex (2025-12-23T15:51:36, Nervos Nation)
Replying to this message from 木南Lynna App5:
what does this mean?
舟舟 tovarishch (2025-12-23T16:03:20, Nervos Nation, edited 2025-12-24T01:26:18)
Replying to this message from Alex:
what does this mean?
Hi Alex, it’s the form of this requirement 招募 Recruitment | DAO v1.1 首届物业团队成员 Inaugural Steward Team Members
舟舟 tovarishch (2025-12-24T10:56:58, Nervos Nation, edited 2025-12-24T13:30:51)
DAO v1.1 Weekly Progress Report (12.24)
Dear community, we are launching regular updates on project progress. Starting this week, we will:
Publish weekly progress reports, including Dev Logs, steward team formation progress, and other important matters
Organize bi-weekly AMAs to answer community questions and discuss project directions
These updates will continue until v1.1 mainnet officially launches and the DAO Stewards team formally takes over the platform’s daily operations. Through this approach, we hope to give the community complete visibility into the project’s progress and enable timely feedback.
This week’s dev progress:
15 commits across 4 repos
Security fixes, editor optimization
Management center, meta-rules docs live
Steward recruitment open
Test env: https://ccfdao.dev
Full report
Merry Xmas. 
舟舟 tovarishch (2025-12-28T16:54:27, Nervos Nation, edited 2025-12-28T18:04:18)
DAO v1.1 AMA
Time: Dec 30, 2025
23:00 UTC+8
07:00 PST
16:00 CET
Duration: ~1 hour
Venue: Google Meet
https://meet.google.com/bgr-cmee-jzu
Agenda:
Development progress update
Steward recruitment update
Community Q&A
Language: Chinese (with AI live subtitles)
AI interpretation: 讯飞同传
All community members welcome!
舟舟 tovarishch (2025-12-30T15:29:42, Nervos Nation, edited 2025-12-30T15:30:02)
Replying to this message from 舟舟 tovarishch:
Time: Dec 30, 2025
23:00 UTC+8
07:00 PST…
Reminder: DAO v1.1 AMA starts in 30 minutes
Time: 23:00 UTC+8 / 07:00 PST / 16:00 CET
Meeting link: https://meet.google.com/bgr-cmee-jzu
AI interpretation: 讯飞同传
Agenda includes dev progress update, steward recruitment update, and community Q&A.
See you there!
舟舟 tovarishch (2025-12-30T22:49:55, Nervos Nation, edited 2025-12-30T23:02:07)
Sorry, but you can find progress below
DAO v1.1 Progress Report #2
- AMA #1 completed
- This week’s dev: See attached pics
- Steward recruitment: 11 applications received, thank you community
First member confirmed: Haoyang @haoyang94 (full-stack dev, Polkadot DAO experience) Recruitment open until Jan 15
Full report [DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #90 by zz_tovarishch
haoyang li (2026-01-07T04:54:19, Nervos Nation, edited 2026-01-07T08:15:23)
哈咯大家好，
这是DAO v1.1的第三周进展报告摘要, 工作主要聚焦在平台功能开发和用户体验优化两个方面。
开发进度：
提案状态筛选功能
Markdown支持优化
会议管理功能
个人治理记录功能
文档站集成
完成率：7/9 (78%)
测试：https://ccfdao.dev
开发进度详细介绍：
————————————————————
Hey community,
The third week’s progress report for DAO v1.1 is here! We focused on developing core platform functionalities and the improvements of user experiences.
Progress:
Proposal status filtering
Markdown support optimization
Meeting management features
Personal governance records
Documentation site integration
Completion rate: 7/9 (78%)
Test: https://ccfdao.dev
————————————————————
You can find more details here:
Phroi (No DM) (2026-01-12T00:11:43, Nervos Nation)
You vote by binding in Metaforo a Neuron address with Nervos DAO deposits
C B (2026-01-12T00:38:12, Nervos Nation)
Replying to this message from Phroi (No DM):
You vote by binding in Metaforo a Neuron address with Nervos DAO deposits
what about joy id
Phroi (No DM) (2026-01-12T02:45:19, Nervos Nation)
Replying to this message from C B:
what about joy id
- I binded JoyID to Metaforo
- I added CKB to said address
- I deposited thru nervdao
- Tried to vote
So I would say: nope, JoyID AFAIK is not supported for voting 
舟舟 tovarishch (2026-01-13T04:26:32, Nervos Nation, edited 2026-01-13T15:30:30)
DAO v1.1 AMA
Time: Jan 15, 2026
23:00 UTC+8
07:00 PST
16:00 CET
Duration: ~1 hour
Venue: Google Meet
https://meet.google.com/bfh-juvf-ucu
(with AI live subtitles)
Agenda:
Development & steward recruitment progress update
Community Q&A
All community members welcome!
Phroi (No DM) (2026-01-13T17:53:04, Nervos Nation)
Hopefully Community DAO v1.1 will be better
C B (2026-01-13T18:01:26, Nervos Nation)
Replying to this message from Phroi (No DM):
Hopefully Community DAO v1.1 will be better
can they do the proposal again when it’s live?
Phroi (No DM) (2026-01-13T18:08:29, Nervos Nation)
Replying to this message from C B:
can they do the proposal again when it’s live?
AFAIK no, once this vote conclude, this is a closed door. Question asked would be:
- What would another proposal improve upon?
- Community already expressed its vote, why we need to vote again?
@zz_tovarishch feel free to correct me 
C B (2026-01-13T18:32:53, Nervos Nation)
i haven’t used neuron in years
舟舟 tovarishch (2026-01-13T18:37:12, Nervos Nation, edited 2026-01-14T00:19:15)
Replying to this message from C B:
i haven’t used neuron in years
Thanks for raising this @C B and @phroi for the explanation.
You’re right that Metaforo only supports Neuron, which excludes JoyID users from participating in this vote. This vote follows v1.0 rules and uses available infrastructure. While not perfect, it’s the legitimate governance process for now. V1.1 platform (MVP, ongoing development) will support broader participation including JoyID users.
舟舟 tovarishch (2026-01-13T18:37:21, Nervos Nation, edited 2026-01-14T00:19:17)
Replying to this message from Phroi (No DM):
AFAIK no, once this vote conclude, this is a closed door. Question asked would be:
- What would another proposal improve upon?
- Community already expressed its vote, why we need to vote again?
…
For re-proposing, v1.0 rules don’t explicitly address whether proposals can be resubmitted after failing, or under what conditions.
Based on the defined process flow (Discussion Stage, Voting Stage, Execution Stage), a resubmitted proposal would logically need to go through the full process again, but this hasn’t been formally clarified. Moreover, questions like “what constitutes a meaningful revision” or “is re-voting on similar proposals appropriate” aren’t defined in the current rules.
If this scenario comes up, it would be a governance question for the community and DAO Funds Management Committee to address.
telmo.bit ROTNT (2026-01-13T22:12:05, Nervos Nation)
Pardon my question sirs, any option available to deposit and withdraw ckb from the DAO with joyid?
Night Lantern (2026-01-13T22:13:13, Nervos Nation, edited 2026-01-13T22:14:41)
not yet as i understand it will be implemented after v1.1 goes live
C B (2026-01-14T00:19:17, Nervos Nation)
Replying to this message from 舟舟 tovarishch:
Thanks for raising this @C B and @phroi for the explanation.
You’re right that Metaforo only supports Neuron, which excludes JoyID users from participating in this vote. [This vote](https://talk.nervos.org/t/dis-ckb-i…
don’t you think it’s worth pausing proposals will the new version is up people like me can’t vote even if i want to
舟舟 tovarishch (2026-01-14T08:11:56, Nervos Nation, edited 2026-01-14T11:51:17)
Replying to this message from C B:
don’t you think it’s worth pausing proposals will the new version is up people like me can’t vote even if i want to
Hi C B, I understand your frustration. This is also one point of the motivation for the v1.1 proposal team to develop a new platform.
The transitional period policy was set by the DAO Funds Management Committee to bridge v1.0 and v1.1 governance. It allows proposals to continue under v1.0 rules rather than pausing the DAO entirely during development.
The Rosen Bridge proposal team chose to proceed under this policy. That’s their call as proposers, knowing the participation limitations.
舟舟 tovarishch (2026-01-14T18:21:31, Nervos Nation, edited 2026-01-14T20:09:59)
Replying to this message from 舟舟 tovarishch:
Voting Security Measures
Key points:
- Unbind function disabled
- Post-voting verification process…
Thanks to @sailoryx’s work on the metaforo verification tool
As the transition period coordinator, I will use this tool along with manual verification to conduct voting checks.
舟舟 tovarishch (2026-01-15T00:04:14, Nervos Nation, edited 2026-01-15T01:11:26)
Rosen Bridge Proposal Voting Progress
Total voting weight cast: 241,208,439 CKB
Quorum: 241,208,439 / 82,070,709 (met)
Approval: 36.64% (51% required to pass)
Time remaining: ~2 days
All community members with Nervos DAO deposits are eligible to participate. Whether you support or oppose, voting is the way to have your preference counted in the final outcome.
Vote here https://dao.ckb.community/thread/vot-ckb-integration-for-rosen-bridge-66568
-–
Quick process note from transition coordination
I’ve seen some concerns about voting legitimacy.
To keep the discussion evidence-based, I ran the open-source CKB DAO Watchdog. It cross-checks Metaforo-recorded voting weights against on-chain Nervos DAO deposit weights for each voter and flags discrepancies via need_review.
In the latest run (20260115064547, UTC+8), no discrepancies were flagged on either side (need_review = false). This indicates the Metaforo-recorded weights match the on-chain DAO deposit weights at the time of verification. (This check is about weight consistency, not identity attribution.)
Please feel free to discuss the proposal itself. If you suspect an issue, sharing concrete evidence will be appreciated and help everyone review.
Tool: GitHub - CKBFansDAO/ckb-dao-watchdog: Community-driven tools for auditing and verifying CKB DAO governance voting results. · GitHub
Verification logs: ckb-dao-watchdog/dao-v1.0/Verification Logs at main · kydchen/ckb-dao-watchdog · GitHub
Hanssen (2026-01-15T14:57:19, Nervos Nation, edited 2026-01-15T15:07:42)
The DAO 1.1 proposal brought people back into the spotlight regarding Nervos DAO voting, and with a more discerning eye.
Hanssen (2026-01-15T15:01:29, Nervos Nation, edited 2026-01-15T15:23:11)
On one hand, I’m happy that people are willing to participate in the voting. On the other hand, I’m worried about the increased threshold for DAOs. I hope this won’t make DAO proposals a thankless task, and perhaps DAO 1.1 will bring some improvements.
舟舟 tovarishch (2026-01-15T15:09:11, Nervos Nation)
Replying to this message from 舟舟 tovarishch:
Time: Jan 15, 2026
23:00 UTC+8
07:00 PST…
Dear community, the AMA will be in 1h
Phroi (No DM) (2026-01-15T15:59:59, Nervos Nation, edited 2026-01-15T16:00:45)
Replying to this message from Hanssen:
On one hand, I’m happy that people are willing to participate in the voting. On the other hand, I’m worried about the increased threshold for DAOs. I hope this won’t make DAO proposals a thankless task, and perhaps DA…
That’s why I really hope that CommunityDAO v1.1 will be nimble enough to be able to adapt to this ever changing voting landscape
舟舟 tovarishch (2026-01-15T17:26:17, Nervos Nation, edited 2026-01-15T17:37:41)
Replying to this message from 舟舟 tovarishch:
Dear community, the AMA will be in 1h
DAO v1.1 Weekly Sync
This week, the platform pushed forward the integration testing of the core governance flow while improving milestone voting UX (voting details, error handling, and avoiding duplicate requests). The frontend also went through a round of architecture cleanup (unified logger, unified HTTP error handling, removing unused rich-text editor deps, CSS co-location). On the backend, vote tx creation is now integrated into proposal/task workflows. Relayer has completed a standalone demo and fixed sync issues, and will be integrated after the governance flow is fully wired. Docs added an English binding guide and more FAQs.
In today’s AMA, @haoyang94 mentioned that steward recruitment closed on Jan 15, interviews are in progress, and the roster will be announced alongside the DAO v1.1 launch.
Nervos talk: [DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #93 by zz_tovarishch
AMA Record: https://drive.google.com/file/d/1uxMbhi_i0WSB7PfjD_51uV5qFgtB4Am_/view?usp=sharing
AMA CN/EN Script: Notion
舟舟 tovarishch (2026-01-17T01:02:52, Nervos Nation, edited 2026-01-17T01:03:08)
Rosen Bridge Proposal Voting has now closed
Preliminary outcome: PASSED (Approval: 64.11%, Total voting weight: 515,967,370 CKB).
Next, I will run a post-close verification using CKB DAO Watchdog to cross-check Metaforo-recorded voting weights against on-chain Nervos DAO deposit weights, along with a manual check. I will share the verification logs with the committee for final confirmation of whether the result is valid per the process.
舟舟 tovarishch (2026-01-21T07:35:00, Nervos Nation, edited 2026-01-21T07:48:15)
Replying to this message from 舟舟 tovarishch:
Rosen Bridge Proposal Voting has now closed
Preliminary outcome: PASSED (Approval: 64.11%, Total voting weight: 515,967,370 CKB).
…
Rosen Bridge vote verification
Final outcome: PASSED
Post-close verification found no evidence of double-counting / weight inflation.
Announcement: [DIS] CKB Integration for Rosen Bridge - #109 by zz_tovarishch
Logs: ckb-dao-watchdog/Verification Logs - Rosen Bridge Vote at main · kydchen/ckb-dao-watchdog · GitHub
—
For visibility, DAO transition updates are also mirrored on X at https://x.com/CkbDaoUpdates (process/status updates only), rather than on my personal account.
The plan is to hand the account over to the DAO v1.1 Stewards team after launch.
舟舟 tovarishch (2026-01-21T15:17:35, Nervos Nation, edited 2026-01-21T16:11:43)
DAO v1.1 Progress Report #5
Governance flow integration completed. Crisis voting shipped. UI fixes, dashboard stats, faster draft autosave, new tech overview doc.
治理流程集成。危机投票上线。
用户界面修复、仪表盘、更快的草稿保存、新的技术文档。
Talk: [DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #94 by zz_tovarishch
X: https://x.com/CkbDaoUpdates/status/2013978884270596265?s=20
ccfdao.dev | docs.ccfdao.org
舟舟 tovarishch (2026-01-23T10:17:14, Nervos Network)
Phroi (No DM) (2026-01-24T17:56:52, Nervos Network)
Replying to this message from Kevin Wang (slow to respond):
KevinW is not me
Hey @zz_tovarishch
On Metaforo we have a user named KevinW, this username was created on 30 October 2025 and (s)he voted vocally in the last two CommunityDAO proposals. Nothing wrong with that, except KevinW is NOT our estimeed Kevin Wang (see the message I’m replying to 
)
Now, if this user was discreet in voting, (s)he may have slipped under the radar unnoticed, but his/her actions are so flashy, that we can argue that (s)he is intentionally impersonating our esteemed Keving Wang:
-
On Rosen proposal (s)he voted
Nowith20 M CKBand (s)he was ostensibly the first user to vote -
On DAO v1.1 proposal (s)he voted
Yeswith20 M CKBand (s)he left a message:
The fact that we haven’t spent much money in three years is largely due to this terrible voting tool. Hopefully, it can be changed soon. so yes !
And indeed during the last vote, I talked with a lot of Community members, and all of them (except a single one) were convinced this user was our esteemed Kevin Wang and they were arguing on the why Kevin Wang voted against it.
So I was wondering:
-
What will be done to address this issue in the upcoming DAO v1.0 vote?
-
What will be done to address this kind of issues in the upcoming DAO v1.1?
Love & Peace, Phroi
舟舟 tovarishch (2026-01-24T18:55:39, Nervos Network, edited 2026-01-24T19:20:31)
Replying to this message from Phroi (No DM):
Hey @zz_tovarishch
On Metaforo we have a user named KevinW, this username was created on
30 October 2025and (s)he voted vocally in the last two CommunityDAO proposal…
Hi Phroi,
On DAO v1.0 and v1.1, there is no rule that restricts display names or requires identity verification. Voting weight and validity come from on-chain Nervos DAO deposits, not from a display name. A display name resembling a known community member does not trigger any DAO rule or change the voting outcome.
As transitional coordinator, I don’t have the mandate to arbitrate identity disputes. Similarly, under the v1.1, Stewards are expected to facilitate process and information flows and execute what is written and approved, not to verify identities or adjudicate impersonation disputes, unless an explicit rule is introduced and approved by the community. However, I’d strongly caution against attributing votes to specific individuals based on display names, as that quickly becomes speculation and undermines procedural integrity.
If the community believes we need an explicit policy (for example, constraints on confusing display names, or an opt-in identity / reputation layer), the correct path is to submit a meta-rule proposal that defines scope, authority, privacy expectations, and failure modes. Until such a rule exists, it should not be treated as part of DAO governance under v1.0 or v1.1.
Personally, I agree that in the long run, a better system would combine on-chain stake weight with an opt-in reputation / Web5 DID system, but that requires careful design and explicit community consensus.
Phroi (No DM) (2026-01-24T19:08:05, Nervos Network)
Replying to this message from 舟舟 tovarishch:
Hi Phroi,
On DAO v1.0 and [v1.1](https://talk.nervos.org/t/dis-community-fund-dao-v1-1-web5-community-fund-dao-v1-1-web5-optimization-proposal…
Just let me double check on this:
Is there any rule preventing CommunityDAO v1.1 from verifiably linking other platform profiles into CommunityDAO v1.1 profiles?
Think of Github, Nervos Talk, … No need for identity check for this, nor arbitration necessary
舟舟 tovarishch (2026-01-24T19:42:30, Nervos Network, edited 2026-01-24T19:53:18)
Replying to this message from Phroi (No DM):
Just let me double check on this:
Is there any rule preventing CommunityDAO v1.1 from verifiably linking other platform profiles into CommunityDAO v1.1 profiles?
…
Correct. There is no DAO v1.0 / v1.1 rule that restricts display names, and there is also no rule preventing the v1.1 platform from supporting opt-in profile linking to other platforms.
This is primarily a product / Web5 DID feature, not a governance rule. Per the v1.1 proposal scope, the initial deliverables prioritize DID login and Nervos DAO address binding. Cross-platform profile linking (e.g., Talk/X/TG…) aligns with the broader profile-center design direction, but whether it lands in the first mainnet-ready release depends on implementation readiness. (Screenshot attached for the UI direction, not a scope guarantee)
Phroi (No DM) (2026-01-24T20:02:52, Nervos Network)
Replying to this message from 舟舟 tovarishch:
Correct. There is no DAO v1.0 / v1.1 rule that restricts display names, and there is also no rule preventing the v1.1 platform from supporting opt-in profile linking to other platforms.
This is primarily a product /…
So long CommunityDAO v1.1 is open to PRs this feature will eventually land 
Phroi (No DM) (2026-01-24T20:05:47, Nervos Network)
BTW when you have time feel free to reply to: [DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #97 by phroi
舟舟 tovarishch (2026-01-26T09:28:15, Nervos Network, edited 2026-01-26T15:44:02)
Replying to this message from Phroi (No DM):
BTW when you have time feel free to reply to: [DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #97 by phroi
[DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #98 by david-fi5box David had given some replies, Yixiu might add later
Phroi (No DM) (2026-01-27T04:13:33, Nervos Network)
Replying to this message from 舟舟 tovarishch:
[DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal - #98 by david-fi5box David had given some replies, Yixiu might add later
Replied Those CommunityDAO v1.1 Voter Whitelists sound quite scary!
Phroi (No DM) (2026-01-27T04:16:58, Nervos Network)
Replying to this message from Matt:
Great catch @phroi
These are the docs: https://docs.ccfdao.org/en/docs/developer-docs/architecture/vote#casting-votes
haoyang li (2026-01-27T08:50:54, Nervos Network, edited 2026-01-27T14:12:12)
Replying to this message from Phroi (No DM):
Replied
Hey Phroi and @mattQuinn, thanks for the scrutiny! I’m haoyang, one of the DAO steward team member, yeah the name does sound scary 
, but I can assure you that this is just a naming issue, it works like this:
If you just staked your CKB, the DAO 1.1 platform needs a bit time to pull this information (currently set as once per day, UTC time); the “whitelist” is to speed up this process so testers (like me) can start testing without waiting. We just finished a meeting and agreed that the name is quite misleading, maybe “voter snapshot” would be better.
But rest assured, this does not mean only people in the whitelist can vote, everyone who staked CKB can, you can verify this once the platform is launched on testnet for community testing 
Phroi (No DM) (2026-01-27T16:36:25, Nervos Network)
Replying to this message from haoyang li:
Hey Phroi and @mattQuinn, thanks for the scrutiny! I’m haoyang, one of the DAO steward team member, yeah the name does sound scary
If you j…
Hey @haoyang94, nice to meet you and congratulations on the steward role Name change is welcomed. That said, I would try to explain more the:
Why do we even need a snapshot/whitelist of voters in the first place?
Issue: potential for long-term abuse and centralization is really high, so there must be an even better reason to introduce it in the first place (V1.0 indeed doesn’t have it)
Hypothetical Example:
- In 2 years Donald Trump is elected in the yearly election for Community DAO v1.1 Roles as Vote Administrator and the other roles are filled by his evil lackeys
- Now Trump is the one controlling both the Voter Snapshot tool and the on-chain cell representation.
- Trump decides to ban all voters except for voters he controls.
- Trump updates the on-chain representation of whitelist, cause he is the one who has the power to so and there is no rule saying that he cannot do that.
- Now Trump fully controls CommunityDAO v1.1 until the next Community DAO v1.1 election
- Trump wins all upcoming elections, cause they are gonna be based on Community DAO v1.1 votes he controls (right?)
…
Result: Trump owns Community DAO v1.1 treasury 
I’m sure that you have pretty good reason to introduce it, so please explain to the Community your reasoning and the rules that underpins its usage. Also, what happens if these rules are violated?
Love & Peace, Phroi
haoyang li (2026-01-28T08:56:01, Nervos Network, edited 2026-01-28T13:57:38)
Replying to this message from Phroi (No DM):
Hey @haoyang94, nice to meet you and congratulations on the steward role
Why do we even need a snapshot/whitelist of voters in the first place?
…
Hi Phroi, totally valid scenario, and I just asked the dev team, they said this feature is only there for testing purpose, and it will be removed after the mainnet launch.
Although one thing I think worth clarifying is that the current whitelist mechanism doesn’t ban anyone from voting, it’s not like only the whitelisted addresses can vote, anyone with staked CKB can, the whitelist only accelerate the speed for the current system to find the information about who has staked CKB, it doesn’t prevent any addresses from voting.
Phroi (No DM) (2026-01-28T18:46:31, Nervos Network, edited 2026-01-28T18:55:28)
Replying to this message from haoyang li:
Hi Phroi, totally valid scenario, and I just asked the dev team, they said this feature is only there for testing purpose, and it will be removed after the mainnet launch.
Although one thing I think worth clarifying i…
Hey @haoyang94 That’s very reassuring, thank you!! So glad to see this cleared up! Just to make sure that we are all on the same page, could your team update the Docs to reflect this change?
Feel free to update:
Documentation > Developer Docs > Architecture > Vote System:
- Vote Creation Workflow
- Casting Votes
- SMT Whitelist Tool
- Vote Data Models
Documentation > Developer Docs > Architecture > Technical Overview
Documentation > User Guide > Frequently Asked Questions:
- Voting Rights & Eligibility > Who can vote?
- Voting Rights & Eligibility > I just registered a Web5 DID. Why can’t I participate in the current vote?
Documentation > User Guide > Getting Started:
- Important Notes
May I additionally suggest that if something exists only for testing purpose and it will not be in production, clearly label it as non-production / testing-only in Docs. This way by reading the Docs all the Community can clearly understand how CommunityDAO v1.1 is gonna work.
Also please, remember to tag me on the progress made to clear up this misunderstanding, I’d like to keep an eye on this.
Love & Peace, Phroi
haoyang li (2026-01-29T12:02:46, Nervos Nation, edited 2026-01-29T12:31:06)
Hey community, this is our weekly DAO v1.1 progress update. In addition to the dev log, we are announcing two key items this week, aligned with the proposal timeline:
- DAO v1.1 will enter the official public community beta starting this week. The beta is expected to run for about one month, so we can collect feedback and converge before final delivery.
- The inaugural Steward Team roster is finalized and published in this post, so the community has clear coordination points during the beta.
You can find more details here:
Thanks for your continued attention!
haoyang li (2026-01-29T12:12:35, Nervos Nation)
DAO V1.1 Bi-weekly AMA
Share dev progress, beta planning, and answer community questions:
Fri, Jan 30 · 8:00–9:00 am (Asia/Singapore, UTC+8) / Jan 29 16:00–17:00 (PST)
Google Meet: https://meet.google.com/hxz-giiy-xji
haoyang li (2026-01-30T07:12:23, Nervos Nation, edited 2026-01-30T07:12:52)
Hey! Thanks for those who attended our DAO v1.1 Bi-Weekly AMA today, for those who can’t attend it we have also prepared the following resources so you can know what has been done, and the future plans.
**
To summarize**:
- We announced the steward team for the first year: Shawn (a.k.a NightLantern), Hongzhou (@zz_tovarishch), and Haoyang (@haoyang94)
- We the steward team is preparing a steward operation manual that will be published after the mainnet launch to detail the responsibilities of the steward team
- DAO v1.1 is about to publish to the community for testing
- For the Web5 part: the first batch of basic services are completed and would be deployed soon for everyone to experience; the Relayer has been completed for BBS, after the DAO mainnet launch, the team will bridge BBS and DAO.
Resources:
- Video Recording: https://drive.google.com/file/d/1MUtscXtPhYFDnQNjVqgslU0LHpiRp7W8/view?usp=sharing
- Transcript: Notion
舟舟 tovarishch (2026-02-09T11:36:34, Nervos Nation)
Forwarded from 舟舟 tovarishch.
Dear community, this week’s DAO V1.1 AMA will be
12 Feb · 10:00 – 11:00 am UTC+8 / 11 Feb · 18:00 – 19:00 pm PST
Google Meet joining info
Video call link: https://meet.google.com/vgu-iswk-eob
haoyang li (2026-02-12T08:12:19, Nervos Nation, edited 2026-02-12T10:14:10)
DAO 1.1 Mainnet Countdown — Live by End of February!
Thanks to everyone who joined the AMA today. Here‘s what you need to know 
—
Dev Update: Testing Wraps Up + Relayer Live
• Full voting flow tested (edge cases, UI/UX, exceptions)
• Relayer integrated: BBS ⇄ DAO accounts connected
• PW Lock voting weight now supported
• Final testing in progress
—
Confirmed Timeline: Mainnet Ready End of Feb
• Feb 14 – Quasi-production deployment (mainnet simulation)
• Mid‑Late Feb – Mainnet environment testing
• End of Feb – 
Public launch & proposals open
—
Steward Team: Docs & Assets on Track
• Four core docs drafted:
– Steward Operation Manual
– Community Guidance Doc
– Bug Report Template
– Milestone Tracking Doc (for community to inspect on proposal team’s progress)
• 
Onboarding video + 
Poster — due Feb 24
• All materials launch together with the platform