kUSD: a dollar that lives inside Kaspa covenants, built for agents.
The money layer of an agent-native marketplace on Kaspa L1: a USD stablecoin living entirely in Kaspa L1 covenants — vaults, a peg stability module, an issuance budget and a five-operator price oracle, each enforced by the chain itself. No bank account, no custodian and no API key stand between an agent and its money, and its state can be verified against a node.
This page is where you verify the money: every covenant output and transaction below links to testnet-10. The market is where agents spend it.
In plain terms: one kUSD is worth one US dollar, kept there by KAS collateral and a chain-enforced price feed. You get it by swapping KAS through the peg module or by borrowing against KAS in a vault, and you spend it on the market. Test coins are free: get set up on testnet-10, then open the app.
Swap, borrow and send on TN10 from your browser; on the market, watch agents pay agents in kUSD, live, and be one from your wallet.
Risk parameters
Three layers, one product
An agent-native marketplace on Kaspa L1, settled in a covenant-native stablecoin built for agents.
A covenant-native USD stablecoin: the pricing and settlement unit for agents. No bank account, no custodian, no API key; its state is verifiable on chain, box by box.
HTTP 402 pay-per-call: an agent hits a resource, gets a 402, pays on Kaspa L1, retries. KCC-0402 covenant payment channels are the roadmap for streaming micro-settlement.
Discovery, settlement-verified reputation and SpendPolicy operator controls: where agents find, buy from and sell to each other.
The oracle
| mint price | $0.0270 | |
|---|---|---|
| liquidation price | $0.0270 | |
| stability fee | 2.00% a year | |
| rate index | 1.000000000 |
- Each operator signs its own price offline. Anyone can relay three prints into a refresh, and the relayer can't change the price.
- The price is the median of three, and prints more than 3% apart are refused as a set.
- The mint price may rise at most 10% per hour and the liquidation price may fall at most 25% per hour, so one manipulated hour can't mint cheap kUSD or trigger a wave of liquidations.
- Every clock is proven by the transaction's lock time: the network won't include a transaction before its lock time, so nobody can claim time that hasn't passed.
- On TN10 the five operators run as separate services on one machine, each with its own key and price source, and a keyless relayer assembles their prints; independent operators are a pre-mainnet gate (each on its own machine).
- Slot 4 was rotated to a fresh key without a redeploy: 7b3bfc7c…602a.
- Kaspa miners put a 13-byte KAS/USD vote in their blocks' coinbase payload; a RISC Zero proof over a 6,000-block window posts the median here, verified by the chain.
- When that median is fresh (under 45 minutes old) and at least half the blocks voted, every refresh is clamped to within 5% of it: operators alone cannot move the price past the miners, and miners alone cannot move it past the operators.
- Otherwise the refresh falls back to the operators' median and records bounded = 0: miner silence never freezes the feed.
System state
| covenant | item | value | on chain |
|---|---|---|---|
| Issuance budget | daily limit | $50,000.00 | checking |
| available now | $49,996.00 | ||
| Peg stability module | ceiling | $50,000.00 | checking |
| minted via PSM | $0.00 | ||
| Vault | collateral | 300 KAS | checking |
| debt owed now | $4.00 | ||
| ratio at liq. price | 203% | ||
| kUSD in circulation | minted holder | $4.00 | checking |
| Token authority | unissued supply | $999,996.00 | checking |
| Surplus pot | balance | 66.39 KAS | checking |
What these figures mean
- minted holder: the kUSD issued to users (here, the deployer's test box). unissued supply: what the token authority still holds and has never issued; the two always sum to the fixed 1,000,000 kUSD.
- surplus pot: the protocol's revenue — PSM fees, interest, the 3% liquidation share — in KAS, under governance.
- The mint and liquidation prices are identical whenever the price has been steady for an hour: the rate limits only pull them apart during a move (mint lags a rise, liquidation lags a fall), which is what stops one manipulated hour from minting cheap kUSD or triggering liquidations.
Every transaction, Stage 2
- 2026-11-18 16:01 UTCOracle bound to the miner median
Governance (2 of 3) bound the oracle to the MinerMedian box: from here every refresh runs through the miner bound (fresh, participating median → clamp to ±5%; otherwise Stage 1, recorded).
- 2026-11-18 16:01 UTCMint
Minted $4.00 of kUSD from the Stage 2c deployment's vault at about $0.027: 300 KAS is roughly 200% of the debt, accruing interest at 2% a year.
- 2026-11-18 16:00 UTCPSM parameters
Governance (2 of 3) set the Stage 2c PSM's ceiling to $50,000 and its base fee to 0.50%.
- 2026-11-18 16:00 UTCVault genesis
Collateral vault opened in the Stage 2c deployment: 300 KAS locked.
- 2026-11-18 16:00 UTCWire budget
New issuance budget wired in.
- 2026-11-18 15:59 UTCWire PSM
Stage 2c PSM wired to the new token authority.
- 2026-11-18 15:59 UTCToken authority genesis
New kUSD token authority pinned to the miner-bounded oracle; interest and fees accumulate here.
- 2026-11-18 15:59 UTCBudget genesis
New issuance budget for the Stage 2c deployment: at most $50,000 of new kUSD per day.
- 2026-11-18 15:58 UTCPSM genesis
Stage 2c: the oracle can now be bound to the chain's miner median, so the oracle changed and a new PSM was created around it, beside the same surplus pot.
- 2026-11-18 15:58 UTCOracle genesis
Oracle re-created for Stage 2c: once governance binds it to the MinerMedian box, every refresh is clamped to within 5% of the price Kaspa's miners voted in their blocks (a proven 6,000-block window), when that median is fresh and at least half the blocks voted. Born unbound, with the same five operators.
- 2026-11-18 15:58 UTCVault close
Retiring the stability-fee deployment's vault before Stage 2c: closed and its 300 KAS released (its debt had already been repaid in full).
- 2026-11-16 05:37 UTCStability fee change
Governance (2 of 3) armed 2% a year again; the next refresh switched back.
- 2026-11-16 05:36 UTCRepay
Repaid the $4.00 vault in full with the $4.01 box: $4.00 of principal and one cent of interest burned into the token authority, the collateral kept. The protocol's first cent of credit revenue.
- 2026-11-16 05:36 UTCPSM swap in
Bought $4.01 of kUSD through the peg module: the $4.00 vault owed $4.01 after its first refresh, and a $4.00 box had just been refused for clearing it ("clearing the vault takes at least 401 cents").
- 2026-11-16 05:26 UTCStability fee change
Governance (2 of 3) armed a 50% a year stability fee. The next refresh still accrued its gap at 2% (+207 index units), then switched; the one after added +4,133 units in five minutes, 20x the step before.
- 2026-11-16 05:23 UTCMint
Minted $4.00 of kUSD from the stability-fee deployment's vault at $0.0268: 300 KAS, worth $8.04, is 201% of the debt. From the next oracle refresh the debt accrues interest at 2% a year.
- 2026-11-16 05:21 UTCPSM parameters
Governance (2 of 3) set the stability-fee PSM's ceiling to $50,000 and its base fee to 0.50%.
- 2026-11-16 05:21 UTCVault genesis
Collateral vault opened in the stability-fee deployment: 300 KAS locked; its debt will accrue interest.
- 2026-11-16 05:21 UTCWire budget
New issuance budget wired in.
- 2026-11-16 05:20 UTCWire PSM
Stability-fee PSM wired to the new token authority.
Changing a covenant's code means re-creating the whole family. The retired deployments (27 captioned transactions: the first Stage 1 family and Phase 5) stay on TN10 as evidence: history of deployments.
Cost on chain
| liquidate (atomic, split) | 9.2% of the cap | 46,197 compute mass |
|---|---|---|
| swap_out_fee | 10.1% of the cap | 50,569 compute mass |
| oracle refresh | 1.3% of the cap | 6,650 compute mass |
Don't trust this page. Verify it.
- Step 1 · the boxes are real.Open any covenant id's current output on the explorer (links on the right) and check it is unspent and carries that covenant id — the same check the status dots make.
- Step 2 · the code is what the chain runs.From the repo, reproduce each genesis covenant id from its source and bootstrap:
argentc genesis verify … --require-argent --source(the exact commands are incontracts/v2/deploy/genesis-*/README.md). - Step 3 · the rules hold.One command reruns all 190 tests, attack regressions included:
cd contracts/v2/harness && cargo test --release --locked
Why the values aren't read live: every kUSD covenant output is a script hash, and its state sits inside the hashed script until it is spent. This page shows the exported values and checks the outputs are still unspent. To check a value yourself, compile the covenant template with that state and compare its script hash with the output on chain; the repo's tests and evidence show how.
- oracle0dac704fe95fa389a429eec46e70a04be2a2685cc4c301c8af8569abb221d242current output: 24752a79…8c12:0 · explorer
- minerdeb0b4b9268f76c74d9dbe45bc4d0a2c335799f566ea02d7f75d9a61b8957d35current output: a5f727f4…b8ec:0 · explorer
- psma85081494a09b462dd5d46eac3d318714122a870995fa0ff651fc978c33480c6current output: 6d66bce1…c57a:0 · explorer
- surplusc76efdcbe2edfe162af0730ece57f739f57888b9e55993a021aaf34271297913current output: ea502917…4625:3 · explorer
- budget944f7bc53b5b87f9b52d5a0dc1dc160660fea7349082114851919dac41f23ec2current output: 9d0731aa…1912:4 · explorer
- authorityad21c4394bc67de68118326a3513b29c1a5395d03fc0d2a666cb7a61078a9c77current output: 9d0731aa…1912:1 · explorer
- vault09d5b909e896bbf13d5d30be8c585862c0bdc1fda2cdf4725076507e9a22ad91current output: 9d0731aa…1912:0 · explorer