Developers

Build against explicit deployment records.

The current web console targets the private Arbitrum USDC PoC and keeps deployment config, ABI, readers, estimates and transactions in separate modules.

Run locally

From dapp-new:

python -m http.server 8000

Then open http://localhost:8000/

User entry points

USDC approve to LiquidityManager.
LiquidityManager.deposit(uint256).
LiquidityManager.withdrawWithDeadline(uint256,uint256).
Events for deposit and withdrawal history.

Normal users do not call plugins directly.

PoC addresses

Component	Address
USDC	`0xaf88d065e77c8cC2239327C5EDb3A432268e5831`
LiquidityManager	`0x80fB731B78D2C7180cd22eCF18Dc4243546ce192`
ProxyGeneral	`0xb070303C3634eA404593A87725aaCb18E1d5d9BF`
ValueCalculator	`0x1850e1E37a7a46E74bBDAE5704Afe0C79BCb7c1A`
ProtocolManager	`0x91fEc8f3161504Dd20c2Ed58B8E6003854AC5A8D`

Recorded in arbitrum-usdc-poc-1.json on 14 July 2026; verify live before use

Frontend module boundaries

Config & ABI

Immutable PoC description and minimal callable interfaces.

Readers & estimates

Read-only snapshots and explicitly indicative client-side calculations.

Transactions

Validated approval, deposit, withdrawal and revoke workflows.

Do not copy addresses between deployments. A base-asset deployment is a distinct vault system. Update config from a verified manifest and test every ABI against deployed bytecode.