Skip to content
IcebergDocs
Transparency

Status, pool & addresses

What is implemented, what is configured separately, and what does not exist yet.

Updated 8 September 20262 min read
On this page

Current implementation status

This page is a dated product record, not live uptime monitoring. It describes the code and configuration requirements reviewed on 8 September 2026.

AreaCurrent state
Sign-in and owned-account accessImplemented with Privy and server-side ownership checks
Simulated trading and analyticsImplemented for provisioned accounts; simulation must be enabled
Native-USDC checkoutImplemented; receiver setup and explicit production activation remain required
Payout requests and cancellationImplemented with immutable reserve/refund accounting
Operator approvalServer-only helper; disabled by default and requires a funding reference
Approved-credit purchasesImplemented at 90% of the regular account fee; requires approved credit
USDC wallet payoutsTreasury signing and transfers are not activated
Public payout-pool contractPlanned; no deployment or address is confirmed

The intended payout pool

The project model puts account access fees into a transparent payout pool and allocates 80% of eligible gross claims to traders and 20% to Iceberg. A public smart-contract pool is the intended direction.

The current application has a direct-receiver checkout and a server payout-request ledger. It does not yet deploy the proposed pool or route payouts through it. There is no published on-chain reserve balance, automated solvency proof or contract audit to cite for that future pool.

Public address registry

ItemAddress / referenceMeaning
Iceberg payout-pool contractTBD · not deployedNo contract address or explorer link is available
Treasury payout walletTBD · not publishedSigning and wallet payout execution are not activated
Production checkout recipientTBD · configured in the app invoiceNever infer it from the USDC token address
Pool audit reportTBD · not publishedNo audit or audit guarantee is claimed
Native-USDC token contractsSee supported networksExisting token contracts, not Iceberg pool or recipient addresses

The supported token addresses are listed in USDC checkout. A placeholder is not a destination. Only a valid enabled invoice can provide the recipient for a purchase.

What this release does not claim

  • No real Hyperliquid order submission, exact exchange queue replication or guaranteed stop execution.
  • No proof that simulated account equity is backed one-for-one by an on-chain account balance.
  • No activated wallet payout transfers, deployed public pool, pool audit or automated proof of solvency.
  • No guaranteed returns or proven concurrent-user capacity.
  • No TradingView Advanced Charts license or complete Hyperliquid drawing-toolbar parity for the current custom overlay.

Work required before wallet payouts

Treasury custody and signing, solvency controls, operational review, transfer execution, receipt reconciliation and public reporting must be completed before wallet payments are activated. A funding reference entered during approval is an operator attestation, not an automated on-chain receipt check.