Membership
Clear membership rights, responsibilities and eligibility. Access that reflects a person's role in their community.
Belong with clarityA framework taking shape
Better systems.
Stronger
communities.
Infrastructure for people who want to organize, make decisions and build something together.
NeoState is developing a shared foundation for membership, governance and transparent resource management—starting with communities, built for the long term.
Built around people.
Designed for accountability.
Open by intention.
01 / Our mission
Make collective action
easier, safer and
more effective.
A community needs more than a group chat. It needs a clear way to belong, decide and take responsibility.
NeoState brings a systems engineering approach to those needs: understand the people, define the rules, test the system, and learn from what happens.
Our long-term vision connects digital coordination with sustainable physical communities. The immediate focus is practical governance infrastructure that can be examined, improved and eventually adopted independently.
NeoState is being developed primarily to support Black American communities in organizing, building institutions and developing shared economic resources. The open-source goal is to let other communities adopt and adapt the software independently, broadening its usefulness and helping sustain development while preserving that founding purpose.
Inspired by Network State ideas. Grounded in operating within existing U.S. law.
02 / What we are building toward
Structure for a
shared future.
Three connected capabilities.
One accountable community.
Planned product capabilities.
Decision-making
Proposals, participation and voting under agreed rules, with a record of how a decision was reached.
Decide with accountabilityShared resources
Defined spending authority and traceable financial records, with safeguards for community funds and member privacy.
Act with responsibility03 / The first planned workflow
From a shared idea
to a visible outcome.
A community improvement proposal is one example.
This sequence describes our intended pilot;
it is not a live application.
- 01
Establish membership
Confirm who can participate and under which rules.
- 02
Make a proposal
Define the purpose, requested resources and expected outcome.
- 03
Reach a decision
Eligible members vote using agreed thresholds and procedures.
- 04
Authorize the action
The treasury process checks the decision and required approvals.
- 05
Publish the receipt
Show what happened, while protecting private member information.
A vote and a payment are separate events. The rules connecting them are being specified before implementation.
04 / What guides us
Trust is a
design requirement.
Clarity, security, responsibility, accessibility and stability guide the work—from the first requirement to a future release.
Transparent by design
Decisions and financial outcomes should be understandable and verifiable. Transparency must coexist with member privacy.
Human authority. Defined boundaries.
AI may assist with research, drafting and review. Its permissions must be explicit; an AI suggestion is not spending authority.
Open-source as the destination
The goal is software that other communities can deploy independently at no cost for the code. Publication and licensing are still being prepared; operating costs depend on each deployment.
05 / Development status
A clear view of
what comes next.
In development
Building the foundation first.
Our next product milestone is a testnet pilot that connects membership, proposals, voting and authorized treasury actions.
The intended technology direction is Base, native USDC and Safe, with bounded AI assistance. These integrations are not yet implemented in the current baseline.
Independent security assessment, remediation and retesting are required before a real-funds release.
- 01Current focus
Define
Reconcile mission, requirements, governance authority and privacy.
- 02Planned
Demonstrate
Build and test one complete workflow using test funds.
- 03Required gate
Assess
Independent review, fixes and operational recovery checks.
- 04Future
Release
Controlled deployment, independent adoption and later mobile distribution.
This is an information site. Account registration, voting, payments and mobile apps are not available here. No launch date has been announced.
06 / The person behind the project
Meet the founder.
Jason V. Holmes
Founder & Creator · NeoState
Visit Jason’s portfolioA vision for communities that can organize, decide and build together.
Jason created NeoState to explore how clear rules, accountable governance and transparent resource management can support stronger communities.
His direction for the project brings a systems engineering approach to development: document the mission, define requirements, examine the architecture, test the implementation and learn from independent review.
The long-term goal is an open-source foundation that other communities can adopt independently, with digital coordination supporting sustainable physical communities within existing U.S. law.
07 / A few useful answers
Understand the direction.
Who is NeoState for?
Community organizers, civic networks, cooperatives and professional groups that need clearer membership, collective decisions and shared-resource accountability. Specific pilot users and requirements are still being defined.
Is NeoState creating a sovereign state?
NeoState draws inspiration from digital-first community coordination. Its framework emphasizes operating within existing U.S. law. This website does not establish sovereignty, diplomatic recognition or any special legal status.
Can I use NeoState or contribute today?
The product is in development. Public source publication, contribution instructions and pilot participation are being prepared. There is no public sign-up or contribution intake on this site yet.
Does using Base or Safe mean the project is endorsed?
No. They are part of the intended technology direction. NeoState does not claim endorsement, a partnership or funding from Coinbase, Base, Circle or Safe.