Developer Reference
Start with the specification and the exact deployment/artifact revision when building an integration. Consumer guide simplification does not change contract interfaces, account formats or security requirements.
Specification and interfaces
The Protocol Specification defines note relations, encodings, external execution, service profiles, account files, validity rules and source correspondence. The current statement schema uses 71 monetary signals or 11 account-only signals, including checkpoint advancement and proof expiration.
The published format vectors, Poseidon parameters and contract interfaces match the current implementation. Generated sources, reproducible fixtures and the pinned release record define the integration boundary; test vectors are not production qualification evidence.
Integration references
- Contracts and Deployments for contract relationships and version bindings.
- Circuits, Proving, PLONK and Cryptography for relation and implementation detail.
- State & Notes, Account State and Account History for formats and reconciliation.
- Intent services, Transfer Delivery and intent service operations for transport and service behavior.
- Account Client and Google Account Architecture for key bootstrap, access and client behavior.
- Margin Architecture for typed actions, market eligibility and failure cases.
- Circuit Artifacts and Multisig Administration for release and operating procedures.
Source access
Repository source references are shown with their file paths when the source is not a published documentation page. Source access and independent security review must be established separately.
Integrators need access to the exact reviewed source and generated release files before relying on an interface.