Genesis application manuals¶
This section is the canonical task-oriented manual collection for user-facing applications that ship with, or are explicitly scoped to, the 420 Integrated Genesis environment.
The frozen public application inventory remains config/genesis-applications.json. DOC-18 additionally reconciles contract-backed Genesis surfaces from contracts/config/genesis-dapp-contract-map.json so implementation families that are not separate public-catalog entries still receive governed documentation ownership.
Available manuals¶
- 420 Wallet — account management, authorization, security, economics, troubleshooting and developer integration.
- 420 Explorer — blocks, transactions, receipts/logs, addresses, contracts, provenance and finality-aware chain inspection.
- 420 Search — unified public discovery with explicit provenance, privacy boundaries and ranking-as-presentation semantics.
- 420 Analytics — reproducible metrics, trends and dashboards with source-window, version and finality context.
- 420 AppStore — curated application discovery with Registry-backed provenance, permission/security context and non-authoritative ranking/curation.
- 420 Verify — reproducible deployed-source/build verification with explicit result classes and no audit/endorsement implication.
- 420 Notifications — opt-in, replay-safe alerts that preserve event provenance without gaining execution authority.
- 420 Status — network/service health, readiness and incident presentation that remains observational rather than canonical.
- 420 Registry — canonical service discovery/versioning with explicit limits on what registration means.
- 420 Names —
.420lease, forward/reverse resolution, transfer and expiry workflows. - 420 Identity — optional pseudonymous profiles, governed issuers and lifecycle-bound credentials.
- 420 Swap — bounded canonical swap execution with explicit route, authorization, fee, minimum-output and safety semantics.
- 420 Bridge — verified, replay-protected cross-chain movement with explicit chain/asset/route/proof/risk boundaries.
- 420 Token — governed-template ERC asset deployment with deterministic provenance and the exact 42 native
$420creation fee. - 420 Stake — validator bond/lifecycle/reward visibility without public delegation or stake-weighted governance.
- 420 Governance — frozen proposal rules/electorates, voting, timelock and exact committed execution.
- 420 Arbitration — domain-scoped disputes, evidence commitments, rulings, bounded appeals and explicit remedy-consumption boundaries.
- 420 AI — model/provider/job/verification/settlement workflows with bounded spend, privacy and off-chain compute execution.
- 420 Attention — opt-in sponsor campaigns, consent, proof commitments, reward entitlements and segregated sponsor liabilities.
- 420 Launchpad — qualified project registration, sale configuration and allocation workflows; registration is not endorsement.
- 420 Faucet — explicitly testnet-only distribution for developer onboarding, with no monetary value and bounded abuse controls.
The completed Genesis application coverage audit records the original DOC-8.10 package, navigation, authority/security and scope checks. DOC-18 extends governed coverage to additional contract-map surfaces without rewriting the frozen public Genesis catalog.
Manual contract¶
Each user-facing application documented under docs/apps/<app-id>/ uses the standard package: overview, getting started, user guide, concepts, architecture, permissions, fees, security, troubleshooting, FAQ, and developer integration pages for contracts, API, events, errors and examples.
Generated ABI/API/event/error reference belongs in DOC-10; application manuals explain how to use those interfaces safely.
Genesis manual inventory¶
| Application | Class | Manual | Primary role |
|---|---|---|---|
| 420 Wallet | Genesis user app | available | Smart Account management, capabilities, recovery, assets and dApp access |
| 420 Explorer | Genesis user app | available | chain, transaction, contract, validator, asset, governance and finality inspection |
| 420 Search | Genesis user app | available | unified discovery across canonical and registered public ecosystem data |
| 420 Analytics | Genesis user app | available | rebuildable analytics, metrics, trends and dashboards |
| 420 AppStore | Genesis user app | available | non-authoritative application catalogue and security/provenance context |
| 420 Verify | Genesis user app | available | reproducible deployed-contract source verification |
| 420 Notifications | Genesis user app | available | opt-in event alerts with source provenance and no execution authority |
| 420 Registry | Genesis protocol + user app | available | canonical registered contract/token/application/service discovery |
| 420 Names | Genesis protocol + user app | available | human-readable .420 names layered over canonical identities |
| 420 Identity | Genesis protocol + user app | available | optional pseudonymous profiles, credentials and reputation |
| 420 Arbitration | Genesis protocol + user app | available | dispute cases, evidence commitments, rulings and bounded appeals |
| 420 Swap | Genesis protocol + user app | available | canonical exchange/swap user surface |
| 420 Bridge | Genesis protocol + user app | available | verified, replay-protected cross-chain value movement |
| 420 Stake | Genesis protocol + user app | available | validator bond, registration, lifecycle, rewards and withdrawals |
| 420 Governance | Genesis protocol + user app | available | proposals, houses, voting, treasury and timelock workflows |
| 420 AI | Genesis protocol + user app | available | provider/model/job/escrow/reputation AI-compute workflows |
| 420 Attention | Genesis protocol + user app | available | opt-in sponsor campaigns, proofs and attention rewards |
| 420 Token | Genesis protocol + user app | available | qualified token-template deployment for the fixed native $420 creation fee |
| 420 Status | Genesis user app | available | network/finality/validator/RPC/protocol service health |
| 420 Faucet | testnet only | available | no-value testnet distribution and developer onboarding |
| 420 Gaming Protocol | Genesis protocol only | not an application manual target | shared optional-wallet game interoperability; covered by protocol/developer documentation |
| 420 Launchpad | Genesis contract-map application surface | available | qualified project launch, sale and allocation workflows |
The protocol-only Gaming Protocol remains part of Genesis but has no standalone user application in the frozen catalog. Launchpad is documented under DOC-18 because it exists as a distinct contract-backed application surface in the Genesis contract map even though it is not a separate entry in the frozen public-catalog file.
Authority labels every manual must preserve¶
Every manual must distinguish canonical-state authority, user application over canonical state, derived/rebuildable presentation, replaceable provider/service infrastructure, and testnet-only scope.
Registry, Names and Identity remain bounded to discovery/naming/identity state. Swap, Bridge and Token preserve separate value-domain authorities. Stake, Governance and Arbitration continue that separation. AI and Attention follow the same model: workers/providers do not gain chain authority, result commitments do not become universal truth proofs, sponsors/verifiers do not gain Wallet authority, and raw private payloads/telemetry remain outside canonical public state. Launchpad registration does not create endorsement, investment suitability, asset legitimacy or Wallet authorization. Faucet is strictly testnet-only: it does not define issuance policy, participate in mainnet genesis economics or create monetary entitlement.
Security and support rule¶
No manual may instruct a user to disclose private keys or recovery secrets, passkey private material, Wallet signing secrets, validator signing keys, JWT/Engine credentials, private evidence payloads, private Messenger payloads, encrypted Resource payloads, raw Attention telemetry, private AI prompts/datasets/outputs or unrelated private Identity fields. Faucet support requires only a public destination testnet address and normal abuse-control input.
Documentation history¶
DOC-8 completed the frozen public Genesis application manual set. DOC-18 extends governed coverage to additional Genesis contract-map surfaces while preserving that frozen catalog boundary.
Related documentation¶
- Genesis application coverage audit
- DOC-18 reconciliation roadmap
- Application documentation contract
- 420 Launchpad architecture
- Registry, Names, Identity & 420-IS architecture
- Pay, Token, Swap/Exchange & Bridge architecture
- Stake, Governance, Treasury & Grants architecture
- 420 Arbitration architecture
- 420AI compute infrastructure
- Messenger, Notifications & Attention architecture
- 420 Wallet user documentation
- 420Indexer infrastructure
- Core protocol architecture
config/genesis-applications.jsoncontracts/config/genesis-dapp-contract-map.jsontestnet/services/faucet-policy.jsontestnet/public-services/faucet/operations.json