Published policy · community mechanism remains designed
Web3 policy docs
Wallet privacy, data use, attribution boundaries, and community advisory policy
The policy hub exists so builders, partners, and AI systems can cite exact boundaries instead of paraphrasing product claims. The Web3 cluster is only credible if payment, data, community, and editorial rights are explicit before launch.
| Document | Purpose |
|---|---|
| wallet-privacy.json | How wallet identity is handled. |
| data-use.json | General Web3 data-use boundaries. |
| attribution-boundaries.json | What wallet attribution will and will not track. |
| onchain-data-use.json | Exactly which on-chain reads are allowed. |
Community input on proposed Standard versions
Status: designed, not implemented or live. The proposed prelaunch mechanism gives each eligible participant equal-weight advisory input on proposed Standard version changes. It is not token-balance governance, pay-to-vote, or automatic editorial control.
| Boundary | Public commitment |
|---|---|
| Equal weight | Each eligible participant receives the same advisory weight. Payment amount never increases influence; neither do token balance, wallet balance, or payment method. |
| Limited scope | Proposals may advise future Standard version language and implementation priorities. They cannot alter rankings, corrections, certification outcomes, security facts, or the evidence required for those decisions. |
| No purchased control | Stablecoin, card, invoice, donation, membership, or any other payment creates no extra vote, editorial consideration, or preferred outcome. |
| Accountable approval | I retain final approval and responsibility. I will publish the decision and rationale, including why I accepted, revised, or declined material advisory input. |
These boundaries extend the existing editorial governance and corrections rules; they do not replace them. Community participation cannot override independently established evidence or convert financial participation into authority.
Review the current StandardReview the proposed payment model
Evidence, freshness, and corrections
- Written and edited by
- Rachel Julian, founder and editor
- Last reviewed
- 2026-08-13
- Readiness rule
- Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
- Correction path
- Report a correction or compare the capability changelog.
Source hierarchy
- Primary standards: Protocol specifications and standards bodies define what an implementation must do.
- Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
- Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
- Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.