Vault-minted stablecoin — deposit ETH, mint USDS. $21B supply. Open question: who is the issuer under GENIUS Act?
"The investor's custody account — collateral available, no identity check, permissionless deposit."
User self-custody wallet on Ethereum holds collateral (ETH, WBTC, RWA tokens, etc.) and prepares to lock it in a Sky vault. The protocol is permissionless — no KYC, no whitelist, no identity layer. L4 Account (token balance, approval) and L5 Application (wallet UX, vault interface) are lit. HONESTY MARKER: D1 (Identity) is technically required by GENIUS Act and BSA, but Sky Protocol enforcement is absent. The protocol cannot identify users, cannot freeze addresses. Compliance is structurally absent at the protocol level.
"Real-time collateral appraisal — determines how much USDS the vault owner can mint against locked collateral."
Chainlink oracle (primary) + Sky in-house oracle determine collateral value. For ETH vaults, the minimum collateral ratio is enforced at 150%: if collateral drops 40% below entry price, the vault becomes underwater. Oracle price feed is global, code-enforced. L3 Execution layer: smart contract reads oracle, calculates available USDS minting capacity. No jurisdiction sensitivity; oracle is neutral market data.
"Vault issuance — collateral is locked, USDS is minted into existence. Stability fee accrues in real time."
User creates a vault smart contract instance, locks collateral (ETH, WBTC, RWA tokens), and mints USDS. The protocol enforces minimum 150% collateral ratio (for ETH) — if user tries to mint more USDS than collateral supports, the transaction reverts. Stability fee (interest rate set by SKY governance) accrues immediately on minted USDS. No human counterparty — user interacts directly with smart contract. HONESTY MARKER: Under GENIUS Act and BSA, who is the 'issuer' of USDS? Sky Protocol has no legal entity. The protocol itself IS the issuer. This is the existential regulatory question for decentralized stablecoins: how do you regulate an issuer that is code?
"Automated collateral seizure — vault is auctioned if collateral ratio drops below 150%."
Continuous oracle monitoring of collateral ratio. If collateral value drops such that (collateral ÷ USDS debt) < 1.5, the vault is eligible for liquidation. Any liquidator bot can trigger a Dutch auction: the vault's collateral is offered at declining prices until a buyer emerges. Liquidation fee (typically 13% of seized collateral) is deducted; remainder is returned to vault owner. This is permissionless and code-enforced — no discretion, no governance intervention, no human approval. OPEN QUESTION: who bears loss if the liquidation yield is insufficient? Who is liable? No legal framework exists for protocol-level liquidation. This is the existential risk gap in decentralized finance.
"USDS in the wild — freely transferable, no restrictions, no freeze capability."
Minted USDS is freely transferable to any Ethereum address. Unlike USDC (which Circle can freeze per law enforcement orders), USDS cannot be frozen. This is by design: the protocol has no pause mechanism, no freeze switch. HONESTY MARKER: USDS cannot comply with law enforcement asset freeze orders. This is the core regulatory tension: a stablecoin is only useful if it's truly stable and transferable. But stability requires backing (collateral + liquidation engine), and transferability requires freedom from freeze. Sky chose transferability over compliance. The consequence: USDS is non-compliant with sanctions and asset recovery law. Recordkeeping is the on-chain transaction receipt (D11); no traditional AML alert or CTR filing.
Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.
Coverage notes: 5 disclosed gap(s).
Interactive exploration of compliance depth: purpose-built stablechains (Arc, Tempo) vs general-purpose chains (Ethereum, Solana).
COMPLIANCE DEPTH THESIS
Circle's Arc embeds compliance mechanisms from L2 Consensus upward. Malachite BFT uses a permissioned validator set — participation requires Circle approval. At L3, confidential transfers shield amounts via TEE while regulatory view keys allow selective disclosure. CCTP v2 at L4 is Circle-native. The result: 4 of 6 blocks are code-enforced, and compliance reaches all the way to the consensus layer.
A-301 · ARC SECTION CUT