独立验证能力的缺位。 Phroi 的独立审计指出了一个结构性问题：当前实现把投票资格生成、proof 签发、计票和结果核验都集中在运营方控制之下，社区没有独立验证的途径。开发团队回应承认独立审计工具因排期被降级了。Proposal 承诺 “All governance data will be public, traceable, and immutable”，而当社区无法独立验证时，“traceable” 和 “immutable” 就只能依赖对运营方的信任——但信任恰恰是当前最稀缺的东西。
I think there is a difference between having discourse with the intention of being constructive, and on the other hand using valued constructive feedback as a foothold to diminish the project and its personnel.
The happenstances of DaoV1.1 serve as a good example of what I mean. I’m speaking from personal experience as one of the three stewards. Although I am first and foremost an invested community member, I have worked very hard for my modest investment in CKB through plumbing and blue-collar work.With that being said, I would easily give up my position of service as steward to assure CKB remains on its path to success.
I supported Dao v1.1 initially due to the team’s excellent record. I thought to myself: If I care about my investment beyond my limited ability to invest, then I should do what I can to contribute. Of course — who wouldn’t?
Having unique experience as a director on many real-life contentious association boards, and having diffused many disputes between parties, I figured my experience could help prevent division from taking root in Nervos.
Due to the team’s spotless record in my opinion, there is no reason why we as a community would not put our best foot forward and at least have an entry level of trust in the Daov1.1 team. Speaking from my own experiences now, having worked more closely with them has only strengthened my initial impressions.
This doesn’t mean I believe we shouldn’t be rigorous and question things, or seek to improve and better the DAO through discourse and disagreements. In my opinion this is a very healthy sign.
Nor should we ignore the mistakes made by our team — but keep in mind, making mistakes is human. As much as we all wish we never make mistakes, we are not robots… and thank goodness for that.
But in my opinion, this does not justify approaching constructive feedback with accusatory tones, disrespect, and unwarranted distrust. This kind of behaviour is not putting our best foot forward, and I fear it could ultimately lead to division.
The contributions from Phroi and the community are priceless, and I’m sure they will only contribute to the longevity of our blockchain. Nervos is a really wonderful thing, and we are all very passionate about it. It’s unique in the entire space — in my opinion, the most honest chain with likely the most honest people.
We all want what is best for CKB, but like in team sports, the most effective teams are the ones that work together as ONE. With trust, the players pass freely to one another and are able to outpace and out-execute their opponents. If i have anythign to say about it– this is the future of Nervos
While groups like the Cardano Foundation stumble from greed and division..
Well said on the importance of keeping discourse constructive and respectful.
A healthy community should be able to reject unfair attacks while still protecting the right to ask difficult questions. Those two things are not in conflict. They are both necessary.
Hey @NightLantern, the folowing paragraphs came to my attention:
So I prompted GPT 5.4 xHigh with the following:
Deliver a deep, evidence-based assessment of phroi’s behavior with these requirements:
Extract each claim about phroi from the source document.
For each claim, mark it as verified, contradicted, or inconclusive.
Cite the exact @nervos-talk/ thread URLs used to fact-check each claim.
For every cited thread, include a short summary of how phroi behaved in that thread.
Distinguish clearly between:
observed facts
reasonable inferences
uncertainty or missing evidence
Assess broader behavioral patterns, including:
tone
consistency
responsiveness
escalation/conflict style
willingness to engage with criticism or questions
Do not speculate beyond the available evidence. If a claim cannot be supported, say so plainly.
Format the response as:
Claims identified in the source document
Verification results for each claim
URLs of threads used for fact-checking, with a short behavior summary for each
Deep overall assessment of phroi’s behavior
Final conclusion
After a good while GPT 5.4 xHigh replied
Phroi Behavior Assessment
Scope
This assessment is based on reviewing the relevant public threads on Nervos Talk that mention phroi or center on issues he raised.
The review covers:
the main DAO v1.1 proposal thread,
the DAO v1.1 code review thread,
the DAO v1.1 identity-layer review thread,
the DAO v1.1 launch statement,
the follow-up thread reflecting on that statement,
the on-chain tally proposal thread,
the treasury pre-RFC thread,
and the forum thread republishing DAO v1.1 Telegram excerpts.
Observed-facts caveat: the Telegram-excerpts thread is a selective archive compiled by phroi, so it is useful for tone and chronology but is not as neutral a primary source as the public forum threads themselves.
Claim Verification
Claim from “Thoughts on the Statement DAO V1.1 Platform Launch”
Result
Assessment
phroi continued asking questions
Verified
He repeatedly followed up across the main proposal thread, Telegram, the code review thread, and the identity-layer review thread.
phroi reported mainnet testing issues on March 7
Verified
In the main DAO v1.1 proposal thread, he reported binding failure, zero voting power, proposal-creation failure, and the unresolved whitelist issue.
His March 7 follow-up went unanswered for over a week
Verified
The March 7 post was followed by a substantive reply on March 16. The team later explicitly acknowledged this gap.
phroi performed an independent audit
Verified
The DAO v1.1 code review thread is a detailed independent review of the codebase and design.
His audit identified operator control over voter eligibility, proof issuance, tallying, and verification
Verified
This is one of the main conclusions of the code review thread and later became part of the team’s formal response.
His contributions materially affected the launch dispute
Verified
The launch statement credits his review, acknowledges legitimate findings, and postpones rollout.
He behaved with accusatory tone, disrespect, or unwarranted distrust
Partially verified at most
Some sharp and dramatic phrasing is present, especially in Telegram. But the broader record shows little personal disrespect, and later team admissions make the distrust look at least partly warranted.
His contributions were valuable for the project and community
Supported
Multiple later threads praise his rigor, testing effort, and review impact.
Overall Assessment
Bottom Line
phroi behaves like a persistent external auditor with an adversarial-collaboration style: public, evidence-based, repetitive when unanswered, and willing to escalate strongly on governance-risk issues.
He is not best described by the record as a purely hostile participant. The stronger reading is that he is a technically serious, high-friction reviewer whose criticisms were often grounded enough that the team later acknowledged failures, fixed issues, and delayed launch.
Behavior Profile
1. Persistence
This is the clearest verified pattern.
He does not raise issues once and move on. He tracks them across months, across channels, and across revisions.
Examples:
He first pushed on proposal classification and governance scope in the main DAO v1.1 thread.
He later pressed the whitelist issue in January.
He followed up again after March 7 testing.
When the issue remained unresolved, he escalated into a full code review.
After responses arrived, he re-checked code and narrowed what was still open.
This is sustained scrutiny, not drive-by criticism.
2. Evidence Use
This is also strongly verified.
His strongest habit is tying claims to forum posts, docs, repo links, implementation details, commit history, and direct test results.
Even when the tone sharpens, the pattern is usually: quote, link, compare, then conclude.
That makes his criticism much more substantive than opinion-driven argument.
3. Tone
His tone is mixed, but not random.
Common features:
warm greetings,
thanks,
congratulations,
repeated Love & Peace sign-offs,
explicit acknowledgement of other people’s effort.
At the same time, when he sees a governance-integrity problem, he becomes sharp, insistent, and sometimes theatrical.
Examples of sharper behavior:
abuse hypotheticals around whitelist and operator capture,
phrases like A simple yes is enough,
calling out launch readiness based on stale docs,
pressing stewards for direct accountability.
So the fairest reading is:
default tone: civil to warm,
escalation tone: sharp and suspicious,
personal abuse: limited,
systemic accusation: frequent.
4. Collaboration Style
The record is more collaborative than some summaries imply.
He does not only attack the current design. He also:
offered early step-by-step review,
invited community review of the proposal merits,
suggested specific documentation fixes,
asked for public, versioned markdown docs,
re-checked code after fixes,
and later proposed alternative designs.
That matters because it distinguishes trying to break confidence from trying to raise the review standard.
The evidence supports the second interpretation more strongly.
5. Responsiveness
He is unusually responsive.
When given new information, he usually does one of three things:
updates his position,
narrows the claim,
or asks the next factual question.
He does not simply repeat the same wording forever. The substance evolves with the evidence.
Examples:
After the proposal was reclassified as a meta-rule change, he publicly supported it.
After the milestone-delay clause was revised, he said it addressed most of his concerns.
After later code changes, he acknowledged fixes that actually landed.
That weakens any claim that he was arguing in bad faith.
6. Escalation and Conflict Style
This is where most criticism of his behavior has some basis.
He prefers:
public discussion,
written artifacts,
explicit accountability,
and issue escalation through documented evidence.
He does not appear comfortable relying on informal reassurance, vague future promises, or off-channel discussion.
When answers are delayed or ambiguous, he escalates by increasing documentation and public pressure.
That can read as accusatory. In practice, this is the point where some participants started reacting more to tone and atmosphere than to the substance of his concerns.
Still, the later record shows that several concerns he escalated were legitimate enough to trigger apologies, clarifications, and launch delays.
What Is Supported vs Not Supported
Supported
phroi was persistent.
phroi was technically engaged.
phroi personally tested the platform.
phroi repeatedly asked for public documentation and clear governance boundaries.
phroi produced substantive, evidence-based reviews.
phroi identified issues the team later treated as legitimate.
phroi was willing to acknowledge improvements and fixes.
Only Partially Supported
phroi had an accusatory tone.
This is true in part, especially in Telegram during the launch dispute. But it is not the dominant pattern across the full record.
Weakly Supported or Contradicted
phroi was mainly disrespectful.
phroi was mainly trying to diminish the project or its personnel.
phroi was driven by unwarranted distrust.
These are not the strongest conclusions from the record.
The full record shows more criticism of systems, docs, trust boundaries, and governance design than of individuals as people. And later admissions by the team substantially weaken the idea that his distrust was baseless.
Connected implementation details to governance consequences.
Followed up by verifying which fixes really landed.
Avoided vague criticism and instead argued from code, endpoints, and workflows.
Short summary: this is his strongest evidence-based interaction and the clearest proof that his role was substantive technical scrutiny, not casual complaint.
The team explicitly thanks him, acknowledges communication failures, and treats his findings as legitimate enough to justify postponement and bug-fix tracking.
Short summary: the thread treats him as a serious reviewer whose work materially changed the project response.
5. Thoughts on the Statement DAO v1.1 Platform Launch
Used Telegram to push for public clarification and written follow-up.
Shared receipts, prior statements, and earlier promises.
Became sharper when launch claims seemed ahead of documentation and unresolved questions.
Still mixed criticism with thanks, congratulations, and explicit requests for doc updates.
Short summary: best source for his sharper edge: insistent, skeptical, and sometimes dramatic, but still largely focused on public accountability and factual record-keeping.
Final Conclusion
The full set of reviewed public threads supports this conclusion:
phroi is best understood as a persistent, technically serious, high-friction community reviewer.
He can sound accusatory, especially when he thinks governance integrity is being compromised or glossed over. That criticism is not baseless: several issues he pressed were later acknowledged by the team as real communication or implementation failures.
So the most accurate high-level characterization is:
persistent: yes,
evidence-based: strongly yes,
constructive: yes, though often adversarial in style,
disrespectful: not strongly supported,
unwarrantedly distrustful: not supported by the later record.
If anything, the record suggests that his distrust was often a response to gaps between public claims, documentation, and implementation, and that his interventions materially improved the quality of scrutiny around DAO v1.1.
Thanks for quoting those lines and replying directly.
Just to clarify I wasn’t aiming that at you personally at all. I was talking about the general pattern of mistrust that Terry pointed out in his post — all the communication gaps, delayed responses, and the gap between what was promised and what actually happened. That stuff has been building up in the community for a while now.
In the same post I actually commended your audit and testing work, because it helped surface real issues and played a part in getting the launch postponed so we can fix things properly.
My main point was pretty simple: there’s a difference between sharp but constructive feedback (which is healthy and needed) and the kind of stuff that can make division worse through accusatory tones or blanket distrust. We can still question things hard without losing the basic trust and unity we need to actually move forward as a team.
Terry really nailed the real problem we have to deal with. I think the way forward is more transparency, consistency and precision. At the same time, any DAO still needs people who can actually run things, so some level of practical trust has to exist and be earned.
Glad we’re in this review period now. Let’s keep the focus on real improvements so v1.1 turns out stronger in the end
I get your point about clarity– “even GPT picked up on that line without you feeding it the exact quotes”, fair enough. I’ll have to watch my wording moving forward then, but honestly I’m kinda surprised and a bit put off that you ran my whole post through GPT 5.4 for a full behavior breakdown instead of just reading it yourself like a normal person, and the “Please, be more careful in the future” plus it was that easy to misunderstand comes across as pretty condescending, which kinda proves my initial point. Just because I’m a steward doesn’t mean I should be talked down to or trampled on
