Skip to content

FAQ

How is this different from just hashing my logs?

Section titled “How is this different from just hashing my logs?”

A local hash proves nothing if the same party can recompute and replace it. AeternisLog anchors the hash (a Merkle root) on an independent, immutable ledger, so the proof doesn’t depend on trusting whoever stores the data.

How is it different from “putting data on a blockchain”?

Section titled “How is it different from “putting data on a blockchain”?”

Only compact Merkle roots go on-chain — never your data. Your records stay in MongoDB where they’re fast, queryable, and private. You get blockchain-grade immutability for the proof and database-grade performance for the data.

A batch’s Merkle root, a batch id, a record count, a timestamp, and (for the caller’s own records) the record-id list — nothing else. Payloads never leave your database.

Do I have to trust AeternisLog to believe a verification?

Section titled “Do I have to trust AeternisLog to believe a verification?”

No. The Go and Python SDKs (and the offline CLI) recompute the hashes and Merkle root locally and compare them with the root read from the blockchain. The server is never in the trust path for verification.

A permissioned Hyperledger Fabric network (Raft ordering). It’s private and permissioned — no public chain, no gas, no cryptocurrency.

Can one tenant see another tenant’s data?

Section titled “Can one tenant see another tenant’s data?”

No. Records are isolated per (tenant, domain) at the API, and — with per-tenant identities — isolation is enforced at the ledger by the caller’s signed identity. See tenant isolation.

Records are marked anchor_failed (never lost) and a reconciler re-drives them. The WAL guarantees an acknowledged record survives a crash.

AeternisLog guarantees integrity, not confidentiality. Encrypt sensitive payload fields before sending if you need confidentiality; the integrity proof works over whatever bytes you store.

Yes — the platform is hardened (see the hardening summary). Review the hardening checklist and the known limitations in tenant isolation for multi-tenant deployments.

Community support is via GitHub. For SLAs and assisted deployments, open an issue.