Self-Custody BTC Into DeFi
Native Bitcoin into swaps, loans, and LP with your keys on both sides of the flow. Wallet choice, OP_RETURN memo, and the end-to-end mechanics — so you understand exactly what you are signing.
What self-custody looks like in this flow
Every DeFi operation on native BTC — swap, loan, LP — reduces to one thing: a signed Bitcoin transaction with an OP_RETURN memo that tells THORChain what to do. There is no "connect wallet" to a DApp, no session key, and no intermediate custodian. The wallet that signs the transaction is the wallet that holds the BTC; the BTC goes directly to a THORChain vault on the Bitcoin chain.
- One signature per operation — the BTC send is the whole interaction.
- No hot-wallet session — you do not authorize a DApp to act on your behalf over time.
- OP_RETURN carries the instruction — memo tells THORChain which pool, which destination, and which action.
Step-by-step: native BTC to DeFi with your own keys
-
Pick a Bitcoin wallet that can attach a memo
You need a wallet that can sign a standard Bitcoin send and attach an OP_RETURN memo. Sparrow and Electrum both handle this comfortably on desktop; most BTC-compatible hardware wallets sign cleanly when paired with one of those as the host software. Custodial mobile wallets typically cannot attach memos — check before committing.
-
Fund the wallet from your current BTC custody
If your BTC is on a CEX, withdraw to the wallet address you control. If it is already in self-custody, move to the wallet you intend to sign the swap from. Either way, wait for confirmations before starting the swap.
-
Choose the operation — swap, loan, or LP
The self-custody flow is the same shape for all three: you sign a BTC send with a memo that tells THORChain what to do. The memo differs — a swap memo routes the BTC through pools to the counter-asset; a deposit memo on Rujira Money Market records it as collateral; an LP memo on Rujira AMM opens a position in the chosen pair.
-
Construct the transaction in your wallet
The deving.zone or Rujira interface shows the exact inbound address and memo. Paste both into your Bitcoin wallet as the destination and OP_RETURN fields respectively. Review fee rate; Bitcoin miner fee is paid from the same UTXO.
-
Sign and broadcast — this is the only signature
Your wallet broadcasts a single BTC transaction to the Bitcoin mempool. That signature is the whole interaction with DeFi. The counter-leg (stablecoin, loan proceeds, LP confirmation) is delivered by THORChain or Rujira automatically once the BTC confirms.
-
Keep your keys, monitor the outcome
Your signing keys never leave your wallet. The THORChain vault holds the BTC on the Bitcoin chain; your position is visible in the relevant UI against your destination address. Repay, close, or exit any time by signing another transaction — same flow, same key material.
Wallet choices at a glance
Desktop, advanced UTXO management, OP_RETURN support, hardware-wallet pairing. The most common choice for self-custody BTC users moving into DeFi.
Desktop, long-established, OP_RETURN via a text field. Works with most hardware wallets. Good default if Sparrow doesn't fit.
BTC-compatible hardware wallets signing via Sparrow or Electrum. The memo appears on the device screen — verify it before confirming.
Put it into practice
Self-custody BTC → DeFi questions
Does THORChain or Rujira hold my keys at any point?
No. THORChain is a non-custodial cross-chain settlement layer; Rujira is a non-custodial app-layer on top of it. At no point does either protocol hold, custody, or require access to your signing keys. The only signature that happens is the BTC send you construct and broadcast from your own wallet.
What is the OP_RETURN memo actually doing?
OP_RETURN is a Bitcoin opcode that attaches arbitrary data to a transaction. THORChain reads the memo to know what to do with the incoming BTC — which pool to route through, what counter-asset to send, which destination to send it to, or which app-layer action (loan, LP) to perform. The memo is the instruction; the BTC send is the payment.
Can I use a hardware wallet?
Yes. BTC-compatible hardware wallets work when paired with host software that handles memo construction — Sparrow and Electrum both support this flow. The signing happens on the hardware device; the memo is part of the transaction that the device signs. Verify the memo on the device screen before confirming.
What happens if the transaction fails or I make a mistake?
If the BTC transaction itself fails to broadcast, nothing moves — you keep the BTC, pay no fee. If the memo is malformed, THORChain typically refunds the BTC to the sending address minus an outbound fee. If you send to the wrong chain's inbound address, the refund path may not apply — always check the inbound address in the latest interface state before signing.
Is there a "connect wallet" step?
Not in the Ethereum-DApp sense. You do not sign a session key into a web DApp; you build and broadcast one BTC transaction from your own wallet. The web interface generates the inbound address and memo text; your wallet is the thing that signs. That is the main structural difference from EVM DeFi self-custody UX.
Which operations can I do entirely from self-custody?
Swaps to any connected chain; loans against native BTC via Rujira Money Market; concentrated LP positions via Rujira AMM; direct exits to stablecoins. Every one of these reduces to a signed BTC send with the right memo. No hot wallet needs the key; no account is created; no KYC applies.