System Component Integration

The Sova Network combines multiple layers of infrastructure into a cohesive system for Bitcoin-secured programmability. From user transactions to validator execution and Bitcoin anchoring, each subsystem interlocks precisely, forming a single, verifiable pipeline.

Architectural Overview

Sova integrates five core subsystems:

Layer

Core Components

Purpose

Bitcoin Layer

Bitcoin Core

Provides canonical blockchain data, transaction validation, and broadcasting.

Finality Services

Sentinel, Signing Service

Track Bitcoin transactions, manage storage locks, and broadcast withdrawals.

Execution Layer

sova-reth (Inspector, Precompiles)

Execute EVM transactions, enforce Bitcoin-linked state correctness.

Consensus Layer

op-node

Sequence transactions, embed Bitcoin headers, and provide rollup finality.

Governance Layer

NetworkParams, ValidatorRegistry, Treasury

Manage configuration, validator sets, and upgrades.

All layers converge back to Bitcoin — the single source of finality for the network.

End-to-End Transaction Lifecycle

1. Deposit & Mint (BTC → sovaBTC)

  1. User sends BTC to a network-derived deposit address.

  2. Sentinel registers the transaction and locks the relevant contract storage slot.

  3. Sentinel periodically queries connected Bitcoin nodes for confirmation depth and validity.

  4. Once confirmed (default: six blocks), Sentinel marks the slot as finalized.

  5. SovaEVM mints sovaBTC 1:1 to the depositor’s address.

  6. The event is recorded on-chain with the Bitcoin txid and block hash.

2. On-Chain Usage (sovaBTC Circulation)

  • Users deploy sovaBTC within vaults, DEXs, and DeFi protocols.

  • Smart contracts can call Bitcoin precompiles (broadcast, decode, address conversion).

  • Inspector ensures that any Bitcoin-linked state remains locked until finality is verified.

  • Consensus layer sequences transactions and embeds the current Bitcoin header into each block.

3. Redemption & Withdrawal (sovaBTC → BTC)

  1. User calls burn(amount, btcAddress) to redeem Bitcoin.

  2. SovaEVM emits a withdrawal request; Sentinel records the pending transaction.

  3. Signing Service constructs and signs a raw Bitcoin transaction (HSM, MPC, or TSS).

  4. Transaction is broadcast to Bitcoin; Sentinel begins confirmation tracking.

  5. When confirmed, Sentinel unlocks the corresponding slot and reports finality.

  6. Inspector commits the final state; user receives BTC directly on L1.

Inter-Component Communication Map

              +----------------------+
              |     Bitcoin Nodes    |
              | (Verification & Tx)  |
              +----------+-----------+
                         |
           Confirmations |
                         v
+------------+       +-----------+       +-------------+
|  SovaEVM   | <---> |  Sentinel | <---> | Signing Svc |
| (Execution)|   RPC  |   Ledger  |   RPC  |   Broadcast |
+------------+       +-----------+       +-------------+
       ^                     |                    |
       |                     v                    |
       |             +---------------+            |
       |             |  op-node (L2) |            |
       |             |  + Anchor Ver.|            |
       |             +-------+-------+            |
       |                     |                    |
       |                     v                    |
       |             +---------------+            |
       |             | Governance &  |            |
       |             |  Parameters   |            |
       +-------------+---------------+------------+

Every interaction is authenticated and replayable. This architecture guarantees deterministic behavior across validators and full auditability for third parties.

Data & Event Synchronization

Sova maintains consistency through event-driven synchronization between services.

Emitter

Event Type

Listener(s)

Action

Inspector (EVM)

LockRegistered

Sentinel

Register new BTC-linked slot.

Sentinel

Confirmed / Expired

Inspector

Unlock or revert slot upon confirmation or timeout.

SovaEVM

WithdrawalRequested

Signing Service

Construct and sign BTC transaction.

Signing Service

WithdrawalBroadcasted

Sentinel

Start confirmation tracking.

Bitcoin Nodes

Block events

Sentinel

Update confirmation depth.

⚙️ Sentinel performs confirmation checks periodically across any configured Bitcoin nodes. If a transaction exceeds the 21-block timeout without confirmation, Sentinel unlocks the slot lazily when sova-reth next queries its status, returning the stored revert_value so the EVM can safely roll back.

Cross-Layer Finality Enforcement

Sova’s determinism is enforced collaboratively:

  1. Sentinel — Monitors Bitcoin transactions, exposes lock state via API.

  2. Inspector — Locks, unlocks, or reverts contract state based on Sentinel responses.

  3. Consensus Layer — Validates Bitcoin anchors and rejects blocks with invalid headers.

  4. Governance — Defines thresholds such as confirmation depth and timeout windows.

This multi-layer design ensures that even if one component fails, Bitcoin truth remains authoritative.

Security Anchors & Audit Trail

Anchor Type

Source

Stored In

Purpose

Bitcoin Header

Bitcoin Nodes

SovaL1Block Contract

Verify L2 blocks against L1 Bitcoin.

Slot Lock Ledger

Sentinel

Local DB (migrations.rs)

Record start_block, end_block, btc_block, revert_value, current_value.

Withdrawal txid

Signing Service

On-chain Burn Events

Track L1 redemption.

Validator Signatures

Consensus

Block Metadata

Authenticate sequencing and inclusion.

Governance Proposals

DAO Registry

On-chain

Parameter and upgrade traceability.

Together, these anchors produce an end-to-end proof of correctness that anyone can independently verify.

Integration with Ecosystem Layers

Sova’s modular architecture integrates directly with other systems:

  • Bitcoin: Verifies, tracks, and settles real Bitcoin transactions — no synthetic wrappers.

  • Ethereum / Superchain: Provides composability with OP-Stack rollups and EVM tooling.

  • Hyperlane: Enables cross-chain yield routing and vault state proofs.

  • Custodians: Powers qualified-custody integrations via SovaX triparty agreements.

  • DeFi Protocols: Supports lending, swaps, and yield markets denominated in Bitcoin.

All external connections preserve Bitcoin-level assurance — no bridges, no custodians, no wrapped assets.

Institutional & Developer Impact

For Institutions

  • Transparent proof of reserves and yield.

  • Deterministic audit trails for compliance.

  • Safe yield on BTC in qualified custody.

For Developers

  • Build Bitcoin-native DeFi in Solidity.

  • Access precompiles for BTC broadcast and parsing.

  • Integrate easily with Sentinel’s lock model for finality-aware contracts.

This dual focus positions Sova as both a financial infrastructure layer and a developer platform for productive Bitcoin.

End-to-End Guarantees

  1. Verifiable Finality — Every state change is linked to a confirmed Bitcoin block.

  2. Deterministic Replay — Any node can reconstruct history using Bitcoin + Sova data.

  3. Zero External Trust — Bitcoin validation replaces bridge or custodian risk.

These guarantees make Sova a trust-minimized yield and liquidity network, not just another Layer-2.

Summary

  • Bitcoin is the base truth; every Sova subsystem enforces it.

  • Sentinel ensures real-time synchronization with Bitcoin confirmations.

  • Lazy reversion avoids wasted computation while preserving safety.

  • Event-driven coordination keeps all services deterministic and auditable.

  • Governance manages upgrades without touching Bitcoin-linked logic.

Sova achieves bridgeless programmability with Bitcoin-level finality — the foundation of a true Bitcoin Yield Layer.

PreviousGovernance & Network ParametersNext$SOVA

Last updated