420Docs context
Skip to content

420 Token developer integration

Discover the current template registry and factory through canonical Registry/deployment metadata. Present enabled templates and their exact semantics rather than inventing client-side variants.

After deployment, preserve the token address, creator, template/version and configuration hash as provenance and let downstream protocols perform independent qualification.