Motif | Docs
  • Motif
  • Problem: 'Bitcoin Solo Staking?'
  • Size of the Opportunity
  • Solution: Bitcoin staking DTP
    • Staking DTP vs Staking ETP
    • Staking DTP vs LSTs
  • On-chain primary markets
  • On-chain secondary markets
  • User Guide (BitDSM Testnet)
    • How to mint DTP
      • Create New Staking DTP
      • Create BOD
      • Deposit
      • Delegate & Remap
    • How to redeem DTP
      • Undelegate
      • Withdraw
  • SPECIFICATION
    • Intuition
    • What is in-kind remap?
      • In-kind vs wrapped
    • Contract Architecture
    • BitcoinPod Overview
      • Stateless vs Stateful
    • Restaking remap
Powered by GitBook
On this page
  • Native Onboarding
  • Many vaults, Many DTP Tokens
  • Onboarding Staked Bitcoin From Other Protocols

Was this helpful?

  1. Solution: Bitcoin staking DTP

Staking DTP vs LSTs

Native Onboarding

Bitcoin LSTs today are either minted as an ERC-20 bridge token or an ERC-4626 vault contract. This approach either relies on an external protocol for staking assumptions or uses wBTC/cbBTC for minting LSTs/LRTs. However, this method limits the entry point for users who cannot interact with a bridge contract due to regulatory reasons or are not comfortable entrusting custody to a third-party LST issuer. Currently, there is no native onboarding mechanism for Bitcoin holders to Ethereum, where they can run their own node and retain control of their Bitcoin.

Motif's Bitcoin Remap not only provides a way to onboard native Bitcoin into Ethereum staking applications but also enables validators from other Bitcoin L1s/L2s to mint DTPs without relying on an LST issuer. This serves as a gateway to unlock validator liquidity on Ethereum from other L1s/L2s.

Many vaults, Many DTP Tokens

Each vault is a standard ERC7575 that issues its own “share token” (IndexToken1, IndexToken2, etc.). When a user deposits underlying assets into Vault #1, they get IndexToken1; depositing into Vault #2 yields IndexToken2, etc.

Onboarding Staked Bitcoin From Other Protocols

To onboard liquidity from other L2s, validators and stakers can set their L2 Bitcoin unbonding address to a BitcoinPod address remapped on Ethereum. This mirrors the functionality of EigenPods in Ethereum staking, where EigenPods remain empty until the stake is unbonded from the Beacon Chain.

Similar to EigenPods in EigenLayer, BitcoinPods rely on the post-unbonding state of the BOD to enforce custom validation logic for already staked bitocoin in other protocols.

Feature
In-Kind
LST

Ownership

Bitcoin remains native, unwrapped, and under user control.

Bitcoin is locked, and an ERC-20 token is minted as a derivative.

Tokenization

No tokens are issued.

LSTs are issued as synthetic representations of staked Bitcoin.

Custody

Non-custodial; relies on BitcoinPods (BODs) for delegation.

Custodial or semi-custodial setups often required for processing peg-out.

Composability

Primarily designed for delegation via remap.

Highly composable with DeFi protocols as an ERC-20 token.

PreviousStaking DTP vs Staking ETPNextOn-chain primary markets

Last updated 4 months ago

Was this helpful?