420Docs context
Skip to content

APPSTORE-1 — service/runtime scaffold

APPSTORE-1 turns the Genesis AppStore profile into a runnable, contract-free service scaffold without giving the catalogue protocol authority.

Configuration

The service is configured through:

  • APPSTORE_CHAIN_ID — expected chain ID; defaults to 420;
  • APPSTORE_RPC_URL — canonical RPC endpoint;
  • APPSTORE_REGISTRY_ADDRESS — canonical Registry/ProtocolRegistry deployment used for startup qualification;
  • APPSTORE_CATALOGUE_STORE — path reserved for non-canonical catalogue persistence introduced in later phases;
  • APPSTORE_LISTEN_ADDR — HTTP listen address; defaults to :8426.

Invalid or incomplete configuration fails startup.

Startup qualification

Before accepting traffic, the service checks canonical chain state through RPC:

  1. eth_chainId must match the configured network;
  2. the configured Registry address must contain deployed bytecode.

A wrong chain, unavailable RPC, malformed RPC response or missing Registry deployment leaves the service unready and causes startup to fail closed.

These checks establish only that the service is attached to the intended network and Registry deployment. APPSTORE-1 does not yet ingest Registry entries or build catalogue records; that begins in APPSTORE-2.

Health and readiness

GET /healthz reports process health and explicitly returns canonical: false.

GET /readyz returns success only after startup qualification passes. Readiness therefore cannot be used to imply that AppStore owns canonical application state.

Authority boundary

The runtime cannot:

  • create or revoke Registry registration;
  • rewrite canonical service identity or version provenance;
  • sign transactions or hold wallet keys;
  • grant Smart Account capabilities;
  • make a listing equivalent to audit, endorsement or protocol legitimacy.

420Registry and chain state remain canonical. 420Wallet and Smart Accounts remain the authorization boundary.

Process lifecycle

The production entrypoint is appstore/cmd/appstore420. It qualifies the network before serving HTTP, uses bounded HTTP timeouts and shuts down gracefully on interrupt or SIGTERM.