> 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/protocol-economics/attestation-services.md). # Attestation Services Explains the attestation lookup service built around KAR and the protocol's per-query revenue model for accessing recorded RWA trading decisions. ## Attestation Services KAR, the Attestation Registry, permanently records RWAPACT risk decisions and their associated context on-chain. Those records remain useful after the original trade decision. A downstream application, auditor, agent, or protocol component may need to inspect a prior decision and understand the conditions associated with it. ### Attestation context The RWAPACT attestation structure records the following decision data: | Field | Purpose | | -------------------------- | ----------------------------------------------------------------- | | Attestation ID | Identifies the recorded decision. | | Agent ID | Identifies the agent that submitted the trade. | | Session ID | Identifies the active session evaluated by KSO. | | Asset | Identifies the requested RWA asset. | | Amount | Records the requested trade amount. | | Risk score | Preserves KRO's risk assessment. | | Policy version | Identifies the KPV policy governing the decision. | | Gas route hash | References the gas route evaluated by KGR. | | Approval status | Records whether RWAPACT authorized execution. | | Rejection reason | Identifies the failed condition when applicable. | | Timestamp | Records when RWAPACT made the decision. | | Execution transaction hash | Associates an authorized decision with execution when applicable. | Together, these fields let a consumer inspect which agent requested the trade, which session applied, and whether RWAPACT approved or rejected it. A rejected record can identify why authorization did not proceed. An approved record can later associate the execution transaction. ### Attestation lookup model RWAPACT's revenue model includes an attestation query service. A consumer that needs to retrieve or query a stored attestation can use the service. The current economics define a per-query fee for attestation lookup. This is a micro-fee usage stream. The specification does not define an exact fee amount. ``` Trade Decision -> KAR Records Attestation -> Attestation Stored On-Chain -> Consumer Queries Record -> Query Fee ``` ### Practical query use cases Attestation lookups can support several forms of later analysis. #### Post-trade auditing An application can inspect the conditions associated with a historical trade. The record provides context beyond an execution transaction alone. #### Rejection analysis A consumer can inspect why an autonomous request was rejected. The rejection reason and associated risk, session, and policy context remain available for review. #### Decision verification A system can verify which risk score and policy version were associated with a particular decision. This supports analysis of the policy state that governed the request. #### Agent activity analysis A consumer can inspect the agent and session context associated with recorded decisions. This can help analyze how delegated authority was used. #### Dispute analysis The attestation can provide the underlying decision context for later analysis. KAR does not automatically resolve disputes. ### Storage and lookup are separate activities Recording an attestation is part of the Pact decision flow. KAR records an approval or rejection after the required checks produce a decision. Querying an attestation is a separate consumption activity. This distinction matters for the economic model. | Activity | Purpose | Economic model | | --------------------- | ------------------------------- | ---------------------- | | Attestation recording | Preserve the decision context | Core protocol function | | Attestation lookup | Retrieve recorded decision data | Per-query micro-fee | ### ERC-8273 compatibility The RWAPACT specification states that KAR implements an ERC-8273-compatible interface. This supports interoperability with other attestation-based systems while adding an RWA-specific attestation schema. This compatibility statement is limited to the specification. It does not claim additional capabilities. ### Attestation as Data Infrastructure Attestation Services turns RWAPACT's decision history into queryable protocol infrastructure. The record is not disposable execution metadata. It preserves the context needed to inspect a decision after the trade request has been approved or rejected. *** --- # 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/protocol-economics/attestation-services.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.