PRODUCT
How Log On Chain works
- Sign in with Google → we create a portable client profile and an HttpOnly session.
- Submit a log or dataset via console or API → content is indexed in our database (ATP).
- Anchor → a keccak commitment is written to XDC; we store
chain_tx_hash. - Verify → check the explorer tx and that the hash matches your payload commitment.
LAYERS
- API / session — human Google OIDC + machine ORDS OAuth
- System of record — ATP (ownership, status, hashes)
- Chain — XDC commitment (not full blobs)
- Future durable store — IPFS/Filecoin hat without schema rewrite (ADR-003)