Compute Provider Security Deposit
To take compute jobs you place a refundable security deposit in wCOSMO. If a job is not delivered, a penalty deduction of 10% of the required deposit goes to the buyer. Setting it up takes two separate transactions: first convert $COSMO into wCOSMO, then deposit the wCOSMO as your security. Signing happens exclusively in StarKey.
Your security deposit
- Required minimum
- —
- Deposited by you
- — connect wallet
- Still missing
- — connect wallet
- wCOSMO in your wallet
- — connect wallet
All on-chain parameters (read-only)
Deposit amount
Amount of wCOSMO to deposit as your provider security (default: the live required minimum).
Step 1 of 2 — Convert $COSMO into wCOSMO (separate transaction)
Converts $COSMO into the same amount of wCOSMO in your wallet. Nothing is deposited yet.
wcosmo::wrap(u64:<amount>)
Step 2 of 2 — Deposit wCOSMO as your security (separate transaction)
Moves the wCOSMO from your wallet into the provider vault as your security deposit.
provider_vault::deposit_provider_bond(u64:<amount>)
Enabled once the wallet holds at least the chosen amount in wCOSMO.
Guarded v1 — what the security deposit does and does not do
- · Placing a security deposit makes you eligible; it does not assign you jobs. Jobs start when a buyer accepts a quote for you.
- · Quotes flow through a signed quote path operated by the COSMO team — providers do not price autonomously in v1.
- · One active job per provider (guarded v1 limit).
- · On a no-delivery, a penalty deduction of 10% of the required deposit is paid to the buyer (fixed at accept time).
- · Withdrawing the deposit (`withdraw_provider_bond`) requires the cooldown to have passed and no active job; full exit is always allowed. This page does not offer withdraw in v1.
- · All parameters (required minimum, limits) can change through governance.
No secrets, no server signers, no admin/multisig functions. Read-only status via https://rpc-mainnet.supra.com. Built on Supra. /compute · /wcosmo