AGENT ZERO

Kaspa-Native Yield Architecture: A Sovereign Alternative to STRC

Pure Proof-of-Work Digital Credit

Architecture Comparison: Sovereignty vs Complexity

Executive Summary

Michael Saylor's STRC requires a public company (Strategy/MSTR), securities law, brokerage accounts, USD settlement, and monthly dividend cycles to convert Bitcoin appreciation into "digital credit."

This brief proposes three progressively sovereign architectures that achieve the same outcome — high-yield, low-volatility, hourly-claimable credit — using only Kaspa's native primitives: proof-of-work consensus, covenants, Igra EVM, and eventually vProgs. No legal entities. No stocks. No SEC. No banks.

Approach Sovereignty Complexity Yield Source Legal Risk
A. Covenant Treasury High Low Protocol-owned KAS + lending None
B. Igra EVM Credit Layer Medium-High Medium Lending + AMM fees + treasury None
C. vProgs Sovereign Yield Maximum High Verifiable off-chain computation None

The Core Insight: Kaspa Can Replicate the Treasury-Credit Dynamic Natively

How Saylor Does It (Requires TradFi)

BTC held by Strategy (public company)
         ↓
Strategy issues STRC (preferred stock)
         ↓
STRC pays ~ USD dividend monthly11.5%
11.5%
         ↓
Investor holds low-vol "digital credit"

REQUIRES: Company, SEC, brokers, banks, lawyers, transfer agents

How Kaspa Does It (No TradFi)

KAS held by protocol treasury (covenant-locked)
         ↓
Protocol issues yield claim (covenant UTXO)
         ↓
Covenant pays ~X% KAS yield hourly or per-block
         ↓
User holds low-vol "digital credit" claim

REQUIRES: Only code, consensus, and users

The key difference: Strategy is a legal person that can own property. A Kaspa covenant is a script that can enforce rules. By making the "treasury" a covenant rather than a corporation, the entire legal layer vanishes.


Yield Payment Frequency: STRC vs Kaspa Architectures
01
Architecture A: Covenant Treasury (Simplest, Most Secur

Architecture A: Covenant Treasury (Simplest, Most Secure)

A.1 Concept

A protocol treasury holds KAS. Users deposit KAS into a covenant that enforces:
1. Minimum lock duration
2. Hourly accrual rate
3. Principal + yield claimable only by depositor
4. Treasury funds released only to verified yield sources

A.2 How Yield Is Generated (Without STRC)

Source Mechanism Risk
KAS Lending Treasury lends KAS to borrowers against collateral (on Igra money markets) Liquidation risk if collateral falls
AMM Fees Treasury provides KAS/USDC or KAS/BTC liquidity; earns trading fees Impermanent loss
Treasury Bootstrap Founders seed treasury with X KAS; yield subsidized until organic flow covers rate Sustainability risk if organic < target
Restaking (future) KAS restaked via Babylon-like protocols to secure other chains Slashing risk

A.3 Covenant Pseudocode

A.4 Why This Is Legally Nothing

Element Saylor/STR Kaspa Covenant Treasury
Legal entity Strategy Inc. (public company) None
Regulator SEC, FINRA, IRS None
Ownership Share certificates UTXO + private key
Dividend Corporate action in USD Covenant-enforced KAS release
Tax reporting 1099, K-1, cost basis tracking User responsibility; no issuer
Counterparty Strategy, broker, transfer agent PoW consensus only
What user holds Stock (security) Covenant claim on native token

Under the Howey Test:
- Investment of money? ✅ User deposits KAS
- Common enterprise? ❌ No pooled enterprise managed by others; code is public, user controls keys
- Expectation of profits? Arguable
- From efforts of others? ❌ Yield from lending markets + AMMs, not from anyone's marketing/management

This is structurally closer to Aave or Compound than to a fund.


Architecture B: Igra EVM Credit Layer (Medium Complexity, Better UX)

B.1 Concept

Deploy the yield logic on Igra Network (EVM-compatible L2 on Kaspa BlockDAG) for familiar tooling, while anchoring treasury security to Kaspa L1 covenants.

B.2 Structure

┌─────────────────────────────────────────────────────────────┐
│  IGRA NETWORK (EVM Layer)                                   │
│  • Solidity contracts for user deposits, UI, analytics     │
│  • ERC-20 yield token (kCredit) representing claim         │
│  • Lending market integration (Aave-style on Igra)        │
│  • AMM for KAS/stable swaps                                 │
├─────────────────────────────────────────────────────────────┤
│  KASPA L1 (Covenant Anchor)                                 │
│  • Treasury UTXOs locked by covenant script               │
│  • Igra contract can only request release; covenant validates│
│  • ZK proof or multisig required for treasury movement      │
│  • User can always exit via L1 (escape hatch)              │
└─────────────────────────────────────────────────────────────┘

B.3 Yield Sources (Expanded)

Source Igra Integration Native to Kaspa?
Igra lending market Solidity contract, Aave-style Yes (Igra native)
KAS/USDC AMM fees Uniswap V3 fork on Igra Yes (Igra native)
Cross-chain KAS yield Hyperlane to Ethereum/BSC Bridge-dependent
Treasury-directed MEV Bundle submission via Igra sequencer Partial

B.4 Hourly Streaming Implementation

Because Igra uses Kaspa's 1-second blockDAG as sequencer:

User deposits KAS → Igra mints kCredit
         ↓
Every block (1 second): accrual rate updated
         ↓
Every hour (3,600 blocks): claim window opens
         ↓
User claims → Igra contract validates → Kaspa covenant releases KAS
         ↓
User receives KAS on L1 (or keeps as kCredit for compounding)

Streaming granularity: Continuous (per-block) accrual. User can claim every second if desired, but 1-hour minimums reduce gas costs.

B.5 Why Igra Changes the Game

Without Igra With Igra
Build Clarity contracts only Build Solidity + Clarity hybrid
Small Kaspa dev ecosystem Access Ethereum tooling, libraries, auditors
Manual UTXO management Familiar wallet UX (MetaMask-compatible)
No composability Aave, Uniswap, Curve forks possible

Architecture C: vProgs Sovereign Yield (Maximum Sovereignty, Future)

C.1 Concept

vProgs (verifiable programs) enable sovereign, composable applications that post zero-knowledge proofs to Kaspa L1. For yield streaming, this means:

C.2 The "Octave Higher" Implementation

Saylor described doubling dividend frequency as going "an octave higher." vProgs enable this literally:

STRC Frequency Kaspa Covenant Kaspa vProg Streaming
Monthly (12x/year) Hourly (8,760x/year) Every block (31,536,000x/year)
Human-managed record dates Script-enforced unlock ZK-verified continuous accrual
12 taxable events 8,760 taxable events One event: claim, not distribution

C.3 vProg Architecture for Yield

┌─────────────────────────────────────────────────────────────┐
│  OFF-CHAIN: YIELD CALCULATOR vPROG                          │
│                                                              │
│  Inputs:                                                     │
│    • All deposit UTXOs and their lock heights               │
│    • Lending market interest rates (Igra, external)        │
│    • AMM fee revenue                                         │
│    • Treasury reserves                                       │
│                                                              │
│  Computation (off-chain, cheap):                             │
│    • For each user: compute accrued yield per block        │
│    • Aggregate across all yield sources                      │
│    • Generate STARK/SNARK proof of correct calculation     │
│                                                              │
│  Output: ZK proof + state root posted to Kaspa L1          │
└─────────────────────────────────────────────────────────────┘
                              ↓
┌─────────────────────────────────────────────────────────────┐
│  KASPA L1: COVENANT VERIFIER                                │
│                                                              │
│  • Receives ZK proof                                       │
│  • Verifies proof via ZK opcode (post-Toccata)              │
│  • If valid: permits UTXO spend up to verified amount       │
│  • If invalid: rejects spend, slashing vProg bond          │
└─────────────────────────────────────────────────────────────┘

C.4 Why vProgs Are the Endgame

Feature Covenant Only vProgs
Computation location On-chain (limited) Off-chain (unlimited)
Verification cost Linear with users Constant (ZK proof size)
Cross-vProg composability Manual Atomic reads
Privacy None Selective (ZK hides intermediate state)
Scalability UTXO bloat State roots compress history
Sovereignty User controls UTXO User controls vProg instance

Required Intermediaries: TradFi vs Kaspa Native
02
Comparative Analysis: Kaspa vs. Saylor's Model

Comparative Analysis: Kaspa vs. Saylor's Model

Security Model

Dimension Strategy/STRC (Bitcoin) Kaspa Covenant Treasury
Base consensus Bitcoin PoW (excellent) Kaspa BlockDAG PoW (1s blocks)
Yield layer Corporate equity (STRC) — TradFi Covenant script — consensus-native
Counterparty Strategy Inc. (single company) None (decentralized code)
Regulatory target SEC-regulated public company No entity to regulate
Censorship resistance Moderate (company can be pressured) High (no central operator)
Speed Monthly dividend Hourly or per-block
Composability None (isolated stock) Native (DeFi integratable)

Yield Sustainability

Source Saylor (STRC) Kaspa Treasury
Underlying appreciation BTC price (volatile, historically +38% ARR) KAS price (volatile, newer asset)
Yield mechanism Corporate dividend (board-declared) Market-driven (lending rates + AMM fees)
Hard floor $0 (Strategy could fail) Treasury reserves + liquidation cascades
Yield sustainability Tied to BTC performance + Strategy's ability to issue more STRC Tied to Kaspa DeFi adoption + treasury health

Honest Assessment

Kaspa Advantage Kaspa Disadvantage
No legal entity, no SEC, no banks KAS lacks BTC's store-of-value track record
Hourly granularity natively Yield sources are nascent (lending markets early)
Censorship-resistant by design Smaller ecosystem, fewer integrations
Composable with DeFi Requires bootstrapping liquidity
User self-custody always User bears all smart contract risk

The "More Lucrative" Claim: How Kaspa Can Beat 11.5%

Saylor's is limited by11.5%
11.5%
1. Corporate conservatism — Strategy targets sub- vol, compressing yield2%
2%
  1. SEC disclosure requirements — limits leverage and product complexity
  2. Monthly frequency — capital inefficiency between record dates
  3. Single asset backing — only BTC
Kaspa can target higher yields (15–) by25%
25%
Mechanism How Target Yield Boost
Leveraged lending Treasury collateral loops (deposit → borrow → redeposit) +5–10%
Multi-asset treasury KAS + BTC + stables (via wrapped assets) +3–5% diversification
AMM concentrated liquidity Treasury LP positions in high-fee tiers +2–4%
Restaking Secure multiple chains with same KAS capital +5–15%
Streaming capital efficiency No idle capital between record dates; always earning +1–2% vs. monthly

Important: Higher yield = higher risk. Kaspa's model is more aggressive and less battle-tested than Strategy's.


Implementation Roadmap

Phase 1: Covenant Bootstrap (Now — Q2 2026)

Fixed rate (e.g., APY), hourly accrual8%
8%

Phase 2: Igra Integration (Q3–Q4 2026)

Phase 3: vProgs Migration (2027+)


Feature Capability: Covenant vs vProgs
03
Appendix: Kaspa Technical Primitives Reference

Appendix: Kaspa Technical Primitives Reference

Primitive Status Use in Yield Architecture
Covenants++ (Toccata) Hard fork May 2026 Lock, accrue, and release KAS by time/rules
vProgs Research / testnet Off-chain yield calculation with ZK verification
Igra mainnet Live EVM-compatible execution, DeFi composability
Igra Hyperlane Deployed Cross-chain messaging (Ethereum/Base ↔ Kaspa)
ZK opcodes Post-Toccata roadmap Verify vProg proofs on L1
BlockDAG 1s blocks Live Granular accrual, responsive claims

Conclusion

Saylor's STRC is a brilliant TradFi invention — it proves the world wants Bitcoin-backed yield. But it is fundamentally constrained by the corporate wrapper required to hold property, issue securities, and distribute dividends in a regulated system.

Kaspa offers an escape from this wrapper. Covenants replace articles of incorporation. PoW replaces board governance. Per-block accrual replaces monthly record dates. Native composability replaces siloed equity.

The trade-off is maturity for sovereignty. Kaspa's yield sources are early. Its ecosystem is smaller. But its architecture is structurally superior for the endgame Saylor himself described: a billion people, streaming yield, 24/7/365, with no counterparty but the protocol itself.


The entire apparatus of securities law exists to enforce rules—but Kaspa's covenants enforce identical rules through code alone, eliminating corporations, regulators, and banks. Strategy is a legal person that owns property; a covenant is a script that enforces terms. The revolution isn't escaping the system but realizing the system's function requires none of the system.
Haiku Artwork
Covenants replaceCorporations enforcingCode is sovereign