Jason Von Holmes

Community systems / founder-led project

Back to all projects

NeoState

Systems engineering for communities that need clear membership, accountable decisions and transparent shared resources.

NeoState official logo
Existing official project identity. Information-site milestone; product services remain planned.
Explore the information site ↗

Current milestone → proposed capabilities

Make the authority path explicit.

  1. Information siteAvailable: mission, status and synthetic concepts
  2. Membership + proposalsPlanned: identity, eligibility and accountable decisions
  3. Authorized executionPlanned: signer authority, recovery and reviewed treasury controls

Illustrative development sequence. Connecting the boxes does not establish implemented services, voting authority or payment capability.

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

Checked 17 November 2026: the information site is available at neostate.io, which declares itself canonical. The workers.dev address declares the same canonical URL. It presents the mission, development status and planned workflow, using the official NeoState logo and brand palette. It also links synthetic interactive and Community Hub concepts; these do not establish working accounts, real voting, payments or messaging services.

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

  1. Keep the information site and synthetic prototypes aligned with verified development status.
  2. Baseline mission, requirements, governance authority and privacy decisions.
  3. Demonstrate membership, proposals, voting and authorized treasury actions using test funds.
  4. Obtain independent security testing, remediate findings and retest before handling real funds.
  5. 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.