wCOSMO · Supra Mainnet (chain 8)

wCOSMO — the security-deposit asset

wCOSMO is a plain 1:1 wrapper around $COSMO. Every security deposit in the COSMO system — compute provider deposits and maker operator deposits — is denominated in it. Wrapping and unwrapping are permissionless, and the peg is verifiable on-chain at any time.

What it is

$COSMO itself is a dispatchable fungible asset. wCOSMO is its plain, non-dispatchable 1:1 wrapper: wcosmo::wrap pulls $COSMO into an on-chain reserve and mints the same amount of wCOSMO; unwrap burns wCOSMO and releases $COSMO. There is no admin mint path — wrapping is the only way wCOSMO comes into existence. Both directions are permissionless. 6 decimals on mainnet.

wCOSMO FA: 0x4799c7cc256a0cb38d28847eae42be5caf5f21e5272a4d3eef52965c1d00cff6
$COSMO FA: 0x11188bb79cd956ab6b8ddff06d64f479358b59ddbd2058a41b447cdf21c17ab0
Module: 0xf2785bf6510d738d2f58c48ee62f00ec56462a5bf0de4ccfdebd11cd2b1264e1::wcosmo

Why security deposits live in wCOSMO

Holding deposits and applying penalty deductions needs an asset with plain, hook-free transfer semantics. The dispatchable $COSMO cannot be held by the vaults by construction — they reject dispatchable assets. wCOSMO keeps the economic exposure of $COSMO while giving both vaults — the maker vault (operator deposits) and the separate provider vault (compute deposits) — a predictable settlement surface. If a provider or maker behaves, the deposit comes back out 1:1; on a failure to deliver, a defined penalty deduction goes to the counterparty.

Peg — live, on-chain

Invariant: the $COSMO reserve fully backs the wCOSMO supply. Not a claim — a view function anyone can call.

peg_holds()
—
wCOSMO supply
—
$COSMO reserve
—

Wrap / unwrap

With $COSMO in a StarKey wallet on Supra Mainnet, wrapping is a single transaction: 0xf2785bf6…::wcosmo::wrap(amount). Unwrapping works the same way in reverse at any time — as long as the wCOSMO is not currently placed as a security deposit.

If you are onboarding as a compute provider, the deposit helper builds the conversion and the deposit as two separate transactions, shows each payload in full, and lets you sign both in StarKey:

Place your provider security deposit

Getting $COSMO — the honest part

There is currently no public listing and no DEX pool for $COSMO. The token is held by a small community, and acquisition happens over the counter — you talk to us. That is not a growth hack; it is where a deliberately guarded v1 honestly stands. If you want to participate as a provider or maker, copy the template and reach out through the contact channel on /compute.

COSMO — $COSMO acquisition request (OTC / community)

Wallet (Supra, chain 8): 0x…
Intended use (compute provider security deposit / maker operator security deposit / other): …
Amount of $COSMO I am looking for: …
Background (infra / DePIN / agents / community): …
Contact: …

Compute track

  • · Provider security deposits are denominated in wCOSMO (self-service; the required minimum is read live on the deposit page).
  • · Jobs are paid in the payment asset of the request — wCOSMO, CASH or SUPRA on the current allowlist (V2 multi-asset path).
  • · On a no-delivery, a penalty deduction of 10% of the required deposit goes to the buyer (fixed at accept time).
About the compute market

Maker track (RFQ)

  • · Maker operators place their operator security deposit in wCOSMO.
  • · Quote escrows on the RFQ rail settle in wCOSMO.
  • · Maker onboarding is not self-service — slot 2 is reserved for the first committed external operator and set up together.
About the RFQ rail

Read this before wrapping anything

wCOSMO is infrastructure, not an investment product. Nothing on this page is financial advice, and no yield or price appreciation is promised or implied. The markets that use wCOSMO are deliberately small, guarded v1 systems with low caps; parameters can change through governance. Wrap what you need for a security deposit — not more. Built on Supra.