How aiOut, keepAIon, Δ9, and 4DNFT form a unified system for human consent, identity, and ownership in a world of ambient AI.
You should never be subjected to an AI system without your explicit permission. The Consent Stack is a technical and social framework built on that single premise.
This document describes the architecture, tokenomics, and governance of a consent-first AI ecosystem — one where human identity remains private, creative ownership is tracked on-chain, and participation in AI systems is always opt-in.
The stack consists of four interlocking layers: the aiOut rights movement and pledge registry, keepAIon as the builder platform and AMOK zero-knowledge proof system, Δ9 as the Solana SPL utility token powering credential maintenance and governance, and 4DNFT as a time-aware NFT standard tracking provenance across the fourth dimension — time.
AI systems are deployed silently, at scale, against people who never agreed to participate. Training datasets scrape creative work without attribution. Inference systems make decisions about individuals without disclosure. The legal and technical infrastructure for meaningful consent does not yet exist.
Existing opt-out mechanisms are fragmented, unenforceable, and designed to minimize compliance friction for deployers rather than protect the rights of individuals. A robots.txt file is not consent. A terms-of-service checkbox is not consent. Consent requires explicit, informed, revocable agreement — and a public record that it was given.
"Your consent. Your right. No exceptions." — aiOut pledge
The Consent Stack is the infrastructure layer that makes real consent technically possible and legally meaningful.
No AI system may process a person's identity, creative work, or data without affirmative opt-in. Silence is not consent.
Consent can be given and verified without revealing who gave it. Zero-knowledge proofs decouple identity from participation.
Creative ownership is tracked as it happens — every play, every share, every transfer — not as a snapshot but as a living record.
Any consent given can be withdrawn. Credentials expire without active maintenance. Participation is never permanent by default.
The Consent Stack operates across two blockchains — Solana for high-throughput token operations and Base (Ethereum L2) for smart contract verification and NFT standards. The layers are designed to be independently functional but mutually reinforcing.
A public pledge registry where individuals signal their consent position. Each entry is a timestamped, verifiable record of a person's stance on AI use of their identity and creative work. The registry is append-only and publicly auditable.
The builder platform and zero-knowledge proof system. AMOK generates a ZKP circuit that allows a person to prove they hold a valid consent credential without revealing their identity. The nullifier prevents double-signaling; the commitment is stored on-chain.
The Solana SPL utility token that powers credential maintenance, governance voting, and feature access. Staking Δ9 keeps a wallet's AMOK credential active. Unstaking below threshold causes credential expiry — participation is always active, never passive.
An ERC-1155 NFT standard on Base that adds temporal provenance — every play, share, and transfer is recorded as an on-chain event. The fourth dimension is time: ownership is not a snapshot but a journey.
AMOK (Anonymous Machine-readable OK) is a ZKP circuit built on the keepAIon-pledge-v1 specification. It allows any wallet holder to generate a proof of consent participation without revealing their GitHub identity or wallet address to third parties.
The AMOK passphrase is never stored or transmitted. The circuit generates three outputs: a nullifier (prevents reuse), a commitment (stored on-chain), and a token (presented for verification). Identity remains concealed throughout.
AMOK credentials expire when Δ9 stake drops below the Signal tier threshold (100 Δ9). Re-staking renews the credential immediately.
AMOK answers one question: is this a real, unique, pledged participant? Everything else in the Consent Stack is just a different action attached to that same answer.
Three use cases share the identical underlying proof:
AMOK proves a person signed the pledge — added to the public, append-only record — without revealing who they are.
AMOK proves a vote came from a real pledged holder, weighted by Δ9 stake, contributing to the aggregate civic signal described in the next section.
AMOK proves a code contribution came from a real pledged builder — the same identity primitive extended to recognize and reward the people building the stack itself.
This last use case — contribution proof — is the least developed and will evolve as keepAIon grows. The early concept: a contributor signs work with an AMOK-linked credential, a merged pull request triggers verification, and a small Δ9 reward flows to their staking wallet. "Building by builders" becomes economically literal, not just a slogan — while keeping the same anonymity guarantees as every other AMOK action. The mechanism for Sybil-resistance and quality review on this path is still being designed.
Δ9 is a Solana SPL token that serves as the economic backbone of the Consent Stack. It is not a speculative asset — it is a utility instrument. Holding Δ9 is how participation in the consent ecosystem is maintained and measured.
A single voice can be ignored. Ten thousand cryptographically-verified voices, none of which can be individually identified or punished, cannot be dismissed as easily.
That is the actual function of Δ9 governance. Every staked token contributes weight to a position. Every vote is backed by an AMOK zero-knowledge proof — confirming the voter holds a real, unique, pledged credential, without revealing who that person is. The result is a number: how many verified stakeholders, weighted by stake, support a given position on AI consent policy.
One employee's dissent can cost them their job. Ten thousand anonymous, provable dissents become a dataset — one that advocacy groups, journalists, and policymakers can cite directly.
This is not a claim that Δ9 plugs directly into EU rulemaking, national legislatures, or corporate policy. There is no official channel that ingests on-chain votes. What Δ9 produces is something regulators and advocacy organizations currently lack: a timestamped, tamper-evident, Sybil-resistant record of where a real population of stakeholders stands — usable as evidence in public comment periods, submissions to the EU AI Office, shareholder proposals, or press coverage. The proof is the product. What anyone does with that proof is up to them.
Staking Δ9 unlocks progressively deeper access to the consent stack. Tiers are evaluated continuously — stake more to upgrade, drop below threshold to downgrade.
Entry level. Credential stays active. Standard rewards. Public pledge badge. Counted in the aggregate signal.
Vote on pledge versions and keepAIon parameters. 1.25× reward boost. 1.25× signal weight.
Full governance weight. Vote on legal strategy and royalty parameters. 2× rewards. 2× signal weight.
Maximum governance power. Automatic ERC-2981 royalty routing. 3× rewards. 3× signal weight.
Traditional NFTs capture a moment — who owns what, right now. 4DNFT captures the journey. Every stream mints a provenance event. Every share is recorded. Attribution follows the work everywhere it goes, forever.
4DNFT is built on ERC-1155 on Base with ERC-2981 royalty routing. The consent framework is built in — listeners opt in, artists control their catalogue, and Δ9 stakers receive automatic royalty splits on every secondary sale.
The Consent Stack is not a product. It is infrastructure for a rights movement.
The tools exist to build a world where AI participation is always chosen, never assumed. Where creative provenance is immutable. Where identity can be verified without being exposed. The Consent Stack assembles those tools into a coherent, working system.
We thought this through.
building by builders · keepAIon.com · your consent. your right.