Smart Contracts

TruthID is six Solidity contracts on Base — no backend, no database. Everything described below is on the public chain and independently checkable; this page exists for integrators who want to read on-chain data directly, write their own SDK, or just verify what's actually deployed.

All six contracts are verified on Basescan and carry no upgrade proxy — a bug can't be hot-patched in the deployed bytecode. That's not the same as the deployed addresses being permanent, though: TruthIDAccount and TruthIDAccountFactory both have an owner-controlled updateRegistries function specifically so existing smart accounts can be redirected after a migration to a new deployment, which has happened more than once as issues were found and fixed (see Security Model → Audit status). The addresses below are current as of the latest deployment.

Addresses

Base Mainnet (production, chain ID 8453)

Base Sepolia (testnet, chain ID 84532)

Use testnet while developing — see Networks in the SDK reference for how to point a client at Sepolia. VaultRegistry isn't deployed on Sepolia today (Mainnet only). TruthIDAccount itself isn't listed here — every identity gets its own instance, deployed on demand by the factory; see Smart Account & Gas for how that address is computed.

Getting the ABI

You probably don't need this — the SDKs already wrap every contract call behind plain functions. Reach for the raw ABI only if you're reading state from a language without an official SDK, or auditing the deployment yourself.

• Basescan — since every contract is verified, each address page above has a "Contract" tab with the full ABI and source, plus a one-click "Export ABI" button. This is the easiest source and always matches what's actually deployed.
• GitHub source — the canonical .sol interfaces: IdentityRegistry.sol, DeviceRegistry.sol, RecoveryManager.sol, SessionRegistry.sol, VaultRegistry.sol, TruthIDAccount.sol.

There's no published npm/PyPI/RubyGems package containing the full ABI JSON — the SDKs only embed the minimal fragment each function needs internally. To generate the full artifact yourself: git clone the repo, then cd contracts && forge build (output lands in the gitignored out/ directory).

Contract reference

A quick map of what each contract does and who's allowed to call what. Full behavior (commit-reveal, guardian thresholds, session hashing) is covered in How TruthID Works and Security Model — this is just the function list.

IdentityRegistry

Username ↔ controller wallet mapping. The root of every other contract — DeviceRegistry, RecoveryManager, and SessionRegistry all resolve a caller's identity by asking this contract who controls which username.

DeviceRegistry

Device public keys per identity, registered via commit-reveal to prevent front-running. Caps at MAX_DEVICES = 50 per identity.

RecoveryManager

M-of-N guardian recovery with a 7-day timelock (TIMELOCK constant) and a 20-guardian cap (MAX_GUARDIANS constant).

SessionRegistry

Stores only a keccak256 hash per session — never the data it represents.

TruthIDAccount

The ERC-4337 smart account that controls an identity — one instance per owner, deployed via TruthIDAccountFactory. Full explanation of the two signer tiers, setup flow, and cost is in Smart Account & Gas; this is just the function list.

TruthIDAccountFactory

Deploys TruthIDAccount instances at deterministic CREATE2 addresses, one per owner (or per owner + index, for multiple accounts).

VaultRegistry

Stores a pointer to the user's encrypted Vault blob — never the Vault's contents. The cid field name is a holdover from when this always held an IPFS CID; today it typically holds an ar://<transaction-id> reference instead (see Cross-Device & Storage for why). Content integrity is checked against contentHash, a keccak256 of the encrypted blob.

Cost per operation

Real gas numbers from the project's own test suite (forge test --gas-report), not estimates — IdentityRegistry/DeviceRegistry/RecoveryManager/SessionRegistry have 140 tests passing; TruthIDAccount/TruthIDAccountFactory (rows below revokeAllSessions) have their own 62. VaultRegistry's operations aren't in this table — updateVault is the only state-changing call, and its cost is dominated by the size of cid/contentHash you pass in rather than fixed contract logic. Read functions (view) are free when called the normal way — directly via an RPC eth_call, exactly how every SDK reads them. The "free" label below stops applying only if another contract calls them mid-transaction, which no part of TruthID does today.

What that costs in ETH: at the ~0.011 gwei gas price observed during the mainnet deploy, the heaviest operation in this table (registerDevice, ~195k gas) comes out to roughly 0.0000021 ETH — a small fraction of a cent. TruthIDAccountFactory.createAccount's first-deploy row is heavier still (it deploys a whole contract via CREATE2, not just a state update) — see Smart Account & Gas → Cost for that conversion. Gas price moves with network demand; check Base's live gas tracker for the current rate before assuming these numbers hold exactly.

Audit status

See Security Model → Audit status for the manual review findings and what's not yet covered by a third-party audit.

Next steps

• How TruthID Works — the protocol walkthrough behind these functions
• Smart Account & Gas — how the ERC-4337 account works, setup flow, and funding
• Security Model — threat model and what TruthID does and doesn't protect against
• SDK Reference — the typed, documented way to call these contracts from TypeScript, Python, or Ruby