Overview

Sova’s architecture is composed of tightly integrated modules that together provide a Bitcoin-anchored execution environment. Each module performs a specialized role—some on-chain, some off-chain—but all share a single invariant:

Sova state is valid only if it matches Bitcoin state.

This section breaks down the major components of the chain, how they interact, and what responsibilities each carries within the broader network. It can be used as a more in-depth reference at the module level as compares to the Architecture section.

---

Component Map

Category	Component	Purpose
Canonical Asset	sovaBTC	The 1:1 Bitcoin-backed token used across the network.
Execution Runtime	SovaEVM (sova-reth)	Executes smart-contract logic and enforces Bitcoin-linked storage locks.
Consensus Client	op-node	Sequences transactions, embeds Bitcoin anchors, and maintains rollup state.
Finality Services	Sentinel + Signing Service + Bitcoin Core	Verify Bitcoin confirmations, manage locks, and broadcast withdrawals.
Governance Contracts	Network Params + Treasury + Validator Registry	Parameter management, upgrade authority, and economic alignment.

All of these components form a closed verification loop: Bitcoin → Sentinel → EVM → Consensus → Bitcoin.

---

sovaBTC — Canonical Asset Layer

sovaBTC is the canonical representation of Bitcoin on the Sova Network. It is minted when a valid Bitcoin transaction is confirmed and burned when BTC is redeemed on L1.

Key Properties

• 1:1 Backing: Each sovaBTC corresponds to a specific Bitcoin UTXO tracked by Sentinel.

• Bridgeless: No custodians or multisig signers control minting. Validation is deterministic.

• Native to SovaEVM: Implements ERC-20 Upgradeable for compatibility with existing DeFi contracts.

• Auditable: Mint and burn events include the Bitcoin txid and block hash for on-chain traceability.

Lifecycle

1. User sends BTC → Validator detects via Bitcoin Core.

2. Sentinel locks state → after 6 confirmations, EVM mints sovaBTC.

3. sovaBTC can be used in DeFi protocols or institutional vaults.

4. User burns sovaBTC → Signing Service creates and broadcasts BTC transaction.

5. Sentinel confirms and marks the UTXO as spent.

This mechanism produces a self-auditing, bridgeless Bitcoin derivative that retains full composability in the EVM.

---

SovaEVM Modules

Beyond standard EVM opcodes, SovaEVM introduces specialized modules:

• Inspector: Intercepts SSTORE writes to manage Bitcoin-linked state locks.

• Sentinel Interface: Communicates confirmation data to and from the off-chain Sentinel.

• Precompiles: Provide low-level Bitcoin functions (sendrawtransaction, decoderawtransaction, convertaddress).

• Anchor Verifier: Validates Bitcoin block headers against local Bitcoin Core.

Each module works in tandem to enforce finality and enable native Bitcoin logic within smart contracts.

---

Sentinel and Signing Service

These off-chain components bridge the EVM and Bitcoin Core without introducing custody risk.

• Sentinel: Tracks Bitcoin transaction confirmations and maintains lock state.

• Signing Service: Generates withdrawal transactions on Bitcoin L1 after sovaBTC burns.

• Audit Interface: Exposes APIs for external verification and regulatory reporting.

Together they enforce the rule that no state on Sova is final until Bitcoin says it is.

---

Governance and Network Params

Sova’s governance contracts handle upgrades and economic coordination while preserving core immutability.

Core Contracts

• NetworkParams.sol: Stores configurable variables (e.g., confirmation thresholds, fee rates).

• ValidatorRegistry.sol: Tracks authorized sequencers and validators.

• Treasury.sol: Collects fees and funds buybacks for the $SOVA token.

• UpgradeManager.sol: Controls protocol updates through a multi-sig or DAO process.

Governance cannot alter the core security invariants — Bitcoin anchoring and finality rules are hard-coded at the protocol level.

---

Component Interactions

        +----------------------+
        |    Bitcoin  L1       |
        +----------+-----------+
                   |
                   v
        +----------+-----------+
        |   Sentinel Service   |
        | (tx tracking, locks) |
        +----------+-----------+
                   |
                   v
        +----------+-----------+
        |   SovaEVM (sova-reth)|
        | (Inspector, Precomp.)|
        +----------+-----------+
                   |
                   v
        +----------+-----------+
        |  Consensus Layer     |
        |   (op-node anchor)   |
        +----------+-----------+
                   |
                   v
        +----------+-----------+
        | Governance + Treasury|
        +----------------------+

Each component validates and extends the one below it, creating a self-referential security loop that always terminates in Bitcoin’s proof-of-work.

---

Design Objectives for Components

Objective	Implementation Example
Determinism	Identical state roots across nodes via Bitcoin-verified locks.
Auditability	Public Sentinel logs + on-chain txid linking.
Interoperability	EVM compatibility + Hyperlane messaging.
Scalability	Modular execution and checkpointing via OP Stack.
Institutional Readiness	Qualified custody support through SovaX.

---

In Summary

• sovaBTC anchors all on-chain value to real Bitcoin.

• SovaEVM extends the EVM with Bitcoin-aware execution logic.

• Sentinel and Signing Service bridge confirmation and withdrawal flows trustlessly.

• Governance coordinates upgrades without compromising core security.

• Together they form a closed-loop system for verifiable Bitcoin-denominated finance.

---

Next → sovaBTC Detailed Specification

Learn how sovaBTC functions as the canonical Bitcoin asset within Sova — its minting and burning processes, audit path, and integration with vault protocols