Demo preview — LOCAL AI COIN is not issued yet. Nothing here is for sale. Not financial advice.

LITEPAPER / CONCEPT EDITION

An independent
intelligence layer.

A working thesis for local AI, community coordination, and the choices we still need to make.

CONCEPT DOCUMENT · NOVEMBER 2026 · NOT ISSUED

01 / THE PROBLEM

Intelligence should not require giving up control.

Many AI workflows depend on a remote service. That can put availability, data handling, model access, and the shape of a workflow outside the user’s control. Cloud tools have useful roles, but they should be a choice.

Running models locally introduces a different set of constraints: hardware limits, setup effort, model selection, and maintenance. The opportunity is to make that choice more understandable and practical, without pretending those tradeoffs disappear.

02 / THE LOCAL AI THESIS

Ownership is a practical capability.

A local-first system gives its operator meaningful control over where inference happens, which model runs, and what leaves the device. Compatible models can operate offline once the required files and software are installed.

Local does not automatically mean secure, private, open, or unrestricted. Model licenses, application telemetry, dependencies, and device security all matter. Our proposed ecosystem should make these boundaries visible, with network sharing optional and off by default.

  • Private workflows should keep prompts and outputs on the chosen machine.
  • Resource use should be visible, limited, and easy to stop.
  • Models and applications should describe their licenses and hardware needs.

03 / NETWORK DESIGN

Independent machines, explicit coordination.

The proposed design has three parts: a local client, a discovery layer, and a contribution verification system. None is operational on this website. The dashboard and network map use only simulated data.

Local client

A future client would let an operator choose workloads, set memory and compute budgets, approve sharing, and stop participation. Isolation and a clear permission boundary would be prerequisites for any pilot.

Discovery and verification

A discovery layer could match suitable devices to permitted work. Verification would need to assess useful completion without exposing private inputs. Redundant checks, reproducible evaluations, and privacy-preserving approaches need research; no final method has been selected.

Model and application layer

Model metadata should include provenance, licensing, integrity checks, and documented evaluations. Applications should declare their network behavior and allow local-only use where feasible.

04 / INCENTIVES

Reward usefulness, with evidence.

LOCAL AI COIN is a proposed incentive and community mechanism, not a requirement for running local models. Candidate contributions include verified compute, licensed model publication, evaluations, and useful local-first software.

A workable system would need to resist duplicate identities, fabricated activity, low-quality submissions, and collusion. Raw device time is not the same as useful work. Quality review, usage evidence, and clear eligibility rules would need testing before any reward mechanism could be considered.

No reward amounts, issuance rules, or redemption mechanisms are defined. The distribution graphic on the coin page is a draft example, subject to change, not an offer.

05 / GOVERNANCE

Open input, accountable decisions.

The initial concept is to publish proposals, document decisions, and invite technical and community review. Any future governance model must define who can propose changes, how participation is represented, and which decisions require independent review.

Token ownership alone may not represent expertise or affected users. Safeguards against concentrated control, conflicts of interest, and rushed security changes remain open design questions. No governance rights exist today.

06 / RISKS AND LIMITATIONS

Clear limits are part of the design.

This project may change direction or never become an operational network. Prototype results, legal constraints, funding needs, and security findings could prevent progress.

  • Technical: consumer hardware varies; performance, verification, and reliable scheduling are unresolved.
  • Privacy and security: shared workloads can expose devices or data without strong isolation and review.
  • Model quality: outputs can be wrong, biased, unsafe, or unsuitable for a task. Users must evaluate them.
  • Economic: incentive mechanisms can be manipulated or fail to attract useful contributions.
  • Legal: token rules, licensing, and obligations differ by jurisdiction and require professional review.

Do not rely on this concept for critical operations or financial decisions.

A living concept, open to thoughtful feedback.

Tell us what is useful, what is missing, and what needs a harder look.

Send feedback
ON THE HORIZON

Coming soon.

This feature is planned. Join the waitlist by email to share your interest.

Join the waitlist

Opens your email app. No signup is stored on this site.