420Docs context
Skip to content

420Docs

420Docs is the canonical documentation portal for the 420 Integrated ecosystem.

The source for this site lives in the docs/ directory of the main 420 Integrated repository. The rendered site is a presentation and discovery layer; repository-controlled documentation remains authoritative.

Choose what you want to do

  • Get Started — learn what 420 Integrated is, set up 420 Wallet, receive or acquire $420, make a first transaction, and learn security basics.
  • Use 420 Integrated — complete day-to-day tasks such as sending funds, connecting dApps, signing transactions, managing permissions, bridging, staking, governance, and safely using 420Automation.
  • Build on 420 Integrated — integrate contracts, RPC, SDKs, 420Indexer, 420Automation, Wallet, storage, AI, bridge, and game infrastructure.
  • Operate 420 Integrated — run validators, nodes, RPC endpoints, storage/resource services, compute providers, gateways, indexers, automation workers, and oracle infrastructure.
  • Architecture — inspect chain, consensus, protocol, infrastructure, application, security, governance, and trust-boundary architecture.
  • Reference — find exact chain IDs, network configuration, deployed addresses, constants, events, errors, and canonical terminology.
  • Troubleshooting — diagnose failures and follow safe recovery procedures.
  • 420Automation infrastructure — scheduling, triggers, workers, replay/finality safety, resource bounds, and the non-authority boundary.
  • Use 420Automation safely — task-oriented guide to registering/managing jobs, trigger behavior, ambiguous submissions, and fail-closed security behavior.

Documentation principles

420Docs is designed to be:

  • task-oriented for users;
  • precise and implementation-aware for developers and operators;
  • explicit about permissions, value movement, trust boundaries, and failure recovery;
  • version-aware;
  • reviewable as source-controlled Markdown;
  • expandable as new applications and protocols join the ecosystem.

Documentation project

DOC-0 established the taxonomy, application documentation contract, Architecture Decision Record format, diagram conventions, terminology rules, and contribution requirements. DOC-1 is building the public site, navigation, publication pipeline, and repository entry points.

See the Documentation Roadmap, Documentation Contribution Policy, and Style Guide.