3Jane Docs | Contract Addresses
Verify before you sign, integrate or index.
Contract addresses are security-critical. This static documentation intentionally does not invent or freeze addresses that have not been verified from the current deployment manifest. Integrators should validate every address against the live application, official deployment records and the correct Ethereum network context.
Verification workflow
Start from the current app or official deployment record, confirm chain ID, compare the full hexadecimal address, inspect verified contract code where available and confirm the expected token symbol and implementation. Do not trust a search snippet, screenshot or truncated wallet label as an address source.
Address categories
A complete deployment reference can include USD3, sUSD3, vault or staking contracts, LCC components, reward distributors, configuration contracts and approved asset addresses. Each should be labeled by role rather than presented as an unexplained list.
| Category | Verification focus |
|---|---|
| Token / vault | Symbol, decimals, ERC-4626 behavior |
| Rewards | Emission / claim role |
| Config | Admin / upgrade permissions |
| LCC | Margin, promise and call roles |
| External asset | Canonical token deployment |
Upgrade awareness
A proxy address can stay constant while implementation code changes. Security monitoring should therefore track both proxy and implementation state, plus upgrade authority and event history where relevant.
For frontend developers
Keep addresses in one deployment manifest, validate chain before enabling actions, and fail closed if the selected network does not match. Never silently substitute an address based only on token symbol.
Protocol mechanics are documented for education and integration context. Current rates, caps, emissions, eligibility and transaction parameters should be verified in the live 3Jane interface before acting.

