Deployment reference

Updated 21 September 2026. The V3 demo’s Ethereum contracts are deployed on mainnet, chain ID 1. Their deployment and configuration are recorded; the complete customer-wallet journey is still being qualified. Contract deployment is not a public deposit invitation.

Ethereum demo contracts

The recorded source revision is 2a5dffb5847375adc1cbb16d7fa6ba5d950f837c. Index deployment events from block 26027015.

The borrowing asset is mainnet USDC, 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 , with six decimals. The price adapter uses Pyth Lazer verifier 0xACeA761c27A909d4D3895128EBe6370FDE2dF481 .

The eleven contracts are source-verified on Etherscan. Signers, the vault construction and the liquidator are configured, and a verified price update has succeeded. The new pool received an initial 50 USDC liquidity supply. Read available liquidity and price freshness when integrating; the seed amount is not a live balance.

What this deployment enables

The demo uses capped threshold-attested collateral credit, a static supply counter and the Zest Protocol lending pool. It does not have the production SPV adapter, collateral facade or flash-settlement liquidity system wired as deployed components. Construction registry entry 1 carries the V2 schema; the entry number is not the architecture version.

The recorded administration is a deployer EOA, with a 2-of-3 member contribution threshold. Independent production governance and service hosting remain separate rollout requirements. The configured Bitcoin side is mainnet; local regtest deployments use their own generated addresses.

Verify the release you connect to

Use the confirmed deployment manifest  for addresses, contract source revision and start block. The Etherscan links above provide verified source and transaction history. Runtime bytecode was compared against the release build outside constructor immutables; verify configuration and constructor values when integrating.

Backend services can be updated independently of the contracts. This release requires matching backend and wallet integration, including customer-authorized preparation and withdrawals that identify the specific vault output. See the V3 mainnet configuration bundle ; confirm the hosted service revision before enabling the wallet flow.

Bitcoin vault addresses

Bitcoin has no shared Zest Protocol deposit address. Each vault is derived from the construction, customer key and position-bound oracle commitments. Obtain and verify the address for your own position through the supported flow.

After a partial withdrawal or liquidation, follow the new Bitcoin output and its replacement coverage. See Verify your position and Demo status.