# Confirm your deployment

Establish the exact contracts and configuration before connecting customer funds.

The public materials do not provide a complete, verified production deployment registry. Obtain the deployment pack for your integration during onboarding rather than copying an address from a demo or repository example.

## Deployment pack

| Item | What to verify |
| --- | --- |
| Network | Chain ID, RPC environment and explorer |
| Underlying asset | Token address, symbol and decimals |
| Vault | Address, verified code and source revision |
| Proxy, if used | Implementation, upgrade authority and upgrade procedure |
| Providers | Adapter addresses, underlying markets and entry provider |
| Roles | Admin, executor, timelock and treasury addresses |
| Configuration | Fees, minimum assets, paused actions and timelock delay |
| Indexing | Start block, confirmation policy and expected reporting delay |
| Assurance | Audit scope, remediation revision and changes since review |

Record this information in your deployment configuration with a named owner. Review changes before using a replacement address or implementation.

## Source repositories

The imported source includes the earlier `contracts` implementation and the newer `optimized-rebalancer-contracts` implementation. Their roles and behavior are not interchangeable. The [October 2025 audit](/security/audits/) identifies specific commits in the earlier repository.

For integration development, use the ABI that matches your confirmed deployment. Review the [vault model](/concepts/vaults/) for assets, shares and rounding, then test the transaction flow against the agreed environment.

## What to validate in a trial transaction

Verify the asset allowance, recipient, expected shares, transaction receipt and resulting position. Exercise a small withdrawal, full redemption, rejected signature, insufficient balance and unavailable action. Check both the wallet state and the time at which the transaction becomes visible in reporting.