Vault · Supra Mainnet (chain 8)

Custody, verifiable.

Every security deposit, every limit, every peg — read live from mainnet view functions, in three clearly separated sections.

1

Maker security deposits — operators K1 & M2

Checking invariant…

Held in the maker vault; movable only through maker_vault entry functions. This section shows the RFQ maker side only — compute providers are section 2.

The bar is the live wCOSMO held in the vault, split by which operator deposited it. Operator K1 runs autonomously — see its live quoting activity.

2

Compute provider security deposits

Checking invariant…

A separate vault with its own custody account — providers place deposits to become eligible for compute jobs. Not related to the maker vault above.

Place your security deposit
3

wCOSMO reserve — 1:1 backing

Every wCOSMO is backed by exactly one $COSMO held in the reserve. This backs the ENTIRE supply — including both vaults above — and is not a security deposit itself.

About wCOSMO

No private key exists for either custody account; movements are only possible through the vaults' entry functions.

Maker vault (section 1):
Module: 0xf2785bf6510d738d2f58c48ee62f00ec56462a5bf0de4ccfdebd11cd2b1264e1::maker_vault
Custody account: 0x04830c9b762bf0e00d2620026eb172426c686bc8b04a9c350f004482fa1fd54f
Provider vault (section 2):
Module: 0x0fd8940dadb96ec354d200fcc73e7b10889b5968a8aabe4caf106ee25d8003c0::provider_vault
Custody account: 0x76f115fcea64253ec60633c0cf197db38978822fae4af9cface9d88bf39bd576
wCOSMO FA: 0x4799c7cc256a0cb38d28847eae42be5caf5f21e5272a4d3eef52965c1d00cff6