Developers & researchers
Inspect public source, reproduce LOCALNET and challenge the evidence.
AVAILABLE NOWEXPERIMENTAL / LOCALNET
THE AWAKENING — DISTRIBUTED POTENTIAL
Q1 is an experimental blockchain project exploring verifiable coordination and settlement for resources and services.
02 / THE PROBLEM
Capacity is only the beginning.
Storage, compute and services exist across many independent machines. Bringing them together raises harder questions than simply connecting them.
What was committed? Can delivery be checked? What should happen when a commitment fails?
Q1 explores how verifiable commitments and settlement could help answer those questions.
What is available?
What can be checked?
What can we build together?
03 / THE Q1 APPROACH
CONCEPTUAL ARCHITECTUREA direction for research. Each step needs its own evidence.
Storage, CPU, GPU and infrastructure offered by independent providers.
LONG-TERM VISIONExplicit service obligations, with proposed Service Bond / escrow mechanisms.
LONG-TERM VISIONChallenge-based resource access, studied under bounded experimental controls.
IN RESEARCHSigned ledger transfers in a local test environment.
EXPERIMENTAL LOCALNETResource and service settlement: future vision, not deployed.
04 / PARTICIPATION
Different skills. A shared frontier.
New to Q1? Today, you can run a small ledger experiment on your own computer and check whether its nodes agree. Coordinating real storage, compute and services is the longer-term goal.
Inspect public source, reproduce LOCALNET and challenge the evidence.
AVAILABLE NOWRun the local experiment on your own computer. Public network participation is not open.
LOCALNET ONLYExplore future storage and compute participation using resources you already own. No onboarding or compensation is available.
LONG-TERM VISIONConsider future services and autonomous-agent coordination. These are proposed directions, not operational products.
LONG-TERM VISION05 / TECHNOLOGY & STATUS
EVIDENCE BEFORE CLAIMSQ1 LOCALNET v0 is a frozen experimental release for local reproduction. Public source does not mean a public network.
Inspect v0.1.0-localnet.1THE CONVERGENCE — RULES BEFORE TRUST
Connection is not proof of fulfillment. The local ledger tests signed transfers and fixed voting rules; it does not verify delivery of external services.
One computer. Loopback only. Fixed participants.
Signed transfers, durable commits and voter catch-up.
Project status reviewed . Source documents describe their own dated evidence.
Resource-access trials do not prove physical HDD ownership, continuous availability or permissionless resource uniqueness. Earlier resource experiments exposed regeneration and identity-splitting weaknesses.
Published research after the frozen LOCALNET release studies resource access and bounded failover with fixed participants. These experiments do not establish permissionless resource uniqueness, independent native multi-host acceptance or a public Testnet. The frozen release and later research have distinct scopes.
No Mainnet readiness, public mining, token sale, public economic distribution or guaranteed rewards are claimed. LOCALNET does not secure real-world value. Never expose its node ports to the Internet.
06 / ROADMAP
Progress through evidence. No promised dates.
THE EMERGENCE — SHARED POSSIBILITIES
CONCEPTUAL VISION — NOT YET DEPLOYED
Imagine people and machines coordinating storage, compute and services through checkable commitments. Resource markets, Service Bond, escrow and AI orchestration remain future directions.
Inspect the frozen release and independently check its documented behavior.
Study resource evidence, recovery and independent-host operation. External validation remains LEVEL 0.
Resolve and verify admission, fault assumptions, transport, partitions and recovery before opening participation.
Research resource markets and service commitments. Any future Mainnet requires finalized economics, production custody, governance and independent security review.
07 / BUILD WITH US
The next meaningful contribution could be a result someone else can reproduce. Start with the code, test the local release and share what you find.
Review source, scope and known limitations.
Read the source & status ↗Follow the guide’s pinned revision and prerequisites on your own computer.
Reproduce LOCALNET ↗Success, failure and unclear instructions all help. Redact personal data and logs.
Report non-sensitive findings ↗Security-sensitive findings: follow SECURITY.md. Use an existing private maintainer channel if available; otherwise retain details locally until an official private intake is announced. Do not post exploit details or keys in public Issues.
Technical participation today. No allocation, admission or rewards promised.