For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Contract Addresses

All Tesseract DCV contracts are deployed on Ethereum mainnet. Each contract is verified on Etherscan — follow the links for source code and ABI downloads.

Compliance contracts

Vault deployers (one per supported asset)

Each deployer creates a new, dedicated vault configured for a specific underlying asset. Call deployVault(...) or deployVaultWithPermit(...) on the deployer for the asset you want to hold.

Vault instances

Every client gets their own vault contract, created when they call a deployer. The address of the new vault is returned by deployVault(...) and emitted in the VaultDeployed event.

Each vault contract is a standard ERC‑4626 share vault — once you have the address, you can interact with it using any ERC‑4626 tooling or the methods listed in the reference.

Reference deployed vault (for ABI inspection and tooling setup):

0xe1c3a197d16eF96a7c8E7c5F6B83B5E032cD76a9 — also viewable in the app at app.tesseract.fi/vault/0xe1c3a197d16ef96a7c8e7c5f6b83b5e032cd76a9.

Use this as a template for wallet-connector configuration, wagmi/viem code generation, or ERC‑4626 interface probing. Functional behavior is identical across all deployed vaults.

Supported assets

Underlying ERC‑20 tokens that Tesseract vaults wrap. Minimum deposits are configured per-deployer and may change — always read the current value from the deployer's minInitialDeposit() view before deploying.