Programmable

Documentation files

Choose the smallest document that contains the context your integration needs.

/docs/developers.mdThe integration guide as Markdown.
/llms.txtA short source index and the required interpretation rules.
/llms-full.txtExpanded context for readers that need the complete overview in one response.

Resolve the current Router first. Then pin the exact ABI bytes and verification reference used by your build.

Discovery documentStable entry point that supplies manifestUrl.
Live manifestChain, Router, live range, runtime, immutable bindings, event topics, ABI URL and digest.
Hosted Router ABIHash the exact downloaded bytes and match sha256:bb4e728e9f9c850eb01f928e8a798ac206a82e241a8d93b3b3c686635c88ed86.
Router ABI on GitHubThe same interface in the public developer repository.
GitHub Router referenceComplete point-verification specification and finalized PCAN test case.
Terminal and scanner guideBackfill, live follow, overlap, reorg and finality handling.
JSON-RPC verifierDependency-light reference implementation.
viem verifierTyped application reference implementation.

The files have different jobs. Do not treat a model-context file as a replacement for the live contract binding.

Live manifest: Supplies the current chain, Router, block range, runtime, bindings, topics and ABI digest.
Hosted ABI: Defines the contract interface. Verify its exact bytes against the manifest digest.
GitHub Router reference: Defines the canonical point-verification algorithm and test vector.
Web, Markdown and model context: Explain and route the integration. /llms-full.txt is expanded convenience context, not the normative algorithm.

Programmable documentation endpoints require no authentication.
Ethereum RPC authentication depends on your provider.
After manifest and ABI bootstrap, point verification needs an Ethereum provider only.