RWA Oracle · Compliance
Compliance attestations for real-world assets
The Compliance application on AgentVault — tokenized real-world assets need verifiable data. Ownership records, jurisdiction, and audit hashes become on-chain attestations with reputation scores anyone can verify.
Overview
Regulated assets cannot rely on off-chain PDFs alone. Investors and protocols need a tamper-evident signal that asset metadata was reviewed and scored. AgentVault RWA Oracle closes that loop: submit asset identifiers, let the agent validate the submission, then publish an attestation on Casper that anyone can read.
This is the compliance layer for agentic RWA markets — the on-chain primitive that verifiers, oracles, and policy engines can build on.
Dashboard actions
| Action | Type | Contract call |
|---|---|---|
| Submit asset data | Advisory | Agent validates asset ID, data hash, and jurisdiction fields |
| Verify hash | On-chain tx | Attestation.update_reputation — bumps reputation score |
| Publish attestation | On-chain tx | Attestation.init — stores data_hash and initial_score on-chain |
On-chain attestation model
- issuer — the wallet that published the attestation
- data_hash — fingerprint of the underlying asset payload
- timestamp — block time at publication
- reputation_score — numeric trust signal, updatable via verify flow
Contract entry points: init(data_hash, initial_score) and update_reputation(new_score).
Before you publish