Trust center

Current network: Ethereum Sepolia testnet

Proofs are anchored on Sepolia (chain ID 11155111), a public test network. Mainnet anchoring has not been enabled. Records anchored on Sepolia are publicly checkable, but a test network does not carry the economic finality of a production network. Sepolia’s operators plan to retire it; before that, existing anchors will be archived and re-anchored, and we make no promise that any public network will stay available.

Contracts

iBlock Trace is built to use the same registry with a separate key prefix and has no contract of its own. Trace anchoring is not yet enabled in production.

Keys and roles

Administration and pause rights sit with a 2-of-3 Safe multisig: 0x945400DE4bDd49A22B07f3F5afc9fDBC4f342f87.

Records are registered and revoked by a signing key held in AWS KMS (0x8A70bE64347e24b779E641161BeCD7dbe8F0F172). The private key cannot be exported.

Verify registration receipts are signed by a separate AWS KMS key (0x1c8d14EAD8cbe22569188209bac71Ee71d5be174). This key cannot send transactions and the transaction key cannot sign receipts. Earlier receipt keys stay listed here after a rotation.

The deployer address holds no role.

What goes on-chain

• Verify: a salted commitment for each record (records created before 17 October 2026 use the raw SHA-256 document hash). Never the document itself.
• Trace (once anchoring is enabled; it is not enabled in production yet): a checkpoint hash and registry key per batch checkpoint. No personal data, product names or customer identifiers.

Check a proof yourself

Verify: Open the share link and select the document. Your browser computes SHA-256("iblock-verify:v2:commitment" ‖ 0x00 ‖ salt ‖ document hash) on your device and shows the result. Compare it with the value in the anchor transaction on a block explorer. The salt travels in the link after #s= and is never sent to our server.

Verify receipt: On the verification page, open “Registration receipt” to download the receipt JSON or check its signature in your browser. The receipt is EIP-712 typed data (domain name “iBlock Verify Receipt”, version “1”, no chain ID) over the record ID, commitment, registration time, chain, registry, transaction, block number, block hash and block time. Recover the signer with any EIP-712 library and compare it with the receipt key above. A revoked record also carries a revocation receipt (primary type “Revocation”, with the revocation time and the revoke transaction) once the revocation is confirmed on chain. Both receipts stay checkable after the anchoring network is retired.

salt         = 0x00…01 (63 zeros, then 1)
documentHash = SHA-256("document")
commitment   = a2b92e66aabe4f946fe3cd09413a290240786a313f6ce7f875bd98662fb285a6

Trace, once anchoring is enabled: Recompute the Merkle root from the inclusion proof, recompute the checkpoint hash and registry key, then confirm the registry entry, revocation state and transaction receipt.

What a proof does and does not show

A match shows that a document or record is identical to what an identified organization registered, and whether it has been revoked. It does not show that the contents are true or legally valid.

Data handling

• Document bytes are never uploaded or stored. Hashing happens in your browser.
• The salt for a record is available only to the issuing organization and to people it shares the link with.
• Erasure removes the salt from our service; it cannot remove copies of a link already shared or data already on a public chain.
• Retention, deletion and the providers that process account and product data are described in the platform privacy notice (iblocktechs.com/privacy/platform).

Infrastructure providers

Reporting a security issue

Email hello@iblocktechs.com with the subject "Security report". We aim to acknowledge reports within 3 business days and ask for coordinated disclosure.

What we do not claim

No independent security audit or certification has been completed for these services. Independent contract review is scoped separately before mainnet use.