> For the complete documentation index, see [llms.txt](https://rwapact.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwapact.gitbook.io/whitepaper/integrations-and-standards/erc-8273.md). # ERC-8273 How ERC-8273-compatible attestations support KAR's on-chain record of Pact decisions. ## ERC-8273 KAR, the **Attestation Registry**, permanently records Pact decisions on-chain. It records both approved and rejected Trade Intents. RWAPACT uses an ERC-8273-compatible attestation approach for interoperability with attestation-based systems. KAR retains an RWAPACT-specific schema because RWA agent trading needs decision context beyond a transaction reference. ### Decision context, not only transaction history The value of an Attestation is the state captured when the Pact evaluated a trade. It preserves the context behind the decision: * The Attestation ID, Agent ID, Session ID, asset, and amount identify the request. * The Risk Score, Policy Version, and Gas Route Hash preserve the evaluation context. * Approval status, Rejection reason, and timestamp preserve the decision and when it occurred. * The execution transaction hash is associated after execution, when applicable. ``` Pact Evaluation -> Authorization or Rejection -> KAR Attestation -> Execution transaction reference when applicable ``` An execution transaction hash alone does not explain why a trade was permitted. KAR records the pre-execution decision context that led to Authorization or Rejection. ### Authorization and Attestation Authorization answers whether a Trade Intent may proceed to the Execution Layer. Attestation answers what RWAPACT evaluated and decided. KRO, KSO, KPV, and KGR perform the risk, Session, policy, and gas evaluations required by the Pact. ERC-8273 compatibility does not perform those checks. It provides the standards-compatible framing for KAR's record of their outcome. For a rejected Trade Intent, the Attestation preserves the Rejection reason and relevant context. No execution transaction hash is expected when the trade never reaches execution. ### RWAPACT-specific schema KAR implements ERC-8273 compatibility while adding an RWA-specific Attestation schema. This keeps the record interoperable while preserving the information needed to inspect autonomous RWA decisions. Read [Attestation](/whitepaper/pact-execution/attestation.md) for the complete KAR record and its lifecycle. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rwapact.gitbook.io/whitepaper/integrations-and-standards/erc-8273.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.