My role
I am NeoState’s founder and creator. I set the mission and requirements, review architecture and risks, and guide AI-assisted research and implementation through documented decisions and verification.
Mission
The goal is practical infrastructure for communities to organize, make decisions and manage shared resources responsibly. The long-term vision connects digital coordination with sustainable physical communities and software that other communities can deploy independently.
NeoState draws inspiration from Network State ideas while emphasizing operation within existing U.S. law. It does not claim sovereignty or special legal status.
What exists today
As of 11 November 2026, a replacement information-site preview runs on Cloudflare Workers Static Assets. It presents the mission, development status and planned workflow, using the official NeoState logo and brand palette.
The project uses GitHub for source and change history and shared Drive documentation for engineering context. Automated checks cover responsive layouts, keyboard navigation, links, brand contrast pairs, privacy and missing-page behavior. Deployed HTTPS responses and security headers were also checked.
This is an information-site milestone. Registration, member voting, treasury payments and mobile applications are not available. The repositories remain private while publication and licensing are prepared.
Planned architecture
The intended direction uses Base, native USDC and Safe, with bounded AI assistance for research, drafting and review. These integrations are not yet implemented in the current baseline. An AI recommendation does not grant spending authority.
The authority connecting a community vote to treasury approval, signer recovery, privacy boundaries and operational controls must be specified and verified before a real-funds release. No endorsement, partnership or funding from Coinbase, Base, Circle or Safe is claimed.
Next milestones
- Complete information-site review and controlled hosting migration.
- Baseline mission, requirements, governance authority and privacy decisions.
- Demonstrate membership, proposals, voting and authorized treasury actions using test funds.
- Obtain independent security testing, remediate findings and retest before handling real funds.
- Prepare open-source licensing, independent deployment guidance and later mobile distribution.
This brief will evolve with verified implementation evidence; no product launch date has been announced.