Whitepaper · v2.0 · November 2026

SatoshiFi.
Bitcoin without intermediaries.

Bitcoin federations and confederations on EVM. Native BTC stays on a Taproot wallet controlled by FROST threshold signatures; its movements are proven on-chain through a header relay or a zero-knowledge SPV state. Custodians are chosen from ULR holders, and confederation treasuries pay daily income to ULR stakers.

TechnologyFROST · DKG · SPV · ZK
Bitcoinmainnet
LayerEthereum / EVM
LicenseMIT contracts
Contents
Chapter 01 · Introduction

Introduction and project overview

SatoshiFi lets a group of participants hold Bitcoin together without a single custodian and issue fully backed ERC-20 wrappers for it on an EVM network. The bitcoin never leaves Bitcoin: it sits on a Pay-to-Taproot wallet whose key exists only as shares distributed by DKG. Every spend requires a threshold of participants to sign with FROST.

The EVM side does not trust anyone's word about Bitcoin. Deposits and payouts are accepted only with a Merkle proof against a Bitcoin header chain that the contracts verify themselves — either through a proof-of-work header relay or through a zero-knowledge state updated by succinct proofs. Wrapped value is issued only against proven, unspent, sufficiently confirmed outputs, and burned only after the payout transaction is proven on Bitcoin.

Governance is split by purpose. FROST participants authorize operations; custodians — admitted from holders of the ULR governance token — add a second, independent approval for confederation operations; ULR stakers receive the daily income that confederation treasuries pay out.

What the protocol delivers

Layer · Crypto

Threshold custody

FROST Schnorr/BIP340 signatures over a Taproot key generated by DKG. No party, operator included, can spend or approve alone.

Layer · SPV

Proven Bitcoin state

Proof-of-work header relay or ZK-SPV state, both with canonical-chain, depth and freshness checks before any mint or settlement.

Layer · Tokens

1:1 backed wrappers

MP tokens per pool and S tokens per federation or confederation. One satoshi equals 1010 base units; principal can never pay miner fees.

Layer · DAO

ULR governance and income

Custodian candidates from ULR holders, delegated stakers' votes, and a daily payout of 90% of each treasury's excess over its reserve.

t-of-n
FROST threshold
6
Confirmations per deposit and payout
100
Max reorg depth before halt
1010
Token base units per satoshi
Chapter 02 · Architecture

System architecture

The system is a stack of independent layers. Each one checks its inputs itself instead of trusting the layer above: the deposit registry re-checks Bitcoin proofs, the escrow re-checks the payment, and every participant's client re-checks contracts, plans and Bitcoin data before it signs anything.

Architecture layers

LayerResponsibility
Onboarding & DKGSigned on-chain invitation, encrypted DKG exchange on a public board, three key ceremonies per deployment
AuthorizationFROST signing sessions, target-bound operation hashes, custodian approvals
Bitcoin verificationHeader relay with freshness guard, or ZK-SPV state and adapter; canonicality, depth and Merkle inclusion
IssuanceDeposit registry with single-use outpoints and backing accounting; MP minting by mining pools
MultiPoolMP aggregation into S tokens, per-pool balances, withdrawal requests
PayoutUTXO reservation, public signing plan, FROST Bitcoin signing, escrow settlement by SPV proof
Fees & treasuryWrap/unwrap fees, fee pipeline, confederation treasuries, BTC fee reserve
ULRGovernance token, staking, custodian candidates, delegated votes, daily snapshots and payouts

Key components

DKG

DKGCoordinator, DKGOnchainBoard

Phase-timed DKG with encrypted packages published on-chain. No secret is generated or stored on-chain.

FROST

FROSTCoordinator, FROSTVerifier, DKGAuthorization

Signing sessions bound to a completed DKG result; authorization consumes each approved operation exactly once.

Bitcoin

MainnetHeaderRelay, MainnetSPVGuard, ZkBitcoinStateV2

Two interchangeable verification backends behind one proof interface used by every consumer.

Issuance

BitcoinDepositRegistry, MiningPoolV1, PoolMpToken

Proof-only MP issuance. No owner mint, no discretionary redemption.

Payout

BitcoinBatchRegistry, BitcoinSigningBoard, BitcoinWithdrawalEscrow

Reserve, bind, sign, broadcast and settle a payout without exchanging files between participants.

ULR

ULRStaking, ULRConfederationTreasury, ULRCustodianSnapshots

Shared staking, one treasury per confederation, and a daily FROST-attested custodian snapshot.

Data flow: BTC → MP → S → BTC

  1. Deposit to the federation wallet The user sends BTC to the confederation's Taproot wallet, bound to an EVM recipient (see Chapter 08).
  2. Bitcoin state catches up The relay keeper submits headers, or a ZK worker publishes a proof that advances the ZK state.
  3. Inclusion and depth proven The deposit registry checks the canonical block, at least 6 confirmations (100 for coinbase), Merkle inclusion, script and amount.
  4. FROST-approved mint MiningPoolV1.mintFromProof consumes the approval and mints exactly satoshis × 1010 MP to the recipients.
  5. S tokens issued MP is deposited into the confederation MultiPool; S tokens are minted net of the wrap fee.
  6. Withdrawal requested The user names an amount and a Bitcoin address. The payout is rounded down to a whole satoshi.
  7. Approved and escrowed FROST and custodian approvals process the request; S and MP are locked in escrow, not yet burned.
  8. Reserved, bound and signed Inputs are reserved, the exact transaction is bound to the request, and participants sign it with the FROST Bitcoin key.
  9. Broadcast Any participant aggregates the signature shares and broadcasts the transaction.
  10. Settled by proof After 6 confirmations the escrow verifies the payment, burns S and MP, moves remaining backing to the change output and accrues the unwrap fee.
Chapter 03 · Smart Contracts

Smart contract layer

Contracts are written in Solidity 0.8.30 and compiled for Osaka with via-IR. Every contract is immutable once deployed: there is no upgrade proxy and no administrator who can change rules later. A new version means a new, separately approved deployment. Large graphs are built by controlled leaf deployers so that each contract stays within the EIP-170 size limit.

Main contracts

ContractPurpose
DKGCoordinatorDKG phases, receipts, public key shares and completed results (purpose, group key, participants, threshold)
DKGOnchainBoardInvitation, enrollments, encrypted DKG packages and public intents for every approval
FROSTCoordinator / FROSTVerifierSigning sessions bound to a DKG result; aggregate BIP340 verification
DKGAuthorizationPins one federation key; turns a finalized session into a single-use approval of one target operation
FederationFactory / ConfederationFactoryDeploy authorization, pool, S token and, for confederations, CustodianValidator
CustodianValidatorActive custodian set, custodian approvals, candidate source binding
MainnetHeaderRelay / MainnetSPVGuardBitcoin headers from a reviewed checkpoint; freshness and halt guard for consumers
ZkBitcoinStateV2 / ZkSpvAdapterZK-proven Bitcoin header state with a pinned Groth16 verifier; header materialization
BitcoinDepositRegistryRegistered wallet scripts, single-use outpoints, backing and wallet-change accounting
MiningPoolV1 / PoolMpTokenProof-only MP issuance against deposits or coinbase rewards
ConfederationMultiPoolMP deposits, S minting, withdrawal requests, fee accrual
BitcoinBatchRegistry / BitcoinSigningBoardUTXO reservations and the public payout plan, commitments and signature shares
BitcoinWithdrawalEscrowLocks S and MP per request, binds the transaction, settles by SPV proof
ULRStaking / ULRConfederationTreasury / ULRCustodianSnapshotsStaking and claims, treasury payouts, daily custodian snapshot

Target-bound operation hash

Every privileged action is approved as an exact operation, not as a general permission. The hash binds the target contract, the function selector, the parameters and the target's own nonce:

function hashOperation(
    address target,
    bytes4 selector,
    bytes32 paramsHash,
    uint256 nonce
) external view returns (bytes32)

Each target exposes helpers such as getMintOperationHash, getProcessWithdrawalOperationHash or getBindOperationHash. The approval cycle is always the same: open a FROST session for the hash, publish a typed intent on the board, let each participant independently review and sign, finalize, call authorizeOperation, add custodian approvals where required, and execute. The target consumes the approval, so it cannot be replayed.

Chapter 04 · User Flows

User scenarios

Scenario 1 — Wrap BTC into S tokens

  1. Enter the EVM recipient The interface returns the deposit address for that recipient (Chapter 08).
  2. Send BTC from any wallet or exchange Any number of transactions; the sender's addresses play no role in ownership.
  3. Wait for 6 confirmations The Bitcoin state on EVM must also be fresh and include the block.
  4. MP minted to the recipient Participants approve the mint; anyone may then submit the proof.
  5. Deposit MP, receive S S is minted net of the wrap fee and can be used freely in DeFi.

Scenario 2 — Redeem S tokens for BTC

  1. Request a withdrawal Amount of S and a P2WPKH or P2TR address. Minimum payout: 294 sat (P2WPKH) or 330 sat (P2TR).
  2. Approval and escrow FROST plus custodian approval. Tokens are locked; before signing starts the request can still be cancelled with a full refund.
  3. Reserve and bind Two separate FROST approvals fix the inputs, outputs, fee and exact transaction ID.
  4. Threshold Bitcoin signature Participants publish nonce commitments and signature shares on the signing board.
  5. Payout and settlement BTC arrives at the user's address. After 6 confirmations the escrow proof burns the locked tokens.

Scenario 3 — Mining rewards

A pool whose payout script is the federation wallet mints MP against coinbase outputs in the same way as against deposits. Coinbase outputs require 100 confirmations to mint and at least 101 before the wallet may spend them.

Scenario 4 — Custody transfer between wallets

BTC can move between two independent federation wallets without the source participants taking part in the destination. The source pays and burns its MP; the destination gateway verifies the exact output by SPV together with the source's on-chain payment record and issues local cBTC to the fixed recipient. Later exit uses the destination's custodians only.

Scenario 5 — Become a custodian and earn

Hold and stake ULR. Reaching the candidate threshold (200,000 ULR by default) makes the address a custodian candidate; admission is a separate confederation decision. Any staker receives a share of daily treasury payouts in proportion to stake and may delegate voting to an active custodian without giving up the reward.

Chapter 05 · Tokens

Tokens and their backing

Two kinds of wrappers carry bitcoin value; a third token carries governance and income rights. Wrappers are minted only against proven bitcoin and burned only against a proven payout.

TokenIssued byBacking and use
MP (pool token)MiningPoolV1 through PoolMpTokenExactly satoshis × 1010 per proven output; freely transferable ERC-20
FS / CS (S tokens)Federation or confederation MultiPoolMinted for deposited MP net of the wrap fee; redeemable to BTC through the withdrawal flow
cBTCDestination custody gatewayLocal wrapper issued after a proven transfer between independent wallets
ULRCustodianDAOToken10,000,000 supply minted once, no mint function; governance, custodian candidacy and staking income

Backing invariants

Chapter 06 · Threshold Cryptography

FROST, DKG, and BIP340

FROST (Flexible Round-Optimized Schnorr Threshold Signatures) is the foundation of custody. The private key never exists in one place: each participant holds a share, and a valid signature needs a threshold of partial signatures. Signatures are plain BIP340 Schnorr signatures, so a Bitcoin node sees an ordinary Taproot key-path spend.

On-chain onboarding

  1. Signed invitation The operator publishes an immutable invitation: participants, threshold, EVM and Bitcoin networks, confirmation depths, payout minimums, fees and launch parameters. Its fingerprint fixes the policy.
  2. Enrollment Each participant reads the invitation from the chain and publishes signed transport keys. No file is exchanged out of band.
  3. Three DKG ceremonies evm_ceremony for federation authorization, conf_ceremony for confederation authorization, btc_ceremony for the Bitcoin spending key. Each phase has a deadline; a missed deadline fails the ceremony instead of leaving it half-done.
  4. Bootstrap A durable, journaled deployment of the whole graph. Each configuration step is itself FROST-approved and, for the confederation, custodian-approved.
  5. Registry pinning Before the first Bitcoin signature every participant inspects the deployed contracts, compares the fingerprint and pins it locally. A look-alike contract cannot later steer the signer.

Separate keys for separate purposes

DKG results carry a purpose. EVM_AUTH keys approve EVM operations; BTC_SPEND keys sign Bitcoin transactions. The Bitcoin key never approves EVM operations, and a payout always needs both: EVM approvals (reserve and bind) and a Bitcoin signature over exactly the bound transaction.

Nonce safety

A Schnorr nonce reused for two messages reveals the key share. Each participant's client writes every nonce and share to an encrypted state and an independent spent journal before publishing, refuses to sign twice with the same nonce, and fails closed if the journal is missing or rolled back. Recovery never consists of deleting state.

FROSTVerifier formats

Chapter 07 · Bitcoin Integration

Bitcoin verification: header relay and ZK-SPV

Contracts never take a Bitcoin fact on trust. A deposit or a payout counts only with a Merkle proof against a header that the contracts consider canonical, deep enough and fresh. Two backends provide that header state. The choice is made in the signed invitation and is the same for every consumer of a deployment.

Backend A — Proof-of-work header relay

MainnetHeaderRelay starts from a reviewed checkpoint at a difficulty-period boundary, with its exact chainwork and ten predecessors. For every new header it checks the parent link, proof of work against the target, exact bits within a period and the Bitcoin Core retarget rule at boundaries, median-time-past and the two-hour future limit. Among competing branches it selects the heaviest.

Backend B — ZK-SPV Sepolia testing

The ZK backend replaces header-by-header submission with succinct proofs. A RISC Zero guest runs a full Bitcoin header verifier — proof of work, retarget, median time, fork choice by chainwork, reorg depth and halt — over a batch of headers. The proof is compressed from STARK to Groth16 and accepted on-chain by ZkBitcoinStateV2 with a pinned verifier. One proof updates the whole header state; deposits and payouts still use ordinary raw transactions and Merkle branches through ZkSpvAdapter.

Confirmation depths

OperationRequired depth
Ordinary deposit mint6 confirmations (stricter policy allowed)
Coinbase reward mint100 confirmations
Spending a coinbase output, fee-reserve ingressat least 101 confirmations
Payout settlement6 confirmations
Reorganization followed before haltup to 100 blocks

Networks

Bitcoin mainnet and testnet4 each have their own relay and their own fixed ZK guest; regtest is supported for integration tests only. The EVM network is chosen independently: a deployment on Sepolia can verify Bitcoin mainnet or testnet4. Mainnet use requires each participant to run a fully synchronized, unpruned Bitcoin Core with transaction index.

Chapter 08 · Federation

Federation and confederation

A federation is a group of participants holding shares of authorization and Bitcoin keys through DKG. A confederation adds custodians: its operations need a FROST threshold and a custodian threshold for the same operation hash.

Deployment

FederationFactory and ConfederationFactory adopt a completed EVM_AUTH DKG and deploy, through controlled leaf deployers, a DKGAuthorization bound to that result, the MultiPool and its S token, and for a confederation the CustodianValidator. Changing participants or threshold requires a new DKG; the contracts reject a manifest change that would not rotate the key. On Ethereum mainnet factory deployment charges a fee to the project treasury.

The Bitcoin wallet

The wallet is a single Pay-to-Taproot output key from the BTC_SPEND DKG, spent by key path with SIGHASH_DEFAULT. Its script is registered in the deposit registry for one pool. Change always returns to the same wallet; payouts to the wallet's own script are rejected.

Deposit addresses and recipients

ModeHow the recipient is boundStatus
Shared wallet + SMP1The deposit transaction carries a marker that commits to recipient, pool, network and distributionImplemented
Address per requestThe user enters an EVM recipient and receives a unique bc1p… derived from the group key and the request. Everything arriving at it belongs to that recipient; MP is minted to that addressIn qualification

Address-per-request mode works with any wallet or exchange, because ownership no longer depends on the sender or on extra data in the transaction. It is built on BitcoinAddressRegistry with an immutable intent, recipient and script per address and a derivation verifier. Addresses are not issued until the verifier is qualified. In both modes the mint still needs FROST approval and the contract's own proof checks.

Custody states

A deployment can be ACTIVE, DRAINING (no new issuance, existing obligations served), SUSPENDED (temporarily no minting) or COMPROMISED (terminal). Every transition is a quorum decision and increases a generation counter. A resume does not revive approvals from an earlier generation. No state moves BTC, releases reservations or changes a recipient.

MultiPool accounting

ConfederationMultiPool tracks balances per user and per MP token, so S tokens from one pool cannot redeem another pool's bitcoin. Withdrawal requests lock shares first; burning happens only on proven settlement, and a cancellation before signing releases the lock.

Reserves and reconciliation

Backing per outpoint is recorded on-chain. Full reconciliation of wallet UTXOs, pending deposits and token supply against the participants' own Bitcoin Core is a FROST-approved report. A negative or unknown result pauses Bitcoin signing until a reviewed recovery.

Chapter 09 · Custodians

Custodians and ULR governance

Custodians are the second line of approval in a confederation. They do not hold Bitcoin key shares; they independently confirm the same operation hash that FROST participants approved. Custodians are recruited from ULR holders, and ULR stakers decide non-monetary questions by vote.

From holder to custodian

  1. Nomination The first stake registers the address as a nominee in ULRStaking.
  2. Candidate An address is an available candidate while its wallet plus own stake is at least the threshold H — 200,000 ULR by default, fixed at launch. Falling below the threshold removes availability immediately.
  3. Admission The confederation admits a candidate by FROST approval plus approval of the current custodians. The candidate is re-checked right before inclusion.
  4. Active custodian Signs custodian approvals. Losing ULR later does not remove a custodian automatically; removal is a separate approved decision.

With a 10,000,000 supply and a 200,000 threshold, at most 50 holders can meet the threshold at any time. Admission never changes the FROST DKG and creates no key shares.

Delegated voting

A staker may delegate its vote, separately for each confederation, to an active custodian. The custodian votes on the owner's behalf in stakers' decisions but cannot unstake, claim or redirect the owner's income. A removed custodian loses all delegations at once; re-admission does not restore them.

Stakers' decisions

Decisions are opened by confederation FROST approval and weighted by stake eligible on the last completed UTC day, so stake added after creation does not change the weight. Quorum counts for, against and abstain; a decision passes when quorum is met and votes for exceed votes against. Results are recorded but do not execute anything: treasury spending, custodian changes and Bitcoin operations always need their own approvals.

Chapter 10 · Treasury

Treasuries and daily ULR income

Every confederation has one ULRConfederationTreasury holding a single USD stablecoin — the same token that ULRStaking pays out. Realized fee income is converted into that stablecoin and routed to the treasury. Once a day the treasury pays the staking contract a share of its excess over a reserve floor; stakers then claim pro rata.

Daily payout

R = reserve floor          (default $1,000)
b = payout share           (default 90%)
T = treasury stablecoin balance at payout
C = ULR of this confederation's custodians in the daily snapshot
G = ULR of all custodians in the system in the same snapshot

payout = floor( (T − R) × b × C / G )   if T > R, C > 0, G > 0
payout = 0                              otherwise

Example with defaults: treasury $11,000, this confederation's custodians hold 600,000 of the system's 1,000,000 custodian ULR. Payout = $10,000 × 90% × 60% = $5,400; $5,600 stays in the treasury. The reserve, the undistributed 10% and the part outside the custodian share remain in the treasury and take part in the next day's calculation. A missed day is not a debt: only the previous day can be paid, once.

The custodian snapshot

Staking and claims

Chapter 11 · Fee System

Fee system: wrap, unwrap, miner fees

Protocol fees are charged in wrapped value and end up, once realized, in the confederation treasury. Bitcoin miner fees are a separate cost paid from bitcoin that backs no wrapper. Fee parameters are fixed in the invitation and changed only by FROST plus custodian approval.

Wrap and unwrap fees

From accrued fees to treasury income

  1. Accrual in the pool Fees accumulate as MP inside the MultiPool, backed by wallet change.
  2. Approved claim claimFees releases accrued MP under FROST and custodian approval.
  3. Conversion PoolFeePipeline converts the actual tokens into the payout stablecoin through a funded converter.
  4. Router to treasury The confederation fee router forwards realized income to its ULRConfederationTreasury.

Factory deployment fees are separate: on Ethereum mainnet they go through the project router to the project treasury.

Miner fees

Chapter 12 · Security

Security and risks

Security comes from independent checks that an attacker would have to defeat at the same time. When a check cannot be completed, the system stops instead of guessing: an unknown state is never treated as a healthy one.

Defense layers

Layer 1

Threshold custody

No single party holds a usable key. Spending and approvals need a FROST threshold.

Layer 2

Exact, single-use approvals

Approvals bind target, function, parameters and nonce, and are consumed on use.

Layer 3

Custodian second approval

Confederation operations also need custodians admitted from ULR holders.

Layer 4

Contract-verified Bitcoin

Relay or ZK state with proof of work, depth, freshness and a permanent halt on deep reorgs.

Layer 5

Backing invariants

Single-use outpoints, exact minting, principal never pays fees, burn only after proven payout.

Layer 6

Participant-side review

Each signer pins the registry, checks contract provenance, plans and UTXOs against its own Bitcoin Core.

Layer 7

Nonce journals

Encrypted state plus independent spent journal; no nonce reuse, fail closed on rollback.

Layer 8

Immutability

No upgrade proxy and no administrator reset. Halt and terminal states cannot be undone silently.

Known risks and mitigations

RiskMitigation and residual risk
Compromise of key sharesThreshold signing, geographic distribution, custody states down to COMPROMISED; above the threshold the wallet is at risk
Stalled relay or ZK updatesFreshness checks block minting and settlement; this costs liveness, not funds. Keepers and workers must run continuously
Deep Bitcoin reorganizationRelay halts permanently above 100 blocks; the ZK worker blocks its own work locally, without a guaranteed global on-chain halt
Faulty RPC or provider outageClients verify against their own Bitcoin Core; an unconfirmed observation pauses that participant's signing until reviewed
Snapshot manipulationFROST-attested daily snapshot; inventory completeness is an attestation, and short-term borrowing of ULR around midnight is not excluded
Off-chain conversion of feesExplicit approvals with minimum output for each conversion; the converter itself must be reviewed
Contract defectsContracts cannot be patched in place; a fix needs a new deployment and migration of obligations

Production checklist

Chapter 13 · Integration

BTCyield: yield|loan stream on SatoshiFi

BTCyield is a product layer on top of SatoshiFi infrastructure. SatoshiFi provides cross-chain wrapping and custodial infrastructure through FROST. Yield placement into Yield Basis and Silo Finance is executed directly by the SatoshiFi team, under a joint-decision manager multisig.

Three yield streams

Stream 1

Confederation · 2.5% + 7% APY

Risk: minimal. Full BTC control. Create your own confederation and earn 2.5% APY on all capital staked in it — even without staking any BTC of your own. Stake your own BTC as well and earn an additional 7% APY on your own stake, on top of the 2.5% you keep earning on third-party capital. Participants remain owners of their bitcoins. The custodian algorithmically cannot block withdrawal of burned wrappers — their job is solely to defend against key compromise.

Stream 2

Yield|Loan Stream · 4–5% APY

Risk: medium. Rent from the entire system TVL. Wrap BTC into sBTC — SatoshiFi's own decentralized founders' wrapper, free of compliance screening and blocklists — and provide liquidity directly into Yield Basis and Silo Finance. Internally, the manager multisig also maintains a cbBTC/sBTC pair on Yield Basis to manage the peg semi-automatically, topping up liquidity when needed; this is a backend mechanic, not the wrapper you receive. You earn against the full system TVL — all confederations combined.

Stream 3

ULR staking · treasury income

Risk: strategic. Pro-rata participation. ULR stakers receive daily payouts from every connected confederation treasury: 90% of the treasury's excess over its $1,000 reserve, weighted by the share of ULR its custodians hold. Holders of 200,000 ULR can become custodian candidates.

Yield strategies

StrategyPlatformTarget yield
sBTC peg management (internal)Yield Basis + manager multisigBase layer + fees
cyb-sBTC vaultsYield Basis2–3% APY
sBTC lendingSilo Finance4–5% APY
yb-token collateral → crvUSDSilo FinanceLeverage
Stablecoin depositSilo Financefrom 4% APY

ULR at a glance

10,000,000
Total ULR supply
200,000
Custodian candidate threshold
90%
Daily payout of excess over reserve
0
Lock period, days

Thresholds, reserve floor and payout share are launch parameters; the figures above are defaults. Income is counted by full UTC days, and there is no premium for early entry or penalty for exit. See Chapter 10 for the exact formula.

Stream comparison

ConfederationYield|Loan StreamULR staking
BTC controlFullPartial (wrapped)Not required
Target yield2.5% + 7% APY (creator)4–5% APYPro-rata treasury income
Risk levelMinimalMediumStrategic
Minimum entry3+ participantsBTC for wrappingULR stake
Income typeCreator incomeRent from TVLDaily, variable
Chapter 14 · Roadmap

Status and roadmap

Every component below is implemented in code. The status column shows how far it has been proven outside local tests.

ComponentStatus
On-chain onboarding, DKG, FROST approvalsTested on Sepolia
Header relay on Bitcoin mainnet, deposit, mint, S tokens, withdrawal and settlementTested on Sepolia with real BTC — full BTC → MP → S → BTC cycle, October 2026
ZK-SPV state, local proving, Groth16 verificationLocal proofs accepted — Sepolia contour with Bitcoin testnet4 is next
ULR staking, treasuries, candidates, delegated votingImplemented, local tests
Address-per-request depositsIn qualification — addresses are not issued yet
BTC fee reserve, personal fee credits, custody transferImplemented, local tests
Independent external audit of the current versionPending

Next steps

  1. Now · ZK-SPV on Sepolia Full contour with Bitcoin testnet4: own Core and prover per participant, state updates, deposits, mint, withdrawal and settlement.
  2. In parallel · ULR distribution and liquidity ULR staking, custodian candidates, treasury connection. Sourcing liquidity for confederations.
  3. Next · Address-per-request qualification Derivation verifier review, watch and reconciliation, then issuing per-request bc1p… addresses.
  4. Then · Audit and mainnet launch External audit, production checkpoint and launch parameters, first confederations, connection to the Yield|Loan Stream.

Research directions

Earlier versions of this paper described pool reward calculators (PPS, FPPS, PPLNS, Score), Stratum share oracles with staking and slashing, hashrate rental, and support for Dogecoin, Bitcoin Cash and Litecoin. These are not part of the current deployment profile and remain research directions.

Chapter 15 · FAQ

Frequently asked questions

Who owns a deposit?
In address-per-request mode, whoever is named as the EVM recipient of that address: everything that arrives at it is minted to that recipient. With the shared wallet, the SMP1 marker in the deposit transaction names the recipient. The sending addresses play no role, so deposits from exchanges work.
Is minting automatic?
No contract mints on its own. The mint is a FROST-approved operation; after approval anyone may submit the Bitcoin proof, and the contract independently checks inclusion, depth, script and amount before minting.
Who pays the Bitcoin miner fee on withdrawal?
The confederation, from bitcoin that backs no wrapper: a treasury UTXO or the BTC fee reserve. A user may optionally fund the fee of their own withdrawal with fee credits. Wrapped principal never pays miner fees; the contracts reject such a transaction.
Can a withdrawal be cancelled?
Yes, until Bitcoin signing begins: the locked tokens return in full and no fee is charged. Once signing has started, time-outs, mempool absence or RPC failures never authorize a refund; the payment is completed or replaced only through an approved version.
Why are there two verification backends?
The header relay is simple and already tested, but needs a keeper that submits every header. ZK-SPV proves whole batches of headers with one succinct proof. Both serve the same proof interface, so mint and settlement rules do not depend on the choice.
What happens on a deep Bitcoin reorganization?
Up to 100 blocks is followed normally. A deeper reorganization permanently halts the relay; no further mint or settlement is accepted. Already executed operations are not reversed and nothing is reminted automatically; recovery is an incident procedure.
How do I become a custodian?
Stake ULR so that your wallet plus stake reaches the candidate threshold (200,000 ULR by default). The confederation then decides on admission with FROST and current custodian approval. Custodians approve operations; they do not hold Bitcoin key shares.
Do I need to be a custodian to earn ULR income?
No. Any staker earns in proportion to eligible stake. Custodians matter for how much each treasury pays: the payout is weighted by the share of ULR held by that confederation's custodians.
What does a participant need to run?
The signer client with its encrypted state, an EVM RPC with history, and for mainnet an own synchronized Bitcoin Core with transaction index. With ZK-SPV, also a local prover: Linux or WSL2 on x86-64, or macOS on Apple Silicon, with at least 8 GiB free disk space.
Can the contracts be upgraded?
No. Contracts are immutable and have no administrator. A new version is a new deployment, approved by the same participants; existing obligations are not moved by swapping addresses.
Chapter 16 · Glossary

Glossary

MP token
Pool wrapper minted by MiningPoolV1 against a proven Bitcoin output; 1010 base units per satoshi.
S token (FS / CS)
Federation or confederation share token, minted for MP deposited into the MultiPool and redeemable to BTC.
ULR
Governance token with a fixed 10,000,000 supply. Used for staking income, custodian candidacy and stakers' votes.
Federation
Participants holding authorization and Bitcoin key shares through DKG; a t-of-n threshold gates all operations.
Confederation
A federation whose operations also need a custodian threshold for the same operation hash.
Custodian
An admitted ULR holder who independently approves confederation operations. Holds no Bitcoin key share.
Custodian candidate
A staker whose wallet plus stake is at least the threshold H (200,000 ULR by default), eligible for admission.
FROST
Flexible Round-Optimized Schnorr Threshold signatures over secp256k1, producing ordinary BIP340 signatures.
DKG
Distributed key generation. Each participant ends up with a key share; the group key is formed collectively and never exists whole.
EVM_AUTH / BTC_SPEND
DKG purposes: keys that approve EVM operations versus the key that signs Bitcoin transactions.
Operation hash
Target-bound hash of one privileged call: target, selector, parameters and nonce. Approved once, consumed once.
SPV
Simplified Payment Verification: proving a transaction's inclusion with a block header and a Merkle path.
Header relay
Contract that stores Bitcoin headers from a checkpoint, verifies proof of work and retargets, and selects the heaviest chain.
ZK-SPV
Bitcoin header state advanced by succinct zero-knowledge proofs instead of submitting each header.
Fresh
State that is not halted, recently updated and whose canonical tip is recent. Required for minting and settlement.
Halt
Permanent stop of a relay after a reorganization deeper than 100 blocks.
SMP1
Marker in a deposit transaction that commits to recipient, pool, network and distribution for the shared-wallet mode.
Reserve / bind
The two EVM approvals of a payout: reserving its inputs, then binding the exact transaction ID to the withdrawal requests.
Settlement
Escrow step that verifies the confirmed payout and burns the locked S and MP.
Backing
Satoshis recorded per outpoint that stand behind issued MP; moved to wallet change on payout.
Treasury
ULRConfederationTreasury: one per confederation, holds the payout stablecoin and pays stakers daily.
Custody states
ACTIVE, DRAINING, SUSPENDED, COMPROMISED: quorum-controlled issuance status of a deployment.
Registry pinning
A participant's local, one-time binding to the reviewed Bitcoin registry fingerprint before the first Bitcoin signature.
RBF
Replace-by-fee. In SatoshiFi only separately approved replacement versions of the same input set are allowed.
Chapter 17 · References

References and licenses

Academic and standards references

  1. Nakamoto, S. (2008). Bitcoin: A Peer-to-Peer Electronic Cash System.
  2. Komlo, C., & Goldberg, I. (2020). FROST: Flexible Round-Optimized Schnorr Threshold Signatures.
  3. Feldman, P. (1987). A Practical Scheme for Non-interactive Verifiable Secret Sharing.
  4. Groth, J. (2016). On the Size of Pairing-based Non-interactive Arguments.
  5. BIP-340 — Schnorr Signatures for secp256k1.
  6. BIP-341 — Taproot: SegWit version 1 spending rules.
  7. Bitcoin Core consensus code: compact targets, retargeting, block work, median time past.
  8. SEC2 — Recommended Elliptic Curve Domain Parameters (secp256k1).

Dependencies

Auditors and tooling

Licenses

Smart contract code and documentation are distributed under the MIT license (SPDX-License-Identifier: MIT). Some dependencies of the ZK proving toolchain are distributed under GPL terms; the license of a complete prover build follows its components and is not automatically MIT.

Repository and contacts

— FIN —