Konnex is a robot‑native network where every task, escrow, penalty, and reward settles in stablecoins by default. Stablecoins provide a predictable payment rail for machine commerce, while KNX remains the network token for validator security, governance, and fees.
Stablecoin‑Native Flow (overview)
Stablecoin settlement flow
The flow shows:
Payer tops up (optionally via card on‑/off‑ramp) and locks stablecoins into the task escrow.
Executor submits PoPW evidence to Validators; a ScoreRoot is posted.
Escrow settles: payouts or refunds (and penalties) are released; a small fee can be routed to a treasury/buyback in KNX.
Role Split: Stablecoins vs KNX
Stablecoins — settlement currency for escrows, payouts, penalties; supports fiat on/off‑ramps and cross‑chain liquidity.
KNX — staking, governance, and network fees; a small fee from stablecoin flows is auto‑swapped to KNX (buyback/treasury).
Contract Settlement Types (Stablecoin‑Native)
Fixed‑price — escrow a single stablecoin amount and release on success.
Metered — usage‑based debits (seconds, meters, frames) from escrow.
Milestone — staged stablecoin releases across checkpoints.
Prove — submit PoPW bundle referencing JobID and deadline.
Verify — validators publish a ScoreRoot (pass/fail + metrics).
Settle — on pass, release stablecoins; on fail, apply penaltyStable and refunds (fees in KNX).
Multi‑Token Staking & Robotic Bonds
KNX stake — aligns executors with validator security and enables slashing.
Stablecoin bond — compensates counterparties for non‑performance.
Third‑party stakers can supply stablecoins to robotic bond pools and earn yield, with risk priced by reputation. Required stablecoin stake roughly scales as S = kappa / sqrt(T) where T is trust score.
Cross‑Chain Liquidity
Stablecoins from other chains can be bridged into Konnex via approved routes. Tasks are chain‑agnostic to source funds.
Card On/Off‑Ramp
Charge — pay with card in app.
Mint — processor converts fiat to stablecoins to the payer’s Konnex address.
Escrow — stablecoins locked in the task contract.
Payout — after PoPW verification, stablecoins are released.
Redeem/Spend — spend via card, redeem to bank, or reuse on‑chain.
Compliance by Design
Optional KYC/AML gates (market/DAO configurable).
Full audit trail of packets, PoPW, and stablecoin flows.
Developer Surface (API Sketch)
lock(jobId, rewardStable, stakeStable)
prove(jobId, PoPWBundleRef)
settle(jobId)
bond(jobId, amountStable)
Economics & Fee Flywheel
Stablecoins for users, KNX for the network.
Auto‑buyback: small fee on stablecoin flows swaps to KNX for treasury/burn.
Key Metrics
Latency: prove → stablecoin release (target single‑block after validation).
Disputes: <1% and auto‑resolved.
Velocity: avg stablecoin tx/robot/day.
Card share: tasks funded via on‑ramp.
Collateral efficiency: required stakeStable falls as trust T rises.
bond(jobId, amount) — third‑party stakers add stablecoin bonds that secure execution and earn yield on pass.
prove(jobId, proofRef) — executor posts a PoPW bundle reference before deadline.
debitMetered(jobId, amount) — optional usage‑based debits for metered contracts.
settle(jobId) — reads validator decision from IScoreRegistry, applies penalties or releases funds, sends a stablecoin fee to FeeCollector for KNX buyback/treasury.
The FeeCollector is a simple stablecoin sink. Teams typically wire this to a swap/buyback executor off‑chain or via per‑chain router adapters.
To add milestones, track uint256[] milestoneAmounts and a checkpoint index per job, and debit per milestone similarly to debitMetered.