Core Chain's Satoshi Plus: Hybrid PoW and DPoS for Bitcoin L2
Core Chain combines Bitcoin mining hashpower with delegated proof-of-stake in its Satoshi Plus consensus mechanism.
Core Chain is an EVM-compatible blockchain that attempts to align itself with Bitcoin's security by incorporating mining hashpower into its validator election process. Its consensus mechanism, called Satoshi Plus, blends Delegated Proof of Work (DPoW) with Delegated Proof of Stake (DPoS) to elect a rotating validator set. The design raises an interesting question for the broader Layer 2 landscape: can a chain inherit Bitcoin's security guarantees without being anchored to Bitcoin's own consensus rules?
This article breaks down how Satoshi Plus works, examines its dual-staking economics, and compares its trust assumptions against other approaches to scaling Bitcoin, including pure Bitcoin Layer 2s like Lightning and Spark, federated models like Liquid, and rollup-based designs.
What Is Satoshi Plus?
Satoshi Plus is a hybrid consensus mechanism that selects validators using a composite score derived from two inputs: hash power delegated by Bitcoin miners and CORE tokens delegated by stakeholders. The system runs on Core Chain, which is EVM-compatible and supports Solidity smart contracts. Validators produce blocks in rounds, and the top 21 validators by hybrid score are elected to participate in each round.
The hybrid score formula combines the two delegation components with a weighting factor: S = (rHp/tHp) * m + (rSp/tSp) * (1 - m), where rHp is the hash power delegated to a specific validator, tHp is total delegated hash power, rSp is the CORE staked with that validator, tSp is the total CORE staked across the network, and m is the weighting factor between the PoW and PoS components. This score determines which 21 validators are elected for each consensus round.
Delegated Proof of Work (DPoW)
Bitcoin miners participate in Core's consensus without redirecting their hash power away from Bitcoin. Instead, miners embed a vote for a Core validator in the coinbase transaction of the Bitcoin blocks they mine. This piggybacks on existing mining activity: miners continue securing Bitcoin while simultaneously casting validator votes on Core Chain. In return, participating miners earn CORE token rewards on top of their regular Bitcoin block rewards.
This approach differs from merged mining as implemented by chains like RSK. In merged mining, the miner submits proof of work directly to the secondary chain. In Core's DPoW model, miners simply express a preference for a validator: the actual block production on Core uses a DPoS-style mechanism, not proof of work.
Delegated Proof of Stake (DPoS)
CORE token holders delegate their tokens to validators of their choice. One CORE equals one vote, making delegation linear and straightforward. Delegated CORE is not slashed for validator misbehavior: only the validator's self-bonded stake is subject to slashing penalties for downtime or double signing. CORE can be undelegated at any time, providing liquidity flexibility that distinguishes it from systems with long unbonding periods.
Relayers
A third participant class, relayers, bridges the gap between Bitcoin and Core Chain. Relayers operate an on-chain Bitcoin light client that receives Bitcoin block headers, allowing Core's smart contracts to verify Bitcoin mining activity. As Blockworks reported, relayers “run an on-chain light client for Bitcoin” that transmits block headers to Core Chain. Relayers earn a small share of CORE rewards (0.48% of total supply is allocated to relayer incentives).
Key distinction: Core Chain's DPoW component uses Bitcoin hash power for validator election, not for block production. Core validators produce blocks using a DPoS-style round-robin mechanism. The hash power delegation is a voting signal, not a security guarantee in the same sense as Bitcoin's proof of work.
Non-Custodial Bitcoin Staking
Core introduced non-custodial Bitcoin staking in April 2024, allowing BTC holders to participate in Core's consensus without bridging their assets to another chain. The mechanism uses Bitcoin's native CLTV timelocks: stakers create a transaction that locks their BTC for a specified duration and includes metadata identifying their chosen Core validator and a reward address for CORE tokens.
The staked Bitcoin never leaves the Bitcoin blockchain. Users retain their private keys and can spend the BTC once the timelock expires. This is a meaningful improvement over bridge-based staking models where users must trust a custodian or a multisig federation to hold their assets. However, the staked BTC cannot be used on Core Chain itself: it serves purely as a consensus signal, not as collateral for DeFi applications on Core.
Staking parameters
- Minimum BTC stake: 0.01 BTC
- Lock mechanism: Bitcoin-native CLTV timelock
- Custody: non-custodial (user retains private keys)
- Rewards: paid in CORE tokens, not in BTC
- Slashing risk: none for delegators (only validator self-stake is slashable)
- Early withdrawal: not possible before timelock expiry
Dual Staking and the CORE Token
In November 2024, Core launched the Fusion Upgrade, introducing a dual-staking model that pairs BTC staking with CORE token delegation. The system incentivizes BTC stakers to also stake CORE tokens by offering tiered reward multipliers based on their CORE-to-BTC ratio.
Dual staking tiers
| CORE per BTC staked | Tier | Effect |
|---|---|---|
| < 1,000 CORE | Base | Standard BTC staking rewards |
| 1,000 to 2,999 CORE | Level 1 | Enhanced reward multiplier |
| 3,000 to 7,999 CORE | Level 2 | Higher reward multiplier |
| 8,000+ CORE | Level 3 | Maximum reward multiplier |
The exact multiplier at each tier is dynamic and adjusts based on network conditions. Longer lock-up periods for BTC also result in higher rewards, creating a compound incentive structure that rewards both capital commitment and CORE token acquisition.
CORE tokenomics
The CORE token has a hard cap of 2.1 billion, intentionally mirroring Bitcoin's 21 million supply cap. The token allocation breaks down as follows: 40% to node mining rewards, 25% to user airdrops, 15% to contributors, 10% to reserves, 9.5% to treasury, and 0.48% to relayer rewards. The vesting schedule extends through 2137, paralleling Bitcoin's emission timeline. CORE serves three functions: transaction fees on the Core network, staking and delegation, and governance voting.
Dual-token dependency: Core's dual-staking model creates a circular incentive where maximizing BTC staking yields requires acquiring and staking CORE tokens. This means the effective yield on BTC staking is partially denominated in CORE, introducing exposure to CORE token price volatility. Stakers should evaluate whether the additional CORE rewards compensate for this added risk.
Trust Assumptions Compared
The critical question for any Bitcoin-adjacent protocol is: what must you trust, and what can you verify? Core Chain's trust model differs significantly from both Bitcoin Layer 1 and from protocols that anchor their security directly to Bitcoin's consensus.
What Core inherits from Bitcoin
Core uses Bitcoin hash power as an input to validator selection. Miners signal support for validators through coinbase data, and relayers verify this through a Bitcoin light client. BTC staking uses native timelocks, keeping staked assets on Bitcoin's chain. These elements create a genuine connection to Bitcoin, but the connection is economic and signaling-based, not a cryptographic anchoring of Core's state to Bitcoin's blockchain.
What Core does not inherit from Bitcoin
Core Chain runs its own independent consensus. Block production, transaction ordering, and state transitions happen on Core's validator set, not on Bitcoin. If Core's validators collude or go offline, Bitcoin's proof of work does not protect Core Chain users. The trust assumption shifts from “Bitcoin's hashrate secures this chain” to “the validator election process that uses Bitcoin hashrate as one input produces honest validators.”
As a BitMEX Research analysis noted, the “Layer 2” label is unusual for Core because the staked BTC cannot actually be used on the Core blockchain. The Bitcoin locked through CLTV timelocks serves as a consensus signal, not as a bridge allowing BTC to move onto and off of Core Chain trustlessly.
Consensus Models Across Bitcoin L2s
Different approaches to Bitcoin scaling make different tradeoffs between trustlessness, functionality, and complexity. The following table compares Core Chain against other major approaches.
| Property | Core Chain | Lightning | Spark | Liquid | Rollups (e.g., Citrea) |
|---|---|---|---|---|---|
| Consensus type | Hybrid DPoW + DPoS | Payment channels | Statechain (1-of-n operators) | Federated multisig | Validity proofs posted to Bitcoin |
| Trust model | 21 elected validators | Trustless (channel counterparty) | 1-of-n honest operator | k-of-n federation | Cryptographic (ZK proofs) |
| BTC custody | Timelocked on Bitcoin (non-custodial) | Self-custodial in channels | Self-custodial via FROST | Federation-custodied | Bridge contract |
| Smart contracts | Full EVM (Solidity) | No (HTLCs only) | No (transfer-focused) | Elements Script | Full EVM |
| Additional token required | Yes (CORE) | No | No | L-BTC (pegged) | Varies |
| Unilateral exit to Bitcoin L1 | No (separate chain) | Yes | Yes | No (federation controls peg) | Via proof verification |
| Finality | Seconds (Core consensus) | Instant (channel) | Instant (off-chain) | ~2 minutes | Minutes to hours (proof submission) |
The most significant distinction is the unilateral exit property. Lightning and Spark allow users to exit back to Bitcoin L1 without requiring permission from any counterparty. Core Chain, as an independent blockchain, has no such mechanism: if you move BTC to Core (via a bridge, not via the staking timelock), you depend on that bridge's security model to get it back.
The EVM Ecosystem on Core
Core Chain's EVM compatibility means developers can deploy existing Solidity contracts with minimal modifications. The ecosystem includes DEXs, lending protocols, and yield aggregators. DappRadar tracks Core dApps alongside other chains, and infrastructure providers like Chainstack offer RPC endpoints for Core nodes.
Core Foundation has announced ecosystem grants, including a $5 million Innovation Fund targeting India's developer community. The 2026 roadmap, as reported by Token Relations, prioritizes sustainable revenue models, liquid staking tokens, consumer-facing Bitcoin yield products, and CORE token buybacks. This signals a shift toward less reliance on gas fee revenue and more emphasis on Bitcoin yield infrastructure.
Network metrics
As of late 2025, Core reported approximately 69.2 million total unique addresses and around 3,048 BTC staked through its non-custodial staking mechanism, with roughly 240.9 million CORE tokens delegated to validators. Earlier in 2025, following the Ceffu institutional custody integration, the network reported approximately 4,352 BTC staked under the dual-staking model, valued at roughly $380 million at the time.
Core's TVL in DeFi protocols has fluctuated. In September 2024, it was reported at over $346 million, making it the largest Bitcoin sidechain by TVL at that time. For current figures, check DefiLlama's Core page.
Tradeoffs and Risks
Validator centralization
With only 21 active validators, Core Chain's consensus set is relatively small. This is comparable to other DPoS chains like EOS and BNB Chain, but substantially more concentrated than Bitcoin's thousands of miners or Ethereum's hundreds of thousands of validators. A smaller validator set introduces higher censorship resistance risk and makes the network more sensitive to validator collusion.
Dual-token complexity
The requirement to hold both BTC and CORE to maximize staking yields adds friction and introduces price correlation risk. If CORE token value declines, the effective yield on BTC staking decreases, potentially triggering unstaking and further price pressure on CORE. This reflexive dynamic is common in dual-token systems and represents a structural risk that single-asset protocols avoid.
Classification ambiguity
Core Chain variously describes itself as a “Bitcoin-powered Layer 1,” a “Bitcoin-aligned blockchain,” and a Bitcoin Layer 2. The classification matters because it shapes user expectations about security guarantees. As the BitMEX analysis observed, the non-custodial BTC staking mechanism locks Bitcoin on L1 as a consensus signal, but users cannot actually spend that BTC on Core Chain. This makes the “Layer 2” framing unconventional compared to systems like Lightning or rollups, where the purpose of the L2 is to extend Bitcoin or Ethereum's functionality for the locked assets.
Security inheritance limitations
Core's marketing emphasizes that it “leverages Bitcoin's hashrate,” but the actual security guarantee is narrower than that phrase implies. Bitcoin hashrate influences which validators are elected, but it does not secure Core Chain's block production. If Core's 21 validators collude to censor transactions or produce invalid blocks, Bitcoin miners cannot intervene. Compare this to a validity proof rollup, where invalid state transitions are rejected by the base layer regardless of the sequencer's behavior.
Where Core Fits in the Bitcoin Scaling Landscape
Core Chain occupies a specific niche: it prioritizes programmability and EVM compatibility over trustlessness. For developers who want to build DeFi applications connected to Bitcoin's ecosystem, Core offers a familiar Solidity development environment with lower fees than Ethereum mainnet. The non-custodial BTC staking mechanism is a genuine innovation that avoids the custody risks of bridge-based approaches.
However, the tradeoff is clear. Core Chain does not offer the trustless guarantees of pure Bitcoin protocols. Users who value self-custody and trustless transfers above smart contract functionality may prefer solutions like Lightning or Spark, which inherit Bitcoin's security model more directly. Spark, for instance, enables instant, self-custodial Bitcoin and stablecoin transfers without requiring an additional token or trusting a separate validator set: users can always exit to Bitcoin L1 unilaterally using pre-signed transactions.
For those interested in exploring trustless Bitcoin transfers and dollar-denominated payments on a Bitcoin Layer 2, the Spark developer documentation provides SDK integration guides. Wallet builders looking for a production-ready implementation can explore General Bread, a Spark-powered wallet that demonstrates these principles in practice. For a broader comparison of Bitcoin scaling approaches, see our Bitcoin Layer 2 comparison.
This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.

