Protocol
How an attestation is built, signed, and checked without calling Attestra.
Attestra reads a fact from the chain that holds it, signs it, and returns an attestation. Credentials never move between chains. Nothing is reissued.
That design exists to answer one objection: does this mean your credential gets copied onto another chain? No. Only small signed facts cross chains: DID documents, revocation status, trust registry entries. Private fields never leave the network that owns them.
This track substantiates a stronger claim: the answer is verifiable without Attestra. Every attestation is signed over a digest that any of the three chains can recompute independently. A contract on Ethereum, a pallet on eIDChain, and chaincode on Hyperledger Fabric each check it with no call back to us. The pages that follow exist so you can do that yourself, and they show that the same rule is implemented four times over, in four languages.
In this track
- The canonical digest
- Verifying an attestation
- Push and pull
- The oracle network
- Chains and DID methods
- Credential status
- Trust model
- Explorer
Looking to call the hosted API instead of verifying independently? Start at Reference.