Smart contract components
For proxy contracts, distinguish the address users call from the implementation address. The deployment specification provides the network, version, and ABI, together with permissions, price feed connections, and change policies.
Official product materials
Each material identifies the product, version, effective date, and original source link. Transactions use official information for that release. Configuration examples in the source code do not replace product addresses.
Release registry and ABIs
Release integrations package deployment information for each product and network in a machine-readable manifest with the corresponding ABIs. Official mainnet values and deployment file paths will be finalized at release. The following are integration inputs to include in those materials. Registries from the public verification environment and generated artifacts are not mainnet release materials.
Partners map manifest values to their local configuration and load the full ABIs. Use the Developer Quickstart for a configuration example and deposit and redemption completion checks. This input template does not replace a finalized official manifest schema or actual release addresses.
Supported features and version changes
The feature matrix for each product records supported, unsupported, and suspended routes, together with their calls, events, pricing, and token treatment. Until the release versions and ABIs for ArcoUSD, Savings, Funds, and OTC are finalized, the public deposit and redemption functions should not be treated as the execution interface for each product.
Release change records connect the previous and new versions, effective time, affected products and networks, required partner actions, and revalidation scope. Determine compatibility from the actual changes, rather than from the document version alone.
Public source code on GitHub
LBMike/arco-giwa is the public repository. The links below are pinned to source version 8160f354 to provide a consistent implementation reference. The public source explains structure and behavior. Use the relevant release specification for a mainnet product’s official deployment and ABIs.
Generate full ABIs using the relevant source version and the contract package’s build configuration. Partner integrations use ABIs matching the product’s official deployment, rather than an arbitrary generated artifact.
Security materials and licenses
Read security reports together with their target code, deployment, version, review scope, and handling of findings. Audits of the underlying code, verification of external underlying products, and security reviews of ARCO vaults each have a distinct scope. The contract package is subject to file-specific license terms, including GPL and MIT. When reusing, modifying, or distributing code, check the relevant files and the license inventory.Product design and the public implementation
Vault Liquidity Architecture and ArcoUSD, Savings, and Funds explain the composition, operation, and settlement design of the mainnet products. Read the public token, deposit, redemption, and pricing interfaces alongside the relevant release specification.
The public DepositVault’s asset receipt and token issuance behavior does not establish that Funds’ arcoUSD burning and treasury withdrawals are executed. Verify calls, states, fees, and token treatment against the relevant release ABI and operating specification.