Integration Steps
Onchain Integration
Require users to provide an authentic attestation from Predicate in order to access your business logic
Supported Blockchains
Application Compliance is available on any chain where the Predicate Registry has been officially deployed.Predicate Registry
The Predicate Registry is the core onchain contract which applications leverage to verify compliance attestations. It has two primary responsibilities:- Attester management — Stores authorized attester addresses that can sign attestations
- Attestation verification — Validates the authenticity of attestations
FAQ
Who owns the Predicate Registry?
Who owns the Predicate Registry?
Predicate Labs owns and operates the registry.
How is the Predicate Registry architected?
How is the Predicate Registry architected?
The registry uses the ERC-1967 upgradeable proxy pattern:
- Proxy contract — The address you interact with, which delegates calls to the implementation
- Implementation contract — Contains the logic and can be upgraded by the owner
- Two-step ownership — Uses
Ownable2StepUpgradeableso ownership transfers require explicit acceptance
How are attester key rotations handled?
How are attester key rotations handled?
Keys are rotated on a frequent basis. New keys are registered before old keys are deregistered, ensuring zero downtime during rotation.
What signature scheme is used?
What signature scheme is used?
ECDSA on EVM chains, Ed25519 on Solana.
How does replay protection work?
How does replay protection work?
Each attestation includes a unique UUID that is marked as spent after validation. The chain ID is also included in the signed hash to prevent cross-chain replay.