In formation — founding pledges open · no money accepted

Open roles, different responsibilities, no exclusive franchises.

“Seat” is shorthand, not a claim that a relay, a regulated bank, a charity application, and a legal board have identical authority or exit. Each role earns only under an explicit choice by the person, group, buyer, or legal authority entitled to choose it.

Register interest to take a seat — lead@onym.app You don't need our permission. You might want our help.

THE SEAT MAP

Four layers, seventeen open roles.

The person in the middle. Distance is intimacy: protocol components touch the daily route; market services attribute trust; applications serve particular domains; legal institutions remain governed by law. The Foundation sits outside the route, funding common infrastructure. Registering interest is a hello, not a contract.

Protocol kernel

Identity, interface, message, blob, and notary boundaries. Replacement requires wire compatibility and, for shared state, governed migration.

Service market

Recovery and its custody profiles, device backup, Discovery, audit, and arbitration. Signatures attribute claims; they do not manufacture competence or truth, and holding a copy of something is never the same as holding the person.

Application profiles

Charity, banking, distribution, and acquisition. Portability does not override regulation, custody, or domain liability.

Organizational governance

Sponsorship and recruitment. Signed records support accountability but do not replace legal appointment, labor law, or fiduciary duty.

SPONSORS — funds → ONYM FOUNDATION

grants · audits · conformance · standards

Outer band — institutions that keep everyone honest

Audit & attestation

draft spec

Examines components and signs what it found — opinions that expire and can be withdrawn.

Earns: engagement fees, never contingent on the verdict · Fits: security firms, conformance labs, academic groups

Read the contract →

Register interest →

Arbitration

draft spec

Decides disputes inside funded orders, with power capped at the escrowed stake.

Earns: per-dispute fees, outcome-independent · Fits: ADR institutions, law-adjacent firms, industry bodies

Read the contract →

Register interest →

Discovery

draft spec

Helps users find compatible instances for every seat through signed, replaceable catalogs — never a gate on direct use.

Earns: catalog subscriptions and curation services; paid placement stays labeled · Fits: consumer orgs, auditors, enterprises, communities

Read the contract →

Register interest →

Moderation authority

live on iOS · Android draft

Decides abuse reports users consented to at onboarding — notice, response window, reasoned verdicts, declared durations, appeal. Interfaces execute; the authority never touches keys, and sees only the single messages a recipient chose to disclose — never a mailbox, never anything undisclosed.

Earns: interface fees per report adjudicated — never per ban or per case opened — and foundation grants · Fits: trust-and-safety firms, hotlines, civil-society organizations

An authority that accepts reported photographs as evidence must say so in its manifest, publish the periods after which it deletes them, and — for any class it reports to the state — publish the preservation and referral terms too, or refuse media for that class. The Apple path runs in production today — an authority opening cases, serving notice, and signing verdicts, and the DeviceCheck backend that executes them — both from the Rust reference implementation and both currently operated by Onym as the replaceable default. The contract means those halves to sit with different operators, so one operator holding both is a concentration to replace, not a feature. The Android device-recall path is draft and undeployed, and nothing here is audited. This seat costs every user deniability — see what this seat costs everyone. Read the contract → · Reference implementation →

Register interest →

Middle band — services chosen per need

Naming & credentials

spec in review

Issues human-readable names and credentials as revocable claims — the name is never the identity.

Earns: issuance, renewal, dispute-handling, premium resolution · Fits: professional bodies, municipalities, communities, companies

Read the proposal →

Register interest →

Banking & payments

spec in review

Accounts and payments against keys only the user holds; custody always labeled.

Earns: account services, payment fees, premium tiers · Fits: licensed EMIs, anchors, credit unions, fintechs

Read the proposal →

Register interest →

Charitable coordination

draft spec · one profile merged, no code

Campaigns, donations, and private aid claims — a beneficiary proves eligibility without publishing identity, and the contract surface carries zero intentional donor or beneficiary PII in any public record.

Three ledger bindings are planned and none of them runs: BNB/EVM is a merged specification, Stellar/Soroban and Cardano are documented plans whose profiles are unwritten. No binding waits on another.

Earns: service fees to organizations; the cause's books stay public · Fits: NGOs, community foundations, civic tech

Read the contract → · BNB/EVM profile → · The bindings and their open questions →

Register interest →

Distribution

draft spec

Brings measurable aggregate attention — never person-level tracking.

Earns: per-campaign fees for verified aggregate delivery · Fits: media channels, communities, creators

Read the contract →

Register interest →

Acquisition

draft spec

Converts interest into store installs, measured only in aggregates.

Earns: per-order fees on aggregate outcomes · Fits: growth agencies, publishers

Read the contract →

Register interest →

Recruitment

draft spec

Finds participants for every seat, with candidate consent and no candidate ownership.

Earns: finite milestone fees per accepted order · Fits: recruiters, talent networks, guilds

Read the contract →

Register interest →

Recovery trustee

draft spec

Holds only the authority the identity holder enrolled — helps satisfy a recovery policy without becoming the identity.

Earns: the fees its published recovery offers declare · Fits: custody services, hardware vendors, organizations, trusted people

Seed custody lives here, in this seat's profiles, not in a seat of its own: the published Shamir profile splits a threshold of enrolled trustees and holds no usable material at any single one, while the cloud profile is a declared 1-of-1 custodian whose operator can technically recover the artifact it stores. A person choosing one holder is choosing the second, and is owed that sentence before enrolment — see what durable copies cost everyone. Read the contract → · threshold profile · custodial profile

Register interest →

Device backup

draft spec · one profile merged, no code

Keeps a sealed copy of one person's messages and attachments so a lost device is not a lost history — and pins, before the first byte, how long it keeps them, when it erases them, whose law applies, and how it hands them back.

Earns: storage plans and prepaid quotas priced by bytes and retention — never by reading, indexing, or analyzing what it holds · Fits: hosting providers, co-ops, backup specialists, self-hosters

The contract holds no key and offers no reset path: a restore proves possession of the person's own key, so a lost key means an unreadable archive and no operator recourse. An Object-HTTP profile is merged specifying digest, sealing, and proof-of-possession suites, but no conforming adapter, operator, or fixture exists in any Onym repository, so no operator can yet be measured against it. A backup also outlives the retention limits other people rely on — see what durable copies cost everyone. Read the contract → · Object-HTTP profile → · The boundary and its implementation →

Register interest →

Core ring — the user's daily route

Interface

draft spec

The window people use; presents choices honestly, holds no accounts.

Earns: app pricing, disclosed marketplace commission · Fits: product studios, accessibility specialists, enterprise vendors

Read the contract →

Register interest →

Message carriage

reference operator exists

Moves sealed messages it cannot read.

Earns: subscriptions or usage quotas for delivery and retention · Fits: hosting providers, ISPs, co-ops, self-hosters

Read the contract →

Register interest →

Media storage

reference operator exists

Stores sealed attachments it cannot open.

Earns: storage/egress plans, prepaid quotas · Fits: storage providers, CDNs

Read the contract →

Register interest →

Group verification

reference operator exists

Confirms group decisions follow the group's chosen rules, without seeing the member list.

Earns: per-operation or capacity-tier fees · Fits: infrastructure operators, institutions needing verifiable process

Read the contract →

Register interest →

PERSON

Identity stays here — sealed.

"Not a seat. Not for sale."

Sponsorship

pledges open · no payment

The one seat that gives rather than earns. Funds the Foundation's commons work; bounded recognition and a capped governance path are the consideration. The contract →

Become a founding sponsor →

Foundation support may include grant consideration, audit funding, conformance support, or introductions. Each has separate eligibility, conflicts, evidence, and legal terms; support is not protocol permission or a universal offer. Competitors are welcome where a reference operator already exists.

The Onym Foundation takes no commission, runs no user-facing seat for profit, and can be routed around by design.

Status tags are factual: "draft spec" means a public contract document exists and is marked draft; "in review" means the proposal is not yet merged; "live on iOS · Android draft" means one platform's profile is finalized, implemented, and running in production while its sibling profile is still a draft nobody has deployed; "one profile merged, no code" means an implementation profile pins the contract to a concrete stack, but no conforming adapter, operator, or fixture exists in any Onym repository, so no operator can yet be measured against it; "reference operator exists" means one replaceable default deployment runs today. Nothing here is audited yet.

CONSEQUENCE

What the moderation seat costs everyone

A seat that only some users choose, paid for by all of them.

The evidence rule

An authority decides a report by verifying the accused's own signature over the disclosed content. That forces the property in both directions: if a recipient could manufacture the signature, anyone could be framed for words they never wrote; if nobody could produce it, no report could be checked and abuse would be unanswerable.

What it costs

Every message an interface sends must therefore carry a transferable proof of authorship — one the recipient can hand to somebody who was never in the conversation. Deniability goes, for every user, whether or not they ever consent to an authority and whether or not anyone is ever reported.

Why it is written here

This is a governance fact, not an implementation detail. Adopting a moderation seat changes a property of the messenger itself, so the cost belongs in the public record beside the seat that imposes it rather than in a client's release notes.

The bound is narrow and worth stating exactly: an identity is a public key, not a name, and the proof says only that the holder of that key wrote those words. It becomes a proof about a person when the key is linked to one by information that lives outside the protocol. The signature also sits inside the encryption — it changes who can prove authorship of a message they already hold, never who can read one. Interfaces disclose this to users directly; see onym.app/privacy.

CONSEQUENCE

What durable copies cost everyone

One new seat and one existing seat's profiles both sell the same thing: a copy that persists exactly when the person is absent. Durability and secrecy pull against each other, so the terms are the product — which is why they are published here beside the capability.

What an operator must settle before it holds anything

Pinned in advance, binding forward

Retention period, the deadline for honouring an erase request and what erasure provably does not cover, jurisdictions and sub-processors, the export format the person can walk away with, the price, what happens when payment stops, and how a breach is disclosed. New terms govern new snapshots; a policy that can be restated after the data has arrived is leverage over someone's history, not a service.

Sealed, or it is not a backup

Ciphertext only; keys stay on the device; no server-side indexing or deduplication by content; restore proves possession of the person's own key rather than an account password an operator can reset. The honest cost of that rule is stated too: a lost key means an unreadable archive and no operator recourse, because every mechanism that would provide recourse would let the operator read what it stores.

A single holder is custody, and must say so

Seed custody is not a seat of its own — it is how the recovery trustee's profiles differ. The threshold profile splits material so no one holder can use it; the cloud profile is a declared 1-of-1 custodian whose operator can technically recover what it stores. Both are legitimate; only one is sealed, and a person choosing a single holder is owed that distinction before enrolment rather than after a subpoena.

And what it still costs, once all of that is honoured

Backups outlive the sender's expectation

Message carriage and media storage can promise short retention; a recipient's backup quietly extends it for both sides of every conversation. Deletion stops at the edge of other people's archives, and the sender is never asked. Anyone reading a retention promise should read it as covering the route, not the copies people keep at the ends of it.

A single holder concentrates compulsion

A custodial recovery holder can be ordered, breached, or pressured to produce what it holds, in a jurisdiction the person chose once and may not revisit. The exposure exists from enrolment, not from use, and the identity's safety then depends on a stranger's operational security as well as the holder's. A threshold set spreads that; it does not remove it, since any threshold can collude.

Why it is written here

No operator can be trusted to disclose the tension between durability and secrecy in its own pricing page. The Foundation would fund grants and audits for these seats once their contracts merge, so the cost belongs in its public record beside the capability — the same rule applied to the moderation seat above.

The bounds, stated exactly: none of this changes what a courier can read or what encryption protects in transit — it changes how long a copy exists and who else can be compelled to produce it. A backup restores history, never an identity: seed material, recovery artifacts, and trustee shares are ineligible for a snapshot, which is what the recovery trustee seat exists for. What the Foundation is asking upstream for is the profile that is missing — a sealed single-holder custody profile whose operator cannot unwrap what it holds, beside the custodial one that already exists.

PROCESS

How registering interest works

Deliberately anticlimactic.

01

Email us what you'd run.

02

We answer with what the commons can offer — or an honest "nothing yet".

03

You build — with or without us.

"Step 03 never required steps 01–02."

Earnings follow choice, not lock-in.

No surveillance-based revenue — metering is aggregate by design.

Recognition and audits are earned, never bought.

Seats need a funded commons first — meet the founding sponsors.