A community-directed product studio
Ideas become realistic choices. The community decides. A public build specification turns the winner into work—and every milestone, expense, test, and result leaves evidence.
Official token status: `$WBWW` is the project ticker. No official mint has been published. Verify any future contract address through this website only.
The mechanism is the product
Ideas are welcome. Binding choices are scoped first. A winning vote becomes a build mandate with owners, budget limits, acceptance tests, and a public postmortem.
Swipe to inspect all nine stages →
Ideas → Screen → Vote → Specify → Build → Test → Ship → Prove → Repeat
Current round
The first full build cycle: shortlist practical ideas, publish the final scopes, let the community choose, then ship the winner in public.
Candidate shortlisting is underway. The final ballot will contain three practical, fully scoped choices with owners, budget ceilings, delivery targets, and acceptance tests.
These candidate areas are being converted into comparable Build Specifications. Only options that pass feasibility, security, budget, and maintenance review reach the ballot.
A scam-resistant source of truth for every verified project link.
A transparent board for milestones, evidence, costs, and blockers.
A structured intake flow that turns ideas into realistic build briefs.
Current build
When the Round 01 ballot closes, the winning Build Specification moves here with its owners, milestones, budget, acceptance tests, and evidence.
Proof of Build
The Proof of Build archive will document each mandate, release, cost, acceptance result, known issue, and postmortem.
First verified release pending Round 01 selection
ROUND 01“Shipped” means a tagged release, deployed or downloadable artifact, passing acceptance evidence, budget report, known-issues list, and named support or rollback owner.
How decisions become work
The community chooses from safe, feasible choices. Maintainers cannot hide behind “the vote,” and voters cannot waive security, law, budget limits, or the ability to finish.
Anyone can describe a problem. Discussion happens publicly, and duplicates or missing details are handled with reasons.
Safety, legality, cost, time, dependencies, maintenance, and measurable output are reviewed before the ballot.
Final choices, eligibility, timing, budget ceilings, and acceptance criteria cannot change once voting starts.
The winner receives an ID such as WBWW-RFC-0001, a Build Spec, owners, milestones, and public evidence.
Trust architecture
The website will list official accounts, proposals, ballot links, results, treasury labels, releases, and corrections. Social posts point back here.
Durable proposals, Build Specifications, issues, tests, releases, and evidence.
Proposal workshops, contributor coordination, testing, and public support.
Fast updates and discovery—never the binding vote record or sole contract source.
No official mint has been published and no token sale is active. Admins never DM first. Never share a seed phrase or private key, and never “search `$WBWW`” to find a contract.
What this is—and is not
Questions, without the crypto fog
WBWW is a community-directed product studio. The community chooses among feasible ideas; the build team ships the winner in public and publishes the evidence.
Voting opens after scope review. The final ballot, eligibility rules, opening and closing times, budget ceilings, and acceptance tests will be published together on this website.
No official mint has been published. Any address shared elsewhere is unverified until it appears in the official manifest on this website.
No. Round 01 participation does not require token ownership. Any future token role must support the build process rather than replace the product.
Treasury operations will use segmented Squads multisigs, multiple independent signers, public transaction labels, and review delays—not one founder wallet.