Protocol
Developers and security
Published contract references, planned developer access, review status and legal information.
Contracts and interfaces
Section titled “Contracts and interfaces”Use published source, release tags, deployment addresses and network-specific references to verify the rules for a particular release. Contract events can support indexing; an event alone does not establish that a platform service is available. See Contracts and addresses.
A unified platform API and MCP access are planned. The availability of an API, SDK or agent integration should be checked against published implementation and release information. Agents do not receive authority over the user’s browser-held execution keys.
Security and legal
Section titled “Security and legal”Independent security review in progress.
Review status is not a guarantee of safety. A specific deployment, transaction and third-party project must be assessed on its own merits. Product availability and applicable rules can differ by region. See Security and custody, Risk disclosure, Terms of Service and Privacy Policy.
