Publish an Attestation via the Portal
The OMATrust Portal provides a form-based interface for publishing attestations without writing code.
info
This page covers the portal UI workflow. For programmatic attestation publishing, see the SDK Quickstart.
Prerequisites
- Signed in to app.omatrust.org via social login or self-custody wallet — see Connect or Sign In
- The DID of the service you're attesting (e.g.,
did:web:example.com)
No gas fees or OMA tokens are required. The portal uses a delegated attestation flow.
Attestation Types
You can publish the following attestation types through the portal:
| Type | Who publishes | Purpose |
|---|---|---|
| Security Audit | Auditor | Attest that a service passed a security review |
| Compliance Certification | Certifier | Attest compliance with a standard (SOC2, ISO, etc.) |
| Endorsement | Any entity | Vouch for a service's quality or reliability |
| User Review | End user | Share your experience with a service |
| Review Response | Service operator | Respond to a user review on-chain |
Publishing Flow
- Select the attestation type
- Enter the target service DID
- Fill in the attestation-specific fields (score, comments, evidence URL, etc.)
- Review the attestation preview
- Click Submit — your wallet will prompt you to sign the attestation data
- The portal submits the transaction on-chain via the delegated flow
- Wait for confirmation
Once confirmed, the attestation is permanently recorded on OMAChain and verifiable by anyone.
Delegated Flow
The portal uses delegated attestations — you sign the attestation payload with your wallet (or embedded wallet), and the OMATrust backend submits the actual on-chain transaction. This means:
- No OMA tokens needed
- No network switching in your wallet
- Your signature is still cryptographically tied to your account
Next Steps
- Learn about attestation types and schemas in detail
- Want to publish programmatically? See the SDK Quickstart