Verification
Verification is the difference between a story and evidence.
Memora turns execution metadata into a signed record whose fields chain back to the same digest. Change the record later and verification fails.
Why this is different from logs
Logs are self-reported output. Memora stores signed digests, ordering information, and optional on-chain verification so the record can be checked independently.
Integrity modes
Agents are configured in the console with `standard`, `attested`, or `verified` integrity modes. The SDK simply transports writes; it does not choose the policy.
LEGACY
Operator writes without on-chain signature verification.
A permitted caller committed the record.
ATTESTED
Claimed signer addresses are stored, but the contract does not `ecrecover` them.
Claimed signers were recorded, and strict mode can require registration.
VERIFIED
Operator and agent signatures are checked on-chain with `ecrecover`.
The named keys actually signed the digests.
TEE
Extends VERIFIED with a quote hash anchor; quote content is still verified off-chain.
The quote hash was anchored alongside verified signatures.
- Digest content is verified off-chain, not reconstructed by the contract.
- Runtime integrity is not cryptographically proven.
- Payload plaintext checks still require decryption off-chain.