Building for the future with Bitcoin

The latest from Strike

![](https://www.datocms-assets.com/99305/1746537384-lending-hero.png)

Yo! Today we’re **announcing one of the most powerful features we’ve ever built at Strike: bitcoin-backed loans.**

For the first time, eligible customers can borrow against their bitcoin without selling. Get access to cash using your bitcoin as collateral with fast, flexible loans at market-leading terms. Whether you’re buying a home, investing in your business, or funding your next move, bitcoin-backed loans let you tap into your wealth without giving up your stack.

Borrow between $75,000 and $2,000,000 for up to 12 months, starting at 12% APR with a 0% origination fee, available now in [select U.S. states](https://strike.me/faq/where-are-bitcoin-backed-loans-available).

Bitcoin-backed loans are officially live for all eligible customers. [Get started](https://strike.me/lending).

## Story
Bitcoin now represents roughly [$1.8 trillion in global wealth](https://www.coindesk.com/markets/2025/04/23/bitcoin-becomes-fifth-largest-global-asset-surpasses-google-s-market-cap) making it the fifth largest asset in the world. That’s $1.8 trillion held by people who’ve chosen to store and grow their wealth in bitcoin.

Given its track record, it’s easy to see why. Over the past decade, bitcoin has outperformed every major asset class, delivering [average annual returns of over 80%](https://www.coingecko.com/research/publications/bitcoin-versus-traditional-assets-price-returns?utm_source=chatgpt.com), far ahead of equities, real estate, and gold. Against the dollar, bitcoin has appreciated by more than 60% per year on average.

That kind of performance has shifted behavior. More people are choosing to hold rather than trade. As of April 2025, [63% of bitcoin hasn’t moved in over a year](https://www.tradingview.com/news/newsbtc:a79c88bb3094b:0-bitcoin-long-term-holders-show-conviction-63-of-supply-hasn-t-moved-in-a-year/#:~:text=According%20to%20their%20latest%20analysis,the%20current%20volatility%20without%20panic.), a clear signal of long-term conviction. On Strike, that trend is even stronger: **over 90% of bitcoin bought is withdrawn to cold storage**.

Bitcoin is no longer a speculative bet. It’s a long-term store of value. But until now, accessing that value has meant selling, giving up future upside and triggering a taxable event that eats into your gains. For long-term holders, that tradeoff doesn’t make sense. They want access to the value they’ve built without giving up their bitcoin. That’s exactly what bitcoin-backed loans make possible. We’ve heard this feedback firsthand from our own customers.

![](https://www.datocms-assets.com/99305/1746537925-lending-tweets.png)

**A better way to borrow**

Traditional borrowing has always relied on legacy systems like homeownership, credit scores, and relationships with banks. For decades, people have built wealth by borrowing against their homes. The property stays in their name, continues to appreciate, and the loan helps fund investments or major life expenses.

Bitcoin-backed loans offer a similar model but with more flexibility. You can borrow cash while using your bitcoin as collateral. No selling. No credit check or lengthy approval process. No giving up future upside. And if bitcoin continues to grow faster than your borrowing costs, your asset appreciates faster than your debt. In other words, the gains from holding bitcoin can more than offset the interest on your loan.

It’s a powerful shift. Financial tools that were once reserved for legacy assets are now available to anyone holding bitcoin.

![](https://www.datocms-assets.com/99305/1746549818-lending-bitcoin-performance_2.png)

## Introducing Bitcoin-Backed Loans
Strike now offers bitcoin-backed loans to eligible customers in [select U.S. states](https://strike.me/faq/where-are-bitcoin-backed-loans-available), giving you a simple way to unlock your bitcoin’s buying power without selling.

The experience is designed for Bitcoiners, fast, simple, and intuitive. Post your bitcoin as collateral, receive cash, repay with interest, and get your bitcoin back, all within the Strike app. Easily monitor your loan and manage your collateral every step of the way.

Whether you’re buying a home, investing in your business, or funding your next move, bitcoin-backed loans turn long-term holdings into real-world utility, without giving up your stack.

**Why borrow against your bitcoin?**

* **Keep your bitcoin:** Stay exposed to future upside while accessing cash today.
* **Mitigate taxable impact:** Bitcoin-backed loans typically aren't taxed, but situations like loan liquidations or repaying with bitcoin can trigger taxable events. 
* **No credit checks:** Approval is based on your bitcoin collateral, not your credit score.
* **Fast access to funds:** No lengthy approval processes or appraisals.

[Learn more](https://strike.me/faq/what-are-bitcoin-backed-loans/) about bitcoin-backed loans.

![](https://www.datocms-assets.com/99305/1746539011-hero-3.png)

## Unlock your bitcoin’s buying power

**Borrow at market-leading terms**

Strike offers bitcoin-backed loans from $75,000 to $2 million, starting at a 12% annual percentage rate (APR) for a 12-month term with a max initial loan-to-value (LTV) of 50%. There are no origination fees and no early repayment fees.

You can choose to pay interest monthly or at maturity, and add collateral anytime to lower your LTV. Everything is customizable inside the app. [Learn more](https://strike.me/faq/what-are-the-loan-rates-fees-and-terms/) about our current loan rates, fees, and terms.

Check out [Strike’s Loan Simulator](https://strike.me/lending/) towards the bottom of the page to model your options and pick what works best for you.

Bitcoin-backed loans are now rolling out with a $75,000 minimum. But this is just the beginning. We’re already working on lower rates, the ability to top up existing loans, proof-of-reserves lending, removing loan size limits, and expanding into new markets.

![](https://www.datocms-assets.com/99305/1746550071-01.png)

**Open a loan in minutes**

Opening a bitcoin-backed loan is fast and simple. Apply directly in the Strike app, select your terms, and get approved in minutes. Once approved, your cash is credited instantly and available to withdraw within one business day. Loans are not reported to credit agencies and do not affect your credit score.

**How it works:**

1. **Post bitcoin as collateral:** Use your bitcoin as secure collateral for the loan.
2. **Receive cash:** Cash is delivered to you and your loan begins accruing interest.
3. **Manage your loan:** Track your loan’s health, manage payments, add collateral, or close-out your loan early, all from the Strike app.
4. **Repay your loan:** Either at maturity or via monthly payments, you repay your loan with interest.
5. **Receive your collateral:** Once fully repaid, your collateral is returned to you.

[Learn more](https://strike.me/faq/how-do-i-open-a-bitcoin-backed-loan/) about how to open a bitcoin-backed loan. 

![](https://www.datocms-assets.com/99305/1746538658-lending-confirmation_2.png)

**Your bitcoin, securely held**

When you open a loan, your bitcoin collateral is held by Strike or transferred to one of our trusted capital providers, where it is securely held and not re-hypothecated. This means your bitcoin collateral is never lent-out, shorted, or transferred to any other external third party. [Learn more](https://strike.me/faq/where-is-my-bitcoin-collateral-held/).

![](https://www.datocms-assets.com/99305/1747071772-lending-collateral-status.png)

**Monitor and manage with ease**

Strike’s Loan Center puts you in control. Track your loan health in real time, receive alerts about your loan health, and get priority support, all from the Strike app. Our bitcoin-backed loans experience is designed for clarity, control, and peace of mind. [Learn more](https://strike.me/faq/how-do-i-manage-my-loan-in-my-loan-center/) about how to manage your loan in your Loan Center.

![](https://www.datocms-assets.com/99305/1746539213-lending-loan-center.png)

**Stay invested in bitcoin’s future**

Selling bitcoin means giving up long-term upside and potentially triggering a taxable event. Bitcoin-backed loans let you stay invested while unlocking the value you’ve built. 

Whether you're putting a down payment on a home, investing in your business, or covering a major expense, bitcoin-backed loans give you the freedom to use your bitcoin without giving it up.

![](https://www.datocms-assets.com/99305/1746539269-lending-bitcoin-performance.png)

## Get a bitcoin-backed loan
Bitcoin-backed loans are now available to all eligible customers in [select U.S. states](https://strike.me/faq/where-are-bitcoin-backed-loans-available). If you're eligible, you’ll see the Bitcoin-backed loans card in your app’s Cash tab. Tap it to get started.

Not seeing the card yet? Make sure your app is updated and your account is fully verified. [Get started](https://strike.me/lending).

Prior to opening a loan, check out our [FAQs](https://strike.me/faq/#bitcoin-backed-loans) to familiarize yourself with how bitcoin-backed loans work, including the [Loan-to-Value (LTV) ratio](https://strike.me/faq/what-is-my-loan-to-value-ratio), [how payments work](https://strike.me/faq/how-do-loan-payments-work), and [margin calls and liquidations](https://strike.me/faq/what-are-margin-calls-and-liquidations). 

Additional resources can also be found in our [Learn](https://strike.me/learn/what-are-bitcoin-backed-loans/) resource hub.

![](https://www.datocms-assets.com/99305/1746538658-lending-confirmation.png)

## Bitcoin-backed loans for businesses
We’re excited to announce that we’re beginning to roll out bitcoin-backed loans for businesses over the coming weeks. For businesses, Strike offers bitcoin-backed loans from $10,000 to $2 million, starting at a 12% annual percentage rate (APR) for a 12-month term with a max initial loan-to-value (LTV) of 50%. There are no origination fees and no early repayment fees. [Learn more](https://strike.me/faq/can-my-business-open-a-bitcoin-backed-loan/).

![](https://www.datocms-assets.com/99305/1746538803-lending-business.png)

## Thanks
As bitcoin continues to grow into a global financial asset and more people build real wealth, it deserves financial tools built specifically for it that reflect how people actually use and hold bitcoin today.

At Strike, we’re focused on building that future with real financial tools that provide utility for bitcoiners. With the addition of bitcoin-backed loans, we now support spending, saving, getting paid, and borrowing all through bitcoin.

We wouldn’t be here without our customers. Thank you. Your conviction, your feedback, your belief in bitcoin, and in us, is what drives everything we do. We’re excited to continue this journey with you. 

Until then. Much love.

Jack

https://www.youtube.com/watch?v=PdttkQAZ2BM

––––

*Updated on May 12, 2025, to reflect new information about our bitcoin-backed loan offering: Whether you’re opening a new loan or already have one, your bitcoin collateral is held with Strike or transferred to one of our trusted capital providers, where it is securely held and not re-hypothecated.*

Borrow against your bitcoin without selling, with fast, flexible loans at market-leading terms

Announcing Bitcoin-Backed Loans

**Today, we’re excited to introduce one of the most frequently requested features on Strike: Cost Basis.**

Strike’s Cost Basis gives you clarity on your bitcoin’s performance, simplifies tax preparation, and ensures you have a comprehensive view of your bitcoin holdings and transactions.

Now, you get a complete view of your bitcoin holdings, transactions, and performance, including total return, the ability to view, manage, and edit cost basis lots, tailored insights, and tools to assist with tax preparation.

Cost Basis is now available to U.S. customers on both the Strike mobile app and the [Strike Dashboard](https://dashboard.strike.me/) on desktop.

![](https://www.datocms-assets.com/99305/1755194674-cost-basis-tweets.png)

## Introducing Cost Basis

As Bitcoin’s market cap grows and our customers continue building their wealth on Strike, we set out to build more sophisticated and intuitive cost basis tools tailored to the needs of Bitcoiners. Guided by your feedback, we designed an experience that delivers clarity on your bitcoin’s performance, simplifies tax preparation, and ensures you have a comprehensive view of your bitcoin holdings and transactions.

Our new Cost Basis features offer one of the most comprehensive experiences in the industry. Whether you’re selling for the first time, preparing for taxes, or simply wanting a complete view of your stack’s performance, Strike makes it effortless to track and manage your cost basis.

No more guesswork. No more juggling spreadsheets. Everything you need is built right into Strike. You can now track the cost basis for bitcoin bought on Strike, sent to your external wallet, or transferred into Strike, ensuring you have the information you need to make your tax season organized and free from hours of manual record-keeping.

![](https://www.datocms-assets.com/99305/1755194870-manage-cost-basis.png)

## View your bitcoin’s total return in real-time
We recently introduced a quick way to see how your stack is performing, your average buy price: the weighted average you’ve paid for bitcoin purchased on Strike over time.

Today, we’ve expanded this with total return, which combines:

* Realized return: Gains or losses from bitcoin you’ve sold or otherwise disposed of on Strike.
* Unrealized return: Gains or losses from bitcoin you still hold on Strike. 
For accuracy, these numbers exclude any bitcoin transferred off Strike or with unknown cost basis.

Your total return appears directly below the bitcoin price chart, giving you a snapshot based on your actual cost basis, not just market price.

![](https://www.datocms-assets.com/99305/1755194927-total-return.png)

## Track and manage your cost basis in one place

We’ve brought full cost basis tracking to bitcoin that you hold or transfer on Strike. You can manage it all in the Strike mobile app or on desktop with your [Strike Dashboard](https://dashboard.strike.me/).

The Dashboard’s table view is perfect for reviewing and updating cost basis across multiple transactions. Strike tracks your cost basis in three main tabs within the Cost Basis section of your Dashboard:

* Bitcoin Lots: Bitcoin you bought or received on Strike, with acquisition dates and cost details.
* Transfers Out: Bitcoin you’ve sent to your own external wallet.
* Dispositions: Bitcoin you’ve sold, spent, or gifted. Taxable events, like bitcoin sales, appear in your 1099-B.

Each time you acquire bitcoin, whether by making a purchase, receiving a payment, or getting it as a gift, a new ‘lot’ is created (a record of the amount of bitcoin, the price at acquisition, and the date of the transaction). 

Strike assigns default transaction types based on how your bitcoin was sent or received. You can [review and easily update transaction types](https://strike.me/faq/how-do-i-manage-my-cost-basis/) except for purchases and sales, which are already established, fill in missing cost basis for transfers in, and ensure your records are accurate well before tax season. 

Because every detail matters for keeping track of your bitcoin transactions and preparing for taxes, you can easily edit the following cost basis details right in the Strike app:

* Transfers in (on-chain or Lightning): These are assumed to come from your own external wallet. You can edit the amount, acquisition date, and cost basis, or split the transaction into multiple lots with different acquisition details. They can also be categorized as payments or gifts.
* Transfers out (on-chain or Lightning): These are assumed to go to your own external wallet. You can reclassify them as payments or gifts. Taxable transactions will be moved to your Dispositions tab.
* Transactions to or from Strike users: These are assumed to be payments. These can be categorized as payments or gifts, but not as transfers.

You can export your transaction history anytime from the Activity section of your [Strike Dashboard](https://dashboard.strike.me/).

Learn more about [how to manage your cost basis](https://strike.me/faq/how-do-i-manage-my-cost-basis/) on Strike and [understanding cost basis and bitcoin lots](https://strike.me/faq/what-is-my-cost-basis-for-trading-bitcoin-on-strike/).

![](https://www.datocms-assets.com/99305/1755195198-cost-basis-transfer-in.png)

## Get a clear snapshot of your cost basis with tailored insights

We’ve added tailored insights to each Cost Basis tab on your Dashboard, giving you high-level snapshots that make it easy to see your cost basis at a glance. These metrics update in real time as you review and manage your data, providing a clear, accurate view of your bitcoin activity.

For each tab, you’ll see tailored insights:

* Bitcoin Lots: Unrealized gain/loss, total acquired, total cost basis, and average price.
* Transfers Out: Total transferred out, current value, total transfers, and total destinations.
* Dispositions: Realized gain/loss, total disposed, total cost basis, and value of dispositions.

This feature is currently rolling out to all U.S. customers.

![](https://www.datocms-assets.com/99305/1755194855-tailored-insights-hero-metrics.png)

With Cost Basis, Strike gives you the tools to see the full picture of your bitcoin performance, stay on top of your taxes, and save time. It’s one more way we’re making Strike the best place to buy, sell, and manage your bitcoin.


*Cost Basis is for your informational and organizational purposes only and is not (and should not be interpreted as) tax, legal, investment, or financial advice.*

Seamlessly view, track, and manage cost basis for your bitcoin transactions

Announcing Cost Basis

https://www.youtube.com/watch?v=sgCaNzRMiIs

--

Today, we’re excited to announce a major update to our global app, making it easier than ever for customers around the world to transfer dollars in and out of Strike and buy bitcoin.

[Global customers in over 60 countries](https://strike.me/faq/which-countries-support-transfers-using-usd-bank-accounts/) can now easily deposit funds, buy bitcoin, and withdraw cash faster, cheaper, and more seamlessly than ever before, thanks to Virtual USD accounts. Buying bitcoin has never been easier, no matter where you are in the world.

At Strike, we're committed to making Bitcoin accessible to everyone, everywhere. This update is another important step toward expanding options for our global customers.

## More Ways to Buy Bitcoin

Strike serves customers in over 100 countries. The demand for bitcoin is universal but the rails to get there are broken. In many parts of the world, local fiat payment rails are unreliable, expensive, or don’t exist at all. People are locked out, with no access to trusted exchanges or simple ways to buy bitcoin. We're here to change that. That’s why we’re introducing more flexible, USD-based solutions to make it easier for global customers to buy bitcoin.

With Virtual USD Accounts, [global customers in over 60 countries](https://strike.me/faq/which-countries-support-transfers-using-usd-bank-accounts/) can now deposit funds into their Strike account quickly and easily. Whether you're using a traditional U.S. bank like Bank of America, or a virtual USD account from platforms like Wise, you now have more ways than ever to fund your account.

For customers who don’t have access to a U.S. bank account, virtual USD accounts offer a great alternative. These accounts provide you with a unique routing and account number, so you can deposit funds directly into your Strike account without needing a U.S. bank.

Your funds are automatically credited 1:1 with USD and can be used to buy bitcoin.

Wherever you are, Strike gives you a clear and easy way to deposit dollars, buy bitcoin, and withdraw funds, all without relying on local currency rails.

![](https://www.datocms-assets.com/99305/1752597151-virtual-account-deposits-withdrawals.png)

## Introducing Virtual USD Accounts

We’ve made it simple to move cash into your Strike account, buy bitcoin instantly, and access your funds when you need them. Here’s how it works:

**Depositing Cash**

To deposit funds into your Strike account, simply initiate a push transfer from your USD bank account or virtual USD account. You can do this through ACH or wire transfer. Once received, your funds will be deposited into your Strike cash balance, ready for you to stack.
ACH and wire deposits are free, so you can put more of your cash toward growing your Bitcoin stack. [Learn more](https://strike.me/faq/how-do-i-deposit-cash-wr/) about how to deposit cash into your Strike account.

For large bitcoin orders, reach out to us at private@strike.me.

Once your funds are in your Strike account, you can instantly buy bitcoin with ease. You can manually buy bitcoin and set up DCA from your cash balance, or enable Auto-buy bitcoin. With Auto-buy, your incoming cash is automatically converted into bitcoin as soon as it arrives, no extra steps needed. It's the most effortless way to buy bitcoin. [Learn more](https://strike.me/faq/which-countries-support-transfers-using-usd-bank-accounts/).

![](https://www.datocms-assets.com/99305/1752596925-virtual-accounts-deposits-hero.png)

**Withdrawing Cash**

Need to withdraw cash? It’s just as simple. You can withdraw your funds to your linked USD bank account using ACH, instant transfer, or, for larger amounts, wire transfer. We’ve made the withdrawal process as straightforward as possible, so you can access your funds quickly when you need them. [Learn more](https://strike.me/faq/how-do-i-withdraw-cash-wr/) about how to withdraw cash from your Strike account.

For details about withdrawal minimums, limits, transfer times, and fees see our [FAQ](https://strike.me/faq/which-countries-support-transfers-using-usd-bank-accounts/).

![](https://www.datocms-assets.com/99305/1752597059-virtual-accounts-withdrawal-hero.png)

**Bitcoin your way**

We believe in putting Bitcoin into the hands of more people, which means keeping costs low and offering flexible options to suit your needs.

* **Flexible payment methods:** [More ways for you to move money into Strike](https://strike.me/faq/which-cash-payment-methods-are-available-by-country/), however works best for you. Deposit and withdraw funds from USD bank accounts, virtual USD accounts, USDT wallets (via the TRON network), and local currency bank or mobile accounts. Or, send to local or foreign currency accounts via Send Globally, and Bitcoin or Lightning wallets.
* **Free deposits:** Save on fees and stack more with free ACH and wire deposits. No limits and no fees.
* **Auto-buy bitcoin:** Enabling Auto-buy bitcoin ensures your cash deposits will be automatically converted to bitcoin the moment they arrive in your account, instantly.

## Thanks
Over the years, Strike has grown into a global community of Bitcoin users. As we continue to expand, we remain focused on making it easier for more people around the world to access Bitcoin. This includes adding more countries and payment methods, and exploring support for local currencies.

Thank you for being a part of our global journey.

Deposit funds, buy bitcoin, and withdraw cash faster, cheaper, and seamlessly with Virtual USD accounts

Announcing Virtual USD Accounts Globally

https://www.youtube.com/watch?v=qcYJ795pZ8w

--

Today, we’re excited to announce the launch of Bill Pay for businesses, a new feature that lets you pay bills directly from your Strike Business account using bitcoin or cash. 

From credit card payments and software subscriptions to vendor invoices, Bill Pay makes managing business expenses simpler, faster, and more flexible than ever.

At Strike, we’re building the modern financial stack for businesses. Our platform provides everything you need in one place: get access to checking accounts, buy and sell bitcoin, full-service bitcoin wallet, bitcoin-backed loans, and seamless bill payments in cash or bitcoin all in one platform.

Supercharge your business with superior money.

## Introducing Business Bill Pay

With rising costs, volatile markets, and inflation squeezing margins, businesses today face a critical challenge: how to preserve capital, manage cash flow efficiently, and scale without relying on a weakening fiat system. More companies are turning to bitcoin as a long-term treasury asset, but managing fiat-denominated expenses remains a common friction point.

At Strike, we already help businesses manage their corporate bitcoin treasury. Now, with Business Bill Pay, companies can use their bitcoin holdings to pay fiat expenses, without manual conversions, complex wire transfers, or banking delays.

Until now, settling fiat bills meant selling bitcoin manually, transferring funds to a bank, and waiting days for settlement. Bill Pay eliminates that complexity. Businesses can designate bitcoin as their default payment source, and when a bill is charged, Strike converts and pays the amount in cash. Standard bitcoin trading fees apply to convert to cash, which counts toward your monthly fee level.

With unique account and routing numbers, support for unlimited billers, and built-in tax documentation, Strike makes it easy to handle fiat obligations while you run your business on bitcoin. [Learn more](https://strike.me/faq/what-is-strike-bill-pay/).

![](https://www.datocms-assets.com/99305/1754423131-hero-b-business.png)

## Streamline business payments
**Use your bitcoin or cash balance to pay vendors, service providers, and more**

Strike Bill Pay lets you manage all your fiat payments directly from your Strike account with your unique account and routing numbers. Choose either bitcoin or cash as your default payment source, and let your billers pull funds when payments are due. 

**Getting started**
1. Access Bill Pay: Tap the Account icon and scroll to Bill Pay.
2. Generate payment details: Your unique Strike account and routing numbers are generated instantly in the app.
3. Select your payment source: Choose bitcoin or cash to fund your bill payments.
4. Enter billing details: Input your Strike account and routing numbers into your biller’s payment portal. The name on your bill must match your Strike account.

Payments are pulled from your default balance when due. You can switch between bitcoin and cash at any time. Learn more about [Bill Pay](https://strike.me/faq/what-is-strike-bill-pay) and how to [set it up](https://strike.me/faq/how-do-i-set-up-bill-pay).

![](https://www.datocms-assets.com/99305/1754423205-hero-a-business.png)

## Run your business on bitcoin
**Operate in bitcoin, stay fiat-free**

Bill Pay enables you to hold operating capital in bitcoin and convert only what’s required when fiat payments are due. That means lower exposure to inflation, fewer manual steps, and more flexibility in how you manage your treasury.

Combined with features like bitcoin treasury management, bitcoin-backed business loans, high limits, low fees, and free bitcoin withdrawals, Strike gives your business the tools to operate efficiently on a bitcoin standard.

The best part: Bill payments made with bitcoin count toward your Strike fee tier, reducing your fees on all bitcoin trades, buys, sells, and more.

![](https://www.datocms-assets.com/99305/1754423239-pay-bills-business.png)

## Simplify business tax reporting
**Get the tax documentation your business needs**

Paying bills with bitcoin triggers a taxable event, and Strike makes it easy to stay organized. We provide clear, comprehensive tax documentation, including summaries of bitcoin sales and bill payments from your bitcoin balance. These are available in the app during tax season, helping you and your accounting team stay organized and on top of tax requirements.

![](https://www.datocms-assets.com/99305/1754423265-taxes.png)

## Bitcoin financial services for businesses
Strike offers a full suite of bitcoin financial tools for businesses of any size, helping thousands of companies save and operate in this new monetary era.

Here’s everything Strike Business has to offer: 

* Checking account: Hold USD and use Wire, ACH, and instant RTP transfers from your Strike account.
* Buy and sell bitcoin: DCA, set target orders, or buy and sell bitcoin instantly with transparent, tiered, and cheap fees.
* Bitcoin wallet: Secure multisig cold storage custody, free on-chain withdrawals, and a full-featured Lightning wallet.
* Borrow cash: Bitcoin-collateralized loans as low as 9.5% with no origination fee and no early repayment fee.
* Pay bills: Pay business invoices, credit card bills, utilities, and more directly from your Strike account using your bitcoin or cash.

![](https://www.datocms-assets.com/99305/1754423308-business-financial-services.png)

## Thanks
We're proud to partner with hundreds of businesses that are building on bitcoin. Thank you to all of our incredible customers for your trust and continued support. 
Whether you're holding bitcoin on your balance sheet or using it for daily operations, we're committed to building tools that make it easier to run and grow your business with bitcoin at the core.

Run your business on bitcoin, pay bills seamlessly with Strike

Announcing Business Bill Pay

Today, we're excited to share that **Strike now supports passkeys and security keys for two-factor authentication (2FA), as well as new protected actions**. 

Log in seamlessly with your fingerprint, face, or a physical security key, and add an extra layer of protection to sensitive actions like withdrawals and account changes.

That means more ways to secure your account, without slowing you down from stacking sats.

![](https://www.datocms-assets.com/99305/1750265009-2fa-upgrades-hero.png)

## Log in faster, stay more secure

Passkeys and security keys are a new, more secure way to access your Strike account without the friction. No need to enter your email or password. Simply unlock your app with your fingerprint, face, or a security key.

Switch between passkeys, security keys, and authenticator apps at any time. It’s your choice.

## Extra protection where it counts

With protected actions, you can add extra security to key account activity, not just sign-ins. By default, logging back in will always require 2FA. But now, you can go further and protect:

* Account updates, like changing your phone number
* Sends and withdrawals, including any bitcoin and cash transactions

## How to set up passkeys, security keys, and protected actions

Add an extra layer of security to your account in a few simple steps:

1. Go to your Account screen 
2. Tap Security
3. Tap “Enable 2FA”
4. Select “Passkey or security key”
5. Follow your device prompts to complete set up

Once 2FA is enabled, you can choose which additional actions you'd like to protect with 2FA, all from the same Security screen. Tap the “Manage passkeys” button to add, rename, or remove them. 

You’ll get an email notification whenever 2FA or protected actions are enabled or disabled, so you’re always in the know. [Learn more](https://strike.me/faq/how-do-i-set-up-two-factor-authentication/).

As Bitcoiners, we all play a role in keeping Bitcoin safe. Check out our FAQs about [how to spot scams](https://strike.me/faq/how-do-i-identify-a-scam/) and [what to do if you encounter one](https://strike.me/faq/what-should-i-do-if-i-encounter-a-scam/).

If you ever suspect unwanted activity, please contact support@strike.me.

Secure your account with enhanced two-factor authentication

Announcing 2FA Passkeys, Security Keys, and Protected Actions

https://www.youtube.com/watch?v=RiNdTtdiRhg

__

Yo! I’m excited to announce that the Australian dollar (AUD) is now available for our Australian customers on Strike! 

Australian customers can now buy bitcoin with free and instant AUD deposits, withdraw AUD to Australian bank accounts, access the best of bitcoin and Lightning, and open bitcoin-backed business loans.

To get started, download the Strike app via the [iOS App Store](https://apps.apple.com/app/apple-store/id1488724463) or [Google Play Store](https://play.google.com/store/apps/details?id=zapsolutions.strike).

Wen AUD? Now!

## The Story
At Strike, our vision is simple: give everyone access to bitcoin.

Today, the Strike app reaches over 3 billion people across 100+ countries. Over the past few years, we’ve focused relentlessly on expanding Strike’s availability and the features we offer, offering a simple, secure, and reliable way to buy bitcoin. Our goal is to provide the best platform for bitcoin financial services, empowering people to take control of their financial future through bitcoin.

We’ve heard from Australian customers who value Strike’s simplicity and bitcoin-only focus, and they’re looking for better access to buy bitcoin in their local currency.

With the launch of AUD, we’re taking the next step in making bitcoin even more accessible.

![](https://www.datocms-assets.com/99305/1754606542-cash-bitcoin.png)

## Introducing AUD

We’re excited to offer Australian customers the ability to fund their account in AUD and seamlessly use it to buy bitcoin. 

If you’re an Australian customer, here are a few things you can now do with Strike:

* Buy bitcoin directly with free, unlimited AUD deposits from your bank account
* Sell bitcoin and withdraw the funds directly to your bank account
* Withdraw bitcoin to self-custody or send it to any bitcoin or Lightning wallet instantly
* All of our market-leading bitcoin and Lightning wallet features, like free on-chain withdrawals, Lightning Address payments, and zero-value invoices
* Open a bitcoin-backed business loan

**Deposit and withdraw AUD, for free**

Buying bitcoin is easy with Strike. Now, you can deposit AUD into your Strike account with free, unlimited bank deposits, and withdraw AUD just as easily. 

Deposit AUD into Strike using NPP or Direct Entry also known as “direct debit”, from your bank account. Funds are deposited within two business days with direct debit or as fast as a few seconds if your bank supports NPP. Deposits are free and unlimited. [Learn more](https://strike.me/faq/how-do-i-deposit-cash-au/) about deposits.

You can instantly buy bitcoin with ease, using your AUD balance. You can manually buy bitcoin and set up recurring bitcoin buys from your cash balance, or enable Auto-buy bitcoin. With Auto-buy, your incoming AUD is automatically converted into bitcoin as soon as it arrives, no extra steps needed. It's the most effortless way to buy bitcoin.

![](https://www.datocms-assets.com/99305/1754606542-deposit-showcase.png)

Withdraw AUD from your Strike Account to your own Australian bank account. Withdrawals arrive within two business days with direct debit or as fast as a few seconds if your bank supports NPP. [Learn more](https://strike.me/faq/how-do-i-withdraw-cash-au/) about withdrawals.

![](https://www.datocms-assets.com/99305/1754606542-withdrawal-showcase.png)

**Buy bitcoin instantly with no limits**

We know that our customers want a trusted platform to buy and sell bitcoin with no limits, and Strike offers just that. We’re happy to accommodate a range of order sizes. For larger bitcoin purchases, contact private@strike.me to arrange a custom order.

**No-fee recurring purchases**

Buy bitcoin on your schedule with no-fee recurring purchases, also known as dollar-cost-averaging or DCA. Buy hourly, daily, weekly, bi-weekly, or monthly, with no fees after the first week for hourly and daily purchases, or after the second purchase for weekly and monthly purchases.

[Learn more](https://strike.me/faq/how-do-i-set-up-a-recurring-purchase) about recurring purchases.

![](https://www.datocms-assets.com/99305/1754606542-dca-showcase.png)

**Free on-chain withdrawals**

Strike offers on-chain withdrawals with different delivery speeds. Choose from priority, standard, or flexible withdrawal options based on your needs. Flexible withdrawals are free of charge, so you can withdraw bitcoin to self-custody at no cost.

![](https://www.datocms-assets.com/99305/1754606542-free-on-chain-withdrawals-showcase.png)

## The Best of Bitcoin and Lightning

Strike offers all the best bitcoin and Lightning wallet features in one app:

* Send and receive bitcoin with your Lightning Address: Every Strike user has a unique Lightning Address that allows you to send or receive bitcoin, instantly, using the Lightning Network.
* Send and receive bitcoin using zero-value Lightning invoices: Send any bitcoin amount from your Strike account, instantly, using the Lightning Network.
* Protect your account with enhanced security: Strike offers enhanced security features to protect your account, including 2FA passkeys, security keys, and protected actions.
* Dedicated support from real people: Get quick, reliable assistance from our support team to resolve any issues or questions, ensuring a seamless experience with bitcoin and Strike.

![](https://www.datocms-assets.com/99305/1750265009-2fa-upgrades-hero.png)

## Refer a friend, stack fee-free
We love the bitcoin community, and we’re excited to enable our referral program for Australian customers!

Refer a friend to Strike, and you can both stack up to A$500 fee-free when they join and make their first bitcoin purchase. Your fee-free benefit applies immediately to your next A$500 worth of bitcoin trades, whether buying or selling. And, there’s no limit to how many friends you can refer to Strike. [Learn more](https://strike.me/faq/what-is-the-strike-referral-program-au/) about referrals.

![](https://www.datocms-assets.com/99305/1754606543-referrals.png)

## Bitcoin-backed business loans

**Borrow against your bitcoin at market-leading terms**

Strike now offers bitcoin-backed business loans for companies registered in Australia. Get a bitcoin-backed business loan from $5,000 for up to 12 months. Rates start at 10.5% APR with no origination fees and no early repayment fees. Pay interest monthly or at maturity, and add collateral anytime to lower your LTV. Easily customize your loan inside the app. Your bitcoin, your terms. [Learn more](https://strike.me/faq/what-are-the-loan-rates-fees-and-terms-wr).

To access loans greater than $5 million, reach out to our white-glove team at private@strike.me. 

**Open a loan in minutes** 

Apply directly in the Strike app, select your terms, and get approved in minutes. Cash is credited instantly and available to withdraw within a few business days. No credit check required. [Learn more](https://strike.me/faq/how-do-i-open-a-bitcoin-backed-loan-wr/). 

**Manage your loan with ease**

Strike’s Loan Center puts you in control. Track your loan health, get real-time alerts, and access priority support, all from the app. [Learn more](https://strike.me/faq/how-do-i-manage-my-loan-in-my-loan-center-wr). 

**Your bitcoin, securely held**

When you open a loan, your bitcoin collateral is held by Strike or transferred to one of our trusted capital providers, where it is securely held and not re-hypothecated. [Learn more](https://strike.me/faq/where-is-my-bitcoin-collateral-held/).

**Open multiple loans**

Open up to five bitcoin-backed loans at a time. Multiple loans give you greater flexibility and control. Borrow for different goals, access more liquidity, and manage each loan independently. [Learn more](https://strike.me/faq/can-i-open-multiple-loans-wr). 

![](https://www.datocms-assets.com/99305/1753907135-wr-lending-hero-2.png)

## Getting started

To get started, download the Strike app via the [iOS App Store](https://apps.apple.com/app/apple-store/id1488724463) or [Google Play Store](https://play.google.com/store/apps/details?id=zapsolutions.strike). Then, open the app, tap the “Sign Up” button, and follow the steps in our FAQ. Signing up only takes a few minutes!

[Learn more](https://strike.me/faq/how-do-i-sign-up-for-an-account-au/) about how to sign up for a Strike account. 

## Thanks

Today marks another milestone in our global journey, but there’s much more to come. We will continue to enter new markets, expand our services, and build new features that add utility to bitcoin.

Bitcoin is the greatest innovation of our lifetime, and our ambition is to be the best at giving you access to this transformative technology and a better bitcoin experience globally.

Thank you for your support, we wouldn’t be here without you. Please keep reaching out, we love hearing from you and learning how we can make Strike the best it can be.

Until then, much love.

Jack

AUD balances, instant bank deposits, withdrawals, and bitcoin-backed business loans

Announcing the Australian Dollar on Strike

Make your move into bitcoin.

Blog

Agent workflows are messy. Every provider has a different way to store skills, rules, MCP configs, commands, subagents, and hooks. We think agents should be a tool choice, not a lock-in. Environments should work the same locally and in the cloud, whether you're using GitHub Copilot, Claude Code, or Gemini.

Agent Playground is our reference template for portable agent environments. It standardizes configuration, tool access, and setup so you can define once and run with parity everywhere.

https://github.com/LN-Zap/agent-playground

## Design principles

We had a few non-negotiables:

- **Portability over lock-in** - engineers can use the tool that fits their job.
- **Single source of truth** - configs defined once and only once.
- **Reproducibility** - local, CI, and cloud share the same environment.

If a new agent harness shows up tomorrow, we should be able to add it without rewriting everything else.

## How it works

### 1. Centralized config with rulesync

[rulesync](https://github.com/dyoshikawa/rulesync) lets us store skills, rules, MCP configuration, commands, subagents, and hooks in a provider-agnostic format.

![](https://www.datocms-assets.com/99305/1771601602-agent-playground-rulesync.jpg)

A single config declares the agent targets to support and the remote skills to pull in.

```json
{
  "targets": [ "copilot", "claudecode", "opencode" ],
  "features": [ "mcp", "rules", "skills", "subagents" ],
  "sources": [ {
    "source": "https://github.com/anthropics/skills",
    "skills": [ "skill-creator" ]
  } ]
}
```

The outputs are regenerated deterministically from source.

```text
.
├── rulesync.jsonc    # Config
├── rulesync.lock     # Lockfile
└── .rulesync/        # Canonical source
    ├── mcp.json      # Shared MCP
    ├── rules/        # Project rules
    └── skills/       # Pinned skills
```

### 2. Pinned skills via lockfiles

Pulling unpinned remote code is a security risk. We upstreamed lockfile support to rulesync ([PR link](https://github.com/dyoshikawa/rulesync/pull/1032)) to pin installs to specific commit hashes.

A `rulesync.lock` file keeps the environment reproducible:

```json
{
  "lockfileVersion": 1,
  "sources": {
    "anthropics/skills": {
      "requestedRef": "main",
      "resolvedRef": "1ed29a03dc85...",
      "resolvedAt": "2026-02-17T09:49:59.986Z",
      "skills": {
        "skill-creator": {
          "integrity": "sha256-e141..."
        }
      }
    }
  }
}
```

When we update a skill, the workflow is deliberate:

1. Run `rulesync install --update` to fetch code and update lockfile.
2. Review the diff in the "curated" source directory during the PR process.
3. Merge only after vetting the upstream code for security issues.

This makes the agent supply chain as auditable as the rest of our stack.

When we run in cloud environments, the workflow is deterministic:

1. Run `rulesync install --frozen` to pull reviewed, locked code.
2. The process aborts if the sources drift from the lockfile hashes.

This ensures zero drift between local vetting and cloud execution.

### 3. Unified MCP via rulesync

We maintain a central MCP server configuration within the rulesync source. rulesync then syncs this config to every target. Since tool access is defined once, agents keep the same capabilities even when you swap harnesses.

### 4. Reproducibility

We use [devenv](https://devenv.sh/) to ensure the toolchain is identical everywhere. `npm install` runs a frozen rulesync install and regenerates outputs. Setup is automatic via [direnv](https://direnv.net/) - simply changing into the repo bootstraps the environment.

### 5. Prebuilt Cloud Agents

Complex environment setup steps can be slow and cumbersome for cloud agents to run every time. We use `devenv` as the single source of truth to easily prebuild runner images for the GitHub Copilot coding agent (see [devenv-actions](https://github.com/LN-Zap/devenv-actions)).

The action outputs a Docker container that the GitHub Copilot coding agent uses as its environment. By prebuilding the image, we get super fast start-up times for the cloud coding agent, and we guarantee it has the exact same consistent environment we use locally.

We also use `devenv` to generate [Dev Container](https://containers.dev/) specs and use those to generate prebuilt images. That enables us to use the same fully set up coding environment with cloud-based IDEs such as [GitHub Codespaces](https://github.com/features/codespaces).

## Agent Playground at Strike

We run a shared Agent Playground that extends the template with our own skills, MCP servers, and custom agents. Every engineer can pull an environment that knows our internal patterns and connects to our stack.

Engineers bring their own API keys and OAuth credentials. Secrets stay off shared machines and align with individual permissions. Product teams use the same pattern in their own repos, keeping their agent capabilities portable and reproducible.

It's worth noting that Agent Playground is a collection of patterns, not an all-or-nothing framework. While adopting the entire stack (rulesync, lockfiles, devenv) yields the best results, teams can adopt these practices incrementally. You can start by just centralizing your Agent Skills and MCP configs, and add reproducible environments later.

## Standards or bust

Agent tooling shifts too fast for proprietary lock-in. Every new harness brings a unique config format and manual setup cost. That fragmentation slows down engineers.

We advocate for open, vendor-agnostic standards. A shared convention like [AGENTS.md](https://agents.md/) beats a pile of `CLAUDE.md` and `GEMINI.md` files. Your agent system should be bigger than your tool choice.

We aim to treat environments as first-class citizens: portable, reproducible, and tool-blind. Portability pays off. It helps us stay fast as the field evolves.

## Join us

We build this kind of infrastructure every day at Strike, and we think it matters. If you want to go deep on agent systems, developer tooling, and the primitives that make AI actually production-ready, take a look at our open roles.

Apply here: https://job-boards.greenhouse.io/strike

Portable, vendor-agnostic agent environments

Agent Playground

We have been working hard to help bitcoiners acquire more bitcoin in exchange for their fiat. For DCAs and direct deposits, we charge no fees. For one-time or target orders, we offer transparent fee tiers. Now, we are optimizing order routing with our liquidity providers.

## How Strike helps customers tap global liquidity 24/7

When you buy bitcoin on Strike, you’re not buying our bitcoin, because we never sell our holdings. Instead, your order is filled by one of our external liquidity providers. These are large market-making firms that supply buy and sell quotes across the Bitcoin ecosystem. Most exchanges and brokerages rely on a shared pool of liquidity filled by the same handful of providers.

Think of liquidity providers as the always-on counterparties that make the market function. If someone is selling bitcoin on one venue, a liquidity provider may step in to buy it, then hedge or offload that position on another venue. They stitch the global market together.

This is what enables your orders on Strike to execute instantly, at any time of day, any day of the year. Without liquidity providers, you’d be waiting for another human to match your trade.

### Does Strike charge any hidden fees or artificial spreads?

[We transitioned to our current tier-based fee structure in February 2024.](/blog/from-spreads-to-fees-simple-transparent-and-cheap-pricing-for-bitcoiners/) Since then, [the fees you pay](/faq/what-are-the-bitcoin-trading-fees-on-strike/) are displayed on the confirmation screen before you confirm a trade.

![](https://www.datocms-assets.com/99305/1763764585-introducing-smart-order-routing-more-bitcoin-for-your-cash-fee-tiers.png)

If you tap to buy and see $89,047.20, and tap to sell and see $88,652.48, that’s expected. We regularly request live quotes from our liquidity partners and offer the best possible prices. The $394.72 gap between them is not a fee charged by Strike.

Providing liquidity isn’t free. The buy price is always higher than the sell price because this spread allows liquidity providers to fund their operations and be available as a counterparty for your trades at any time. These firms operate sophisticated infrastructure, manage inventory risk, and quote prices across dozens of regions and currencies. They make money by quoting a spread: selling bitcoin slightly above the price at which they’re willing to buy it. That spread is their revenue for making markets efficient and reliable at scale.

![](https://www.datocms-assets.com/99305/1763768028-introducing-smart-order-routing-more-bitcoin-for-your-cash-posts.png)

### Why does Strike show different Bitcoin prices on various screens?

Bitcoin doesn’t have a single, global price. You buy at the price a seller is willing to offer, and you sell at the price a buyer is willing to pay. Strike’s role is to ensure you’re always matched with the liquidity provider willing to sell to you at the lowest price or buy from you at the highest price. Whether you’re buying or selling, we’re constantly searching for the most competitive quotes we can find. That way, you get more sats for every dollar you spend, and more dollars for every sat you sell.

When you first open Strike, you might buy or sell bitcoin, but we don’t know which. To avoid confusion, we show a single midpoint price on the home screen: the average of the best buy and sell quotes we get from our liquidity partners.

For example, if the best buy quote is $89,047.20 and the best sell quote is $88,652.48, the midpoint is $88,849.84. When you actually tap Buy or Sell, you’ll see the real quote for that action. In this example, that means only a $197.36 move from the homepage price in either direction, instead of a full $394.72 swing. Showing the midpoint keeps the homepage neutral, consistent, and easier to understand.

![](https://www.datocms-assets.com/99305/1763760455-introducing-smart-order-routing-more-bitcoin-for-your-cash-price-screens.png)

## How smart order routing provides better prices to Strike customers

Strike has invested in integrating with multiple high-quality liquidity providers to ensure redundancy and competitive execution. However, during periods of high volatility, buy-side and sell-side demand can become unbalanced. When more people want to buy than sell (or the opposite), the bid/ask spread naturally widens throughout the entire market. Neither Strike nor our liquidity providers are “profiting more” during these times. This is simply how market microstructures behave under stress.

Wider spreads can materially affect user experience: a buyer trying to “catch the dip” may suddenly see bitcoin priced thousands of dollars higher than someone selling at the same time. This is a problem we set out to reduce.

![](https://www.datocms-assets.com/99305/1763769761-introducing-smart-order-routing-more-bitcoin-for-your-cash-post.png)

With our new smart order routing system, every time you place a buy order, we request a real-time quote from each of our connected liquidity providers. Conceptually, we’re asking each one: “A user wants to buy $100 of bitcoin. How many sats can you deliver right now?”

Each provider responds with a quote, and those quotes are often different. Smart order routing automatically selects the best quote (the one that gives you the highest number of sats per dollar) and executes your trade against that venue. The same logic applies when you sell: we choose the provider offering the highest price for your bitcoin.

We’ve effectively created real competition among our liquidity providers. Those quoting wide spreads will naturally lose flow to providers offering tighter markets. As a result, spreads should compress over time, and you’ll see better pricing on both buys and sells.

This system improves execution quality in both calm markets and high-volatility conditions, reducing the impact of temporary liquidity imbalances and ensuring you always get more bitcoin for your cash.

![](https://www.datocms-assets.com/99305/1764087623-strike-live-price-quotes.gif?fm=gif)

Smart order routing is enabled for all our fiat and USDT trading pairs. It provides you with the best quote not only when you buy or sell but also when you pay bills with bitcoin or convert part of your salary through a direct deposit. There is nothing you need to do to enable it, and we don’t charge you anything extra for it. There are no gimmicks, tricks, schemes, or artificial spreads, just a healthy obsession with delivering you as many sats as we possibly can whenever you need them.

## How Strike improves trading prices, redundancy, and reliability

Smart order routing is one part of a broader effort. We’re continually exploring new ways to improve execution quality: expanding our network of high-quality liquidity providers, adding new regions and payment methods, and building features that help you grow your strategic reserve.

Strike has come a long way. In our earliest days, we relied on simple, single-path integrations that could be brittle under load or during market volatility. Over the years, we’ve evolved those systems into one of the most robust trading engines in the industry: fault-tolerant, globally distributed, and capable of sourcing competitive prices across multiple venues in real time. Exchange is core to our mission, and as long as our users care about acquiring bitcoin efficiently, we’ll continue investing heavily in making it faster, more reliable, and more cost-effective.

If you haven’t bought Bitcoin with Strike yet, [give it a try](https://strike.me/download). If building systems like this sounds exciting to you, we’re hiring. Check out our open roles and consider [joining the team](https://strike.me/careers/).

We’ve upgraded our systems to provide better pricing for buys and sells

Introducing Smart Order Routing: More Bitcoin for Your Cash

At Strike, we're constantly innovating to push the boundaries of Bitcoin and the Lightning Network (LN) and enhance our customers’ experience. Today, we're excited to announce our support for [BOLT 12 Offers](https://bolt12.org/), a revolutionary technology that enables a more private, versatile, and user-friendly way to send and receive sats over the Bitcoin Lightning Network.

This blog post dives deep into our journey of integrating BOLT 12 into Strike. It's a technical exploration targeted towards both Bitcoin enthusiasts and our valued customers.


## What is BOLT 12?

Introduced in September 2020 by [Rusty Russell](https://x.com/rusty_twit), the [BOLT 12 specification](https://github.com/lightning/bolts/blob/f150782106ac604b8bb056dcd0c0cbe757274e1d/12-offer-encoding.md) provides an improved version of the current [BOLT 11 standard](https://www.bolt11.org/) for LN payments. If you’re familiar with [LNURL](https://github.com/lnurl/luds) - which Strike also supports! - then BOLT 12 should sound familiar on the surface. It enables features that significantly enhance the LN experience:

* **Reusable QR Codes:** Unlike BOLT 11 Invoices, which are generally single-use, BOLT 12 Offers can be scanned and paid multiple times. This makes them ideal for static displays like on websites, flyers, or billboards, eliminating the need to constantly generate and distribute new invoices.
* **Enhanced User Security:** BOLT 12 leverages [onion messages](https://rusty-lightning.medium.com/onion-messaging-in-depth-d8e384ee4184), a cryptographic technique that conceals the path taken by payments within the LN. This improves the personal security of LN payments through increased privacy.
* **Advanced Functionality:** BOLT 12 opens doors for new native functionality like refunds or ATM-style withdrawals that were previously impossible on the Lightning Network without the use of supplementary layers such as LNURL.


## Our BOLT 12 Implementation Journey

Our exploration of BOLT 12 began with an internal research paper that we wrote back in September 2021. We were intrigued by the potential benefits that BOLT 12 had to offer for improved LN payment experiences.

We devised plans for integrating BOLT 12 functionality into Strike, but the early stage nature of the proposal at that time, the fact that it would be a long time before it would be [implemented into LND](https://github.com/lightningnetwork/lnd/issues/5594), combined with various other factors forced us to refocus efforts on other core functionality and play a wait-and-see game to give time for things to further evolve.

Between 2021 and 2022 members of the Bitcoin community continued to iterate on the BOLT 12 proposals, develop implementations, and champion the technology. Whilst some Lightning node implementations were quick off the mark to integrate, [LND](https://github.com/lightningnetwork/lnd) - the primary node implementation that we use at Strike -  took a more cautious and deliberate approach, focusing more on core system stability. The Lightning Labs team developed a comprehensive phased roadmap to implementing BOLT 12, integrating some of the fundamental building blocks bit by bit over a longer period of time. To this day, LND still does not support BOLT 12 though it does now support many of the core component parts and is well on the way to full native BOLT 12 support.

Upon the arrival of [LNDK](https://github.com/lndk-org/lndk) in March 2023, a tool spearheaded by [Carla Kirk-Cohen](https://github.com/carlaKC) and developed in conjunction with the [Spiral](https://spiral.xyz/) team, our interest in BOLT 12 was rekindled. Described as "An experimental attempt at using [LDK](https://lightningdevkit.org/) to implement BOLT 12 features for LND”, it essentially plugs into LND's existing APIs, enabling use of LDK’s built-in BOLT 12 support with LND.


## Technical Deep Dive

The integration involved several key components:

* **LND:** The gRPC API exposed by the target LND node built with the appropriate rpc subservers.
* **LDK:** Imported as a dependency in our application layer to provide BOLT 12 Offer encoding and decoding.
* **LNDK:** While LNDK’s [architectural overview](https://github.com/lndk-org/lndk/blob/master/ARCH.md) playfully refers to LNDK as "Frankeinstein's monster," it’s actually a very clever solution. LNDK acts as a [shim](https://en.wikipedia.org/wiki/Shim_$computing$), leveraging LDK's modular lightning library and connecting it to LND's gRPC API. This allowed us to reuse the existing BOLT 12 implementation within LDK.


## LNDK At a Glance

LNDK, the clever bridge that enables Strike to leverage BOLT 12 functionality within our existing LND infrastructure, deserves a closer look. Here's a high-level overview of its architecture and some key functionality that made it the tool of choice for our integration.


## Modular Design for Flexibility

As mentioned earlier, LNDK acts as a shim, connecting LND's gRPC API with the modular Lightning library from LDK. This design offers several advantages:

* **Component Reusability**: By leveraging LDK's existing BOLT 12 implementation, LNDK avoids the need to reinvent the wheel. This streamlines development and ensures compatibility with the broader Lightning Network ecosystem.
* **Clear Separation of Concerns:** The separation between LND's core functionality and LDK's BOLT 12 support provides a relatively clean implementation which simplifies some elements of maintenance.


## Onion Messaging and Offer Payments

One of the core functionalities of BOLT 12 is its use of [onion messages](https://rusty-lightning.medium.com/onion-messaging-in-depth-d8e384ee4184). These cryptographic messages enable two nodes on the Lightning Network to communicate securely and privately.

The following diagram depicts how the various components interact from a high level:

![](https://www.datocms-assets.com/99305/1722267398-engineering_09-02-onion-diagram.png)

Here's a simplified breakdown of how Strike uses LND, LDK and LNDK to facilitate onion message routing and the BOLT 12 protocol:

1. **Payment Request:** The Strike user initiates a payment by scanning a BOLT 12 Offer QR code or entering a human readable DNS address from where a BOLT 12 Offer can be fetched using [BIP 353](https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki).

2. **LDK Offer parsing:** LDK is used to parse the BOLT 12 Offer to extract payment details.

3. **Onion Message Construction:** LNDK utilizes LDK's libraries and LND’s gRPC APIs to construct onion messages containing the invoice request details.

4. **Relaying the Onion:** The constructed onion message is then relayed through the Lightning Network by LND, traversing various nodes until it reaches the destination node specified in the Offer, where the onion message is unwrapped, revealing the request embedded in the message.

5. **Retrieving a Blinded Path:** The destination node uses onion messaging to send back an Invoice that includes a blinded path detailing how it can be paid.

6. **Sending the Payment:** LNDK interacts with LND's gRPC API to initiate the payment process.

The following diagram depicts the payment flow from a high level:

![](https://www.datocms-assets.com/99305/1722267427-engineering_09-03-offers-flow.png)


## Phased Implementation Plan (3 Phases):

Given the number of moving parts, we started by outlining a three-phased approach to roll out BOLT 12 functionality within Strike. At a high level, the plan was as follows:


1. **LNDK Testing and Deployment**  
  Establish core BOLT 12 infrastructure and functionality for internal testing and observation.
2. **LNDK Platform & API Integration**  
  Extend Strike's platform and APIs to expose BOLT 12 functionality throughout our environment.
3. **Strike Apps Integration**  
  Integrate BOLT 12 payment features into the Strike products.

By following this phased approach combined with insights from our earlier investigations, we felt we could ensure a controlled and efficient integration of BOLT 12 functionality within Strike.


## Proof of Concept Implementation

The first step was to go from concept, to proof of concept and there were a number of technical hurdles we had to overcome along the way.

**BOLT 12 Playground**  
We established a development environment for testing BOLT 12 payments using various combinations of nodes (LND, CLN, Eclair, and LDK-Node) and channels (direct, single hop, multi-hop, cross-implementation). We chose to open source our new [BOLT 12 Playground](https://github.com/LN-Zap/bolt12-playground) to make it available to the wider development community. This playground proved invaluable for streamlining the testing process and facilitating collaboration.

**API Integration**  
We worked closely with the Spiral team and LNDK contributors to enhance LNDK with a gRPC server and TLS implementation that provided a well-defined and secure interface for our application to interact with the underlying BOLT 12 functionality exposed by LNDK.

**Native BOLT 12 Decoding**  
We leveraged [LDK's generated C# bindings](https://github.com/lightningdevkit/ldk-garbagecollected) to enable BOLT 12 Offer and Invoice decoding directly within our .NET codebase, enabling us to limit our interactions with the LNDK daemon in favour of native code paths where possible.

**Onwards...**  
Within a few days, we had a functional proof of concept demonstrating the ability to pay BOLT 12 Offers directly from our Strike backend systems. With this success, we were confident in moving forward with productionizing the solution.


## From Proof of Concept to Production

The next - and certainly more time consuming - challenge involved transforming the proof of concept into a robust and secure system ready for real-world use within Strike's production environment. Here, we provide some insights into that effort:

**Productionizing LNDK**  
We actively participated in shaping many features of LNDK to ensure it met our requirements and had the flexibility needed to be used in our production environment. This involved several iterations on the design, ultimately resulting in a gRPC interface secured by TLS and leveraging a tightly scoped LND macaron for authentication. We also added more granular endpoints for each phase of the BOLT 12 flow.

**Challenges and Workarounds**  
Working closely with the LDK and LNDK developers, we were able to address issues that we found along the way, helping to bring these libraries to a stable state. Multiple new releases of LNDK, LDK, and the LDK C# bindings were cut along the way, until we had all of the necessary functionality working as we needed.

**Infrastructure Deployment**   
For each LND node that we run, we deployed a LNDK sidecar, ensuring each LND instance has a dedicated LNDK counterpart for handling BOLT 12.

**Onion Messaging Support in LND**  
Our LND nodes were running on version 0.17, which lacked built-in support for onion messaging - a critical component for LNDKs BOLT 12 functionality. As we weren't ready to upgrade to LND v0.18 at the time, we opted to backport the relevant changeset from v0.18 to v0.17. This ensured compatibility with BOLT 12 while maintaining stability within our existing infrastructure. In the process, we were able to help shape the LND 0.18 release (which was in its final RC phase at the time), ensuring that it shipped with [everything needed to support onion messages](https://github.com/lightningnetwork/lnd/pull/8744) out of the box, simplifying the process for other node operators in the future.

**Production-Ready Application Code**  
Our proof-of-concept code underwent a significant transformation. The codebase was broken down into smaller, more focused components. This improved maintainability and facilitated a smoother integration with Strike's existing architecture. At a high level, this comprised of:

- Adding supporting libraries like a BOLT 12 Parser, a [DNSSEC](https://http-dns-prover.as397444.net/) implementation for secure DNS lookups, and a gRPC facade for interacting with the LNDK gRPC server.
- Integrating with our existing LND node pool for managing LND node connections and distributing load across our systems.
- Finally, integrating the entire solution with our core systems, APIs, and business and consumer products to enable BOLT 12 payments from Strike!


## Strike's BOLT 12 Future

Whilst we have successfully achieved our goal of enabling BOLT 12 payments from Strike, our initial integration only supports a basic Offer payment flow. However, it paves the way for exciting and more advanced BOLT 12 features over time.

We're committed to staying at the forefront of Bitcoin and Lightning Network innovation. We'll continue to work with the broader community to push the boundaries and provide you with the best possible experience.

We hope this blog post provides an interesting look behind the scenes of our BOLT 12 integration journey! As you can see, in our case the implementation took a fair amount of work given we were trailblazing and helping to develop LNDK in the process. However, with much of this groundwork now done and out there in the open source universe, we’ve proven that there is a viable path to deliver a BOLT 12 experience with LND, today.

If you'd live to give it a try, you can donate to the [Human Rights Foundation](https://hrf.org/)'s BOLT 12 Offer by scanning the QR Code below, or by paying to their BOLT 12 Lightning Address - [bolt12@hrf.org](lightning:bolt12@hrf.org)
![](https://www.datocms-assets.com/99305/1723462840-hrf-bolt12.png)

We’re excited to see the continued evolution of BOLT 12 as more services and node operators upgrade over the coming months and years.

If you have any questions, feel free to reach out to us!

A Look Behind the Scenes

Building BOLT 12 into Strike

Strike has a mission to onboard the world to better money. The services we have built are designed for fast, low-cost, and seamless payments over the Bitcoin network. One of the core techniques we leverage to achieve this is batching bitcoin on-chain payments. 

![](https://www.datocms-assets.com/99305/1721871514-batching-on-chain-sends-hero.png)


In this article, we'll explore how our on-chain batching system operates, the nuances that make it effective, and some of the technical challenges we've overcome to ensure our users receive top-tier service.


## Tiered On-chain Payment Services<a id="tiered-on-chain-payment-services"></a>

At Strike, we offer a [tiered service](https://strike.me/faq/can-i-speed-up-my-bitcoin-send/) for sending on-chain payments:

- **Flexible (Free) Tier**: For those willing to wait 12-48 hours

- **Standard Tier**: For faster, but affordable sends

- **Priority Tier**: For transactions that cannot wait, targeting confirmation in the next block

This tiered approach allows us to cater to different user needs and preferences, balancing cost and speed effectively. Offering both unlimited free on-chain sends and next-block transactions to all our users poses a bevy of technical challenges. We need a system that can scale to a very large number of users, perform on-chain payments at enterprise-level volumes, keep fee costs affordable, and cleverly utilize the liquidity in our hot wallets.


## The Efficiency of Batching<a id="the-efficiency-of-batching"></a>

![](https://www.datocms-assets.com/99305/1722970393-batching-efficiency-visualization.png)

Batching multiple payments into a single large transaction significantly reduces our on-chain footprint and mitigates some of our scaling challenges. This approach benefits not only our users but also the Bitcoin community by minimizing the data usage of our transactions, thereby reducing network congestion and fees. It also means that one of our [UTXOs](https://strike.me/learn/what-is-a-utxo) (unspent transaction outputs, sometimes referred to as “coins”) can be used to facilitate several on-chain payments for our users, which is crucial for scaling our operations.


## Cost Savings through Batching<a id="cost-savings-through-batching"></a>

By batching payments, we can offer cheaper on-chain sends compared to what users would pay if they were to send transactions individually. On the Bitcoin network, you pay for the data size of your transaction, rather than its financial value. The savings of batching stem from the reduced byte size of batch transactions compared to publishing multiple individual transactions. All on-chain transactions contain both fixed and variable data. The fixed data includes information that is standard for all transactions, whereas the variable data includes the transaction inputs (coins to be spent in the transaction) and outputs (destination of the coins), which can vary in number and size. By combining multiple individual transactions into one large batch transaction, all outputs can share the same fixed data and input coins, thereby amortizing their costs.


## Upgrading Our Batching System<a id="upgrading-our-batching-system"></a>

Strike has been batching on-chain payments on behalf of our users for quite a while, and it has allowed us the ability to offer on-chain sends at very competitive prices (including a free tier!). However, recently we made a huge improvement to our batching system, which we think will reinforce our position as a leader in Bitcoin. In sharing our newest batching strategy with you, we’d like to set the expectations of what you can expect when you use Strike to make an on-chain payment as well as help other builders by sharing some lessons we’ve learned while iterating on our on-chain payment service.


### Append Outputs to Unconfirmed Transactions<a id="append-outputs-to-unconfirmed-transactions"></a>

The most recent upgrade to our batching system provides the ability to append more outputs (receivers / destinations) to existing unconfirmed batch transactions when feasible. This is done by leveraging a Bitcoin-native feature called Replace-By-Fee (RBF). RBF allows us to “replace” unconfirmed transactions by raising the fee they pay. Importantly, the outputs don’t have to be the same as the original transaction, enabling us to add more outputs to existing, unconfirmed transactions when needed.

Here are some links for those interested in learning more about RBF:

- [RBF Wiki](https://en.bitcoin.it/wiki/Replace_by_fee) (General info and history)

- [Opt-In Full RBF FaQ](https://bitcoincore.org/en/faq/optin_rbf/)

- [BIP 125: Opt-in Full Replace-by-Fee Signaling](https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki)

This upgrade allows us to handle a surge in "Priority send" requests (our next block-targeting tier described above) without constantly creating new batch transactions. Instead, we add more outputs to our existing batch transactions that have been broadcast but are still unconfirmed. Here’s why this is a game-changer:

1. **Reduced On-chain Footprint:** By minimizing the number of new transactions created, we further reduce congestion on the Bitcoin network.

2. **Fee Cost Savings:** Fewer batch transactions for the same number of payments generally means even more savings on Bitcoin on-chain fees - we generally see between a 50-30% cost savings per transaction.

3. **Enhanced Quality of Service (QoS):** Existing, unconfirmed batches get fee-bumped to the current market rate as part of the RBF operation. This ensures that our users will experience better service quality as their transactions are more likely to be included in the next block, regardless of fee spikes on the network.

_Example of an onchain batch, using RBF to append additional outputs until it gets confirmed_
![](https://www.datocms-assets.com/99305/1722324278-engineering_09-batching-on-chain-sends_txn.png)



## Technical Challenges and Solutions<a id="technical-challenges-and-solutions"></a>

Implementing this sophisticated batching system required overcoming several technical hurdles:


### Prevent Double Send!<a id="prevent-double-send"></a>

Using RBF to add extra outputs requires careful handling to avoid double-sending issues and ensuring that all extra appended outputs are correctly accounted for. There are several reasons double sends could become an issue when you start adding outputs to transactions through RBF. This isn’t because of any problems in the Bitcoin protocol, but because there are some conceptual pitfalls that can arise. One of the main points is that you need to handle the case where miners confirm a non-latest version of your batch transaction. Any candidates you appended after that version need to be rolled over to a new batch. But if you make a mistake here, you might end up double sending!


### Guaranteeing Transaction Tracking<a id="guaranteeing-transaction-tracking"></a>

Ensuring we don’t double send involves meticulously keeping track of which transactions have been published and monitoring which version of a batch transaction gets confirmed. This careful tracking allows us to roll over candidates from unconfirmed versions to new batches accurately. 

But what if your wallet software crashes exactly at the time of publishing a new RBF transaction to the Bitcoin network? How will you know if the transaction was published? 

Some wallet software will give you the new _TxId_ as a response upon successful publishing of a new transaction. This approach is not good enough here, as it could result in us never learning the _TxId_ of a transaction that might have been published and confirmed on-chain. We might fail to receive the response containing the new _TxId_ because of e.g. network level errors, software crashes, etc, even though a new transaction was in fact broadcast. Since all our transaction versions contain a different set of outputs, it's crucial that we know which version gets confirmed so that we can decide if any appended outputs did NOT get confirmed and therefore need to be rolled over to a new batch.\
This general problem can be solved by a 2 step approach:

1. Build your transaction and store it in your DB

2. If step 1 succeeded, try to broadcast the transaction to the Bitcoin network

With this approach, step 2 can safely be retried if you encounter any problems. You will also have the ability to monitor the Bitcoin network for the _TxId_, to help determine if the transaction got published or not. The way Bitcoin transactions work is that building the transaction also means building the _TxId._ This is a completely offline process which can be done by your software without communication with the rest of the Bitcoin network.


### Chain Split & Reorganization<a id="chain-split--reorganization"></a>

Another case to look out for is when versions of your batch transaction are involved in [Bitcoin Chain Splits](https://developer.bitcoin.org/devguide/block_chain.html#block-height-and-forking) (temporary blockchain forks) and potentially the subsequent reorganization of the blockchain. Without going into the details, this could mean that a version of your batch transaction initially gets confirmed on-chain, but is shortly thereafter un-done and superseded by another version of your batch transaction!

Since all versions of our batch transactions contain a different set of outputs, and we make decisions on which outputs to roll over to a new batch based on which version got confirmed, this phenomenon also has the potential to make us double send. Chain Splits & Reorganizations are an important part of the blockchain's operation to ensure consensus, so our systems need to be able to handle this. A simple solution is to just do the same as one normally does for on-chain receives; wait until the transaction has _X_ (more than one!) confirmations on-chain before considering it as final. In Bitcoin, you will occasionally see chain splits with the depth of one block, but if your transaction was confirmed 6 blocks ago it's generally considered safe to count it as “final”.


### Appropriate Fee Estimations<a id="appropriate-fee-estimations"></a>

Using [mempool-based fee estimations](https://strike.me/blog/blended-bitcoin-fee-estimations/) as opposed to blockchain-based estimations is crucial for QoS and cost efficiency. This approach ensures that transactions can get into the next block without overpaying. Our system continuously monitors our mempool to choose an appropriate fee rate for each batch transaction and each RBF.


## Scaling On-chain Operations<a id="scaling-on-chain-operations"></a>

Our enhanced batching system positions us to scale our on-chain operations to a level where we can truly grow to be a global company with millions of active users. Our system now allows us to handle huge increases in volume from our users without compromising on speed, cost or quality of service.


### UTXOs: A Scarce Resource<a id="utxos-a-scarce-resource"></a>

One of the biggest challenges with scaling a custodial on-chain send service while still offering the “Priority send” option is the need to keep a stack of UTXOs which can be used as inputs in your transactions to facilitate on-chain payments. Imagine having to serve one “Priority send” request from your users every second, while there is a larger gap (e.g. 1 hour) between blocks getting mined on the Bitcoin network. If you need to instantly publish all these transactions, batching them wouldn’t be possible.

However, let's say we are clever and we add a slight delay of just 5 seconds between each of our batch transactions. This means we can batch 5 requests together every 5 seconds. So, during an hour where no block is mined we would need to publish 720 transactions to facilitate the requests of our users in this example. Since none of these transactions would get confirmed during that hour, the change outputs from these transactions would not be available for safe reuse, necessitating a stockpile of 720 UTXOs of appropriate sizes in our hot wallet. Without this, our service would simply halt until a new block is mined. This situation becomes even trickier during fee spikes, which might cause transactions to remain unconfirmed for an even longer period.

Moreover, maintaining UTXOs of an “appropriate size” adds another layer of complexity. For instance, if all send requests are for 1 BTC each - we would need to maintain 720 BTC in our hot wallet, broken down into UTXOs of 1 BTC each. This not only becomes complex to manage but also operationally inefficient and hard to scale. It’s of course impossible to 100% accurately predict what your users will do, so your stockpile of UTXOs needs to be even bigger than this to be ready for unforeseen spikes in demand. The foundational issue here is that we end up with many unconfirmed transactions in the mempool simultaneously, locking up numerous of our UTXOs.


### Running the System on a Single UTXO?<a id="running-the-system-on-a-single-utxo"></a>

Instead of publishing new batch transactions every 5 seconds as in the previous example, our new approach appends more outputs to our existing, unconfirmed transaction - if there are any. This provides an incredibly efficient solution to the problem mentioned above. Appending more outputs reuses the existing input UTXO of the unconfirmed transaction, provided the UTXO is large enough. This means that, in theory, our entire batching system could run on a single UTXO.

Each time one of our batch transactions gets confirmed on-chain, we receive the change output back as a new UTXO, which can then be used to fund the next batch. This approach essentially scales infinitely (or at least until the Bitcoin block size limit!), allowing us to handle a growing volume of on-chain send requests without being constrained by the number of UTXOs in our hot wallet. It also mitigates the risk associated with fee spikes, ensuring continuous operation even during network congestion.

Through this system we achieve an unprecedented level of scalability and reliability in our on-chain operations. This positions Strike to grow and serve a global user base with millions of active users, offering them the best possible service in terms of speed, cost, and reliability.


## Superior QoS<a id="superior-qos"></a>

Our commitment to providing our users with the highest quality service in the industry is evident in our approach to on-chain payment batching. Users can trust that their payments will be handled with the utmost care, efficiency, and security, whether they opt for a Flexible, Standard, or Priority send.

Fee spikes on the Bitcoin network are a common problem that plague the quality of other providers. It’s common to publish transactions with a high enough fee to target a confirmation in the next block only to then see the general fee market spike significantly. In these cases, published transactions will likely not get confirmed for several hours and could potentially end up stuck much longer or pruned. The Bitcoin protocol has solutions to let you “fee bump” your transaction to solve for this, but it's not ubiquitous to all apps and wallets, and not common for wallets to automatically fee bump your transaction in such cases without charging you more for it! Strike simplifies all of this for you, and provides flexibility for users with varying time preferences.


## Conclusion<a id="conclusion"></a>

At Strike, we continually strive to innovate and improve our services. Our advanced batching system for on-chain sends is a testament to our dedication to efficiency and high-quality service. We aim to be the best at Bitcoin and that means providing our users with the best possible experience that Bitcoin payments can offer. We truly believe that our on-chain send experience is now well on its way to how on-chain payments will, and should work in the future. We will, however, always continue to iterate on our solutions to further enhance them and to show the world how much Bitcoin has to offer.

Feel free to reach out if you have any questions or need further details about our on-chain batching system and its benefits. We're always here to help and provide the best possible service to our users.


Quality of Service (QoS), Efficiency, and Security

Batching On-chain Sends

I am pleased to share our latest open source contribution, the [BOLT 12 Playground](https://github.com/LN-Zap/bolt12-playground). This project provides a simple to use, hands-on testing environment for those working on or interested in exploring and practically testing BOLT 12, a new payments protocol for the [Lightning Network](https://strike.me/learn/what-is-the-lightning-network/).

Check it out: [https://github.com/LN-Zap/bolt12-playground](https://github.com/LN-Zap/bolt12-playground).

![](https://www.datocms-assets.com/99305/1718994172-bolt12-hero.png)


## What is BOLT 12?

BOLT 12 is a protocol that extends the capabilities of the Lightning Network, a second-layer solution for Bitcoin that enables fast, low-cost transactions. BOLT 12 introduces a new type of [Lightning Invoice](https://strike.me/learn/what-is-a-lightning-invoice/) called "Offers," which are reusable, can be used for recurring payments, include advanced security features, and can contain additional information such as refund addresses and payer notes.

See [https://bolt12.org/](https://bolt12.org/) for more information.

## What is BOLT 12 Playground?

The BOLT 12 Playground is a [Docker](https://www.docker.com/) stack that includes support for the most popular Lightning Network implementations and related components, including [Lightning Network Daemon (LND)](https://github.com/lightningnetwork/lnd), [LNDK](https://github.com/lndk-org/lndk), [Core Lightning (CLN)](https://github.com/ElementsProject/lightning), [Eclair](https://github.com/ACINQ/eclair) and [LDK Node](https://github.com/lightningdevkit/ldk-node). It connects everything together, initializes wallets, and creates channels between the nodes. Every node in the stack supports BOLT 12, enabling easy experimentation with invoice creation, payments, and other features of BOLT 12.

[![](https://www.datocms-assets.com/99305/1718949890-bolt12-playground-stack.png)](https://github.com/LN-Zap/bolt12-playground)

## Why use BOLT 12 Playground?

The BOLT 12 Playground provides an opportunity for Bitcoin professionals and hobbyists to get hands-on experience with the BOLT 12 protocol. It's a sandbox where you can experiment, learn, and gain insights into how BOLT 12 works in practice. Whether you're a developer looking to implement BOLT 12 in your own projects, a researcher studying the Lightning Network, or a Bitcoin enthusiast curious about the latest developments, we think the BOLT 12 Playground may be a useful resource for you.

![](https://www.datocms-assets.com/99305/1718949886-bolt12-playground-tests.png)

The BOLT 12 Playground goes beyond a simple sandbox environment. It's also a powerful tool for developers and testers to ensure interoperability between different Lightning Network node implementations, complete with automated tests to prove things out.

### **The BOLT 12 Playground includes:**

#### **Cross-Implementation Testing**
The Playground facilitates testing BOLT 12 payments across various node implementations, which can help identify and address potential compatibility issues before real-world deployment.

#### **Channel Topology Testing**  
It allows testing across different channel topologies, including direct channels, multi-hop payments, and even multi-hop payments that traverse nodes from different implementations. This helps ensure BOLT 12 functions seamlessly regardless of the network structure.

#### **Automated Testing**
The project incorporates an automated integration test suite. Currently, the suite supports simulated payments with LND (via lndk), Eclair, CLN and LDK Node. This automation streamlines testing and facilitates continuous integration practices.


## Community Contributions

The BOLT 12 Playground is an open-source project, and we encourage contributions from the community. If you're working on a node implementation with BOLT 12 support, we welcome you to test it with and integrate into the BOLT 12 Playground!

## Getting Started

To get started using the BOLT 12 playground visit the project's GitHub  repository [https://github.com/LN-Zap/bolt12-playground](https://github.com/LN-Zap/bolt12-playground).

A Sandbox for Hands-On BOLT 12 Testing

The BOLT 12 Playground

The [Lightning Network](https://strike.me/learn/what-is-the-lightning-network/) is bitcoin payments network that’s instant, private, and low-to-no cost. Running a Lightning node can provide significant benefits, including financial self-sovereignty, enhancement of privacy, earning of routing fees, and/or participation in a new global financial network. However, maintaining a Lightning node requires some work, including the occasional need to migrate your operation to a new node for security, privacy, or maintenance reasons. The process of migrating to a new node, is sometimes referred to as “rotating your node’s seed”.

![](https://www.datocms-assets.com/99305/1712088217-blog-migrating-a-ln-node-01.png)

Your Lightning node's channels, through which bitcoin is sent and received, are linked directly to the node’s unique seed. This means you can't simply "copy & paste" your node’s channels to a new seed. Migrating your node for security or other reasons requires a strategic migration process.

In this post, we'll break down the steps to smoothly migrate your node's liquidity from one node to another, whilst minimizing downtime and making the transition seamless for your users and the network.

__💡NOTE: Moving your node to new hardware without changing its seed? In this scenario, you should use a simpler "lift & lay" approach: backup, transfer, & restore. This avoids complexities of seed rotation.__

Assuming that you _do_ need to migrate to a new node with a new seed, and you have the luxury of time on your side, the following sections will walk through a step-by-step approach to migrating your node's liquidity and routing activity to a new seed with minimal disruption to service.


## Preparing to migrate your Lightning node

Before beginning, it’s important to remember that if your node operates as a routing node, you’ll be restarting its reputation from zero, which can be an important consideration for channel connectivity and liquidity. Let's begin by laying the essential groundwork, setting up your new node and preparing it to take over seamlessly in the future.

![](https://www.datocms-assets.com/99305/1712088227-blog-migrating-a-ln-node-02.png)

### Step 1: Provision a new node

To begin, you’ll need to securely set up your new node with a unique, strong seed. Remember, proper seed and key management are paramount. Your new node comes with a new unique identity and pubkey.

![](https://www.datocms-assets.com/99305/1712088235-blog-migrating-a-ln-node-03.png)

### Step 2: Create a bridge

You’ll then need to establish a large channel between the old and new nodes. Remember to initiate the channel opening from the old node so that it has the capability to route payments through to the new one. This channel will act as a bridge for efficient funds transfer. On the old node, set the channel policy with a low fee (e.g. zero) and a low time lock delta (e.g. 18). Given you control both nodes, you control the routing policies at either ends of the channel. On the new node, set the routing fees for this channel higher to discourage flow in the other direction. The low fee for routing towards the new node will encourage liquidity to flow in that direction.


## Step-by-step migration

While migrating liquidity to your new node, the key is to maintain a smooth transition for your users and the network. You want your existing node to remain active and available, routing with its current liquidity, while simultaneously building up the new node to seamlessly take over.

![](https://www.datocms-assets.com/99305/1712088241-blog-migrating-a-ln-node-04.png)

### Step 3: Strategic channel closures

First, prioritize closing channels where most of the liquidity resides on your side of the channel, also known as channels with outbound liquidity. This will provide you with capital that you can use to open new channels on the new node, and the liquidity profile of those new channels will be similar to the old ones (most liquidity on your side). Channels will need to be closed individually as batching isn’t yet supported by most node implementations, so use strategic timing and appropriately low fees to keep the channel closing costs down.

![](https://www.datocms-assets.com/99305/1712088247-blog-migrating-a-ln-node-05.png)

### Step 4: Batch channel openings

As you close channels on the old node, simultaneously open new ones on the new node to the same set of peers, using batch channel opening to save fees. It’s best to open channels of a similar capacity to enable continuity of service towards those peers. Alternatively, this can be a good opportunity to rethink and reconsider your channel topology.

![](https://www.datocms-assets.com/99305/1712088252-blog-migrating-a-ln-node-06.png)

### Step 5: Controlling the flow

You’ll then need to monitor channel balances for the new node closely and use the routing fees as a lever to influence the flow of liquidity.
    
It’s a good idea to open the new channels with competitive fee rates to promote outbound flow, and gradually raise them as liquidity starts flowing through the new channels and reaches a balanced state. Consider using a tool like [charge-lnd](https://github.com/accumulator/charge-lnd) to automate fee adjustments as the liquidity profile changes over time.
    
If you originate payments form your nodes, consider that if the outbound channels on the new node have non-zero routing fees, then any outbound payments originating from your original node that pass through the bridge channel will incur those routing fees. This may or may not be desirable, depending on your use case. To avoid these extra fees, you can be selective about the first-hop channel used for payments and exclude the bridge channel if desired. Alternatively, you can set externally facing outbound routing fees to zero on the new node, or be strategic about which node you choose to originate payments from.

![](https://www.datocms-assets.com/99305/1712088259-blog-migrating-a-ln-node-07.png)

### Step 6: Rinse and repeat

Continue iterating between steps 3-5, gradually migrating batches of channels until complete.


## Additional Tips

Migrating your Lightning node's seed can sound complex, but with the right approach, it can be a manageable step towards enhanced security or an improved topology. Here are some other things to consider to further streamline the process:

- Consider using swaps such as [peerswaps](https://strike.me/blog/peerswaps/) or [loops](https://lightning.engineering/loop/) to expedite rebalancing.

- Update node policies to prevent new channels being opened towards the old node.

- Use a [blended fee estimator](https://strike.me/blog/blended-bitcoin-fee-estimations/) for good fee estimates.

- Update node aliases to indicate a migration is in progress.

- Inform node operators about the transition through online communities.

- Work with channel partners to update channel acceptor policies with your new pubkey.

- Create new on-chain addresses from the new node and update references as needed.

- Monitor on-chain addresses associated with the old node and transfer received funds.

- Adapt the process to your specific node setup and preferences.


Moving liquidity to a new Lightning node

Migrating a Lightning node

In Bitcoin, transaction fees play an important role in ensuring timely and reliable transaction confirmation. However, accurately estimating these fees can be a challenging task, given the ever-shifting market dynamics and competing transaction demands. This challenge is further compounded by the scarcity of blockspace, a finite resource that every transaction competes for.

With new blocks being mined approximately every 10 minutes, it's up to you, the transaction sender, to determine the fee you're willing to pay to secure your transaction's inclusion in the blockchain. A higher fee generally translates into a higher probability of a fast confirmation, while a lower fee may lead to delayed confirmation. But how can you accurately estimate the fee required based on your time preference?

**In this post, we'll look at some of the different ways of estimating bitcoin transaction fees, and how you can combine these into an effective fee estimation strategy.**


## Bitcoin fee estimation types

Accurately predicting future fee trends remains a challenge. While wallets and nodes employ various fee estimation methods, each approach has its strengths and limitations. 

**There are two primary fee estimation methods that we’ll look at: mempool-based and history-based.**


### Mempool-based fee estimation

Mempool-based fee estimation focuses on analyzing the current state of the mempool - the collection of unconfirmed transactions vying for block space. By examining the fee rates of transactions recently added to the mempool, this method provides real-time insights into the current fee landscape. This approach is particularly useful for situations where rapid confirmation is desired, as it can provide up-to-date estimates based on the immediate fee dynamics of the actual content of the mempool.

A good example of mempool-based fee estimation is the the [Mempool](https://mempool.space/) open source project. The team at [Muun](https://muun.com/) also use their own custom mempool-based fee estimator, which you can read more about [here](https://blog.muun.com/why-is-muuns-fee-estimator-more-efficient/). They produce this chart on their website that shows how much of a difference a mempool-based approach can make:

![](https://www.datocms-assets.com/99305/1705601134-munn-fee-chart.png)

As you can see, when it comes to accurately estimating the fee to get a transaction confirmed in the _next_ block, mempool-based estimators like this do a good job; They produce estimates that are more optimal as they are more reactive to short term changes.


### History-based fee estimation

In contrast to mempool-based estimation, history-based fee estimation uses historical data to predict future fee trends, analyzing past transaction data to identify patterns and trends in fee fluctuations. By understanding historical fee movements, history-based estimation can provide more stable and predictable fee estimates for transactions with more flexible confirmation targets.

[Bitcoin Core](https://github.com/bitcoin/bitcoin) - the most widely used Bitcoin node implementation, and the one we use at Strike - uses this history based approach. If you want to see exactly how it generates its fee estimates, you can read the [Bitcoin Core fee estimation source code](https://github.com/bitcoin/bitcoin/blob/master/src/policy/fees.h). But to break it down in simple terms, the estimation process involves:

- Grouping transactions into buckets based on similar fee rates
- Tracking how long it takes for transactions in these buckets to be mined
- Using different data sets to track this information over various time horizons (short, medium, and long)
- Applying a decay factor for each dataset to give more weight to recent transactions
- Using success thresholds for different time horizons
- Calculating estimates based on the number of transactions confirmed within the target number of blocks or less

Bitcoin Core's fee estimation uses a moving average and various parameters to provide fee rate estimates under different conditions. Within this, there are two estimation modes that you can select from: economical and conservative.

**Economical Mode:** This mode estimates fees based on recent blocks, aiming to optimize for lower fees. It is more responsive to the latest changes in the fee market, making it suitable for situations where you are willing to risk longer confirmation times for potentially lower fees.

**Conservative Mode:** This mode provides estimates that are more likely to ensure faster confirmation, as it considers a longer transaction history. However, it is less responsive to short-term drops in fee rates, often resulting in higher fee recommendations. This mode is better if you want to prioritize transaction confirmation time over fee cost.

Both modes aim to balance cost and confirmation time based on different user preferences and market conditions.


## Striking the right balance
At Strike, we make a lot of Bitcoin transactions on behalf of our users. Depending on the scenario, we have differing requirements for our confirmation times. To look at a couple of brief examples:

**Transaction batching:** When we broadcast on-chain transactions on behalf of our users, we use transaction batching in order to optimize our block space usage. Generally speaking our batching algorithm aims to broadcast a batch of transactions every block. For this to be effective, we need strong guarantees that our transaction will actually make it into the next block, so using a mempool-based fee estimator works best for this use case.

**Lightning channel opening/closing:** Conversely, when we are opening and closing lightning channels, we may be able to wait longer, and so a history based estimate, like those from Bitcoin Core, can be more appropriate as it enables us to more effectively target blocks further into the future.


## Blended fee estimation

Given the benefits and limitations of each individual approach, we use a blended fee estimation method that leverages the advantages of both mempool-based and history-based estimations.

For immediate transactions demanding prompt confirmation within the next few blocks, we prioritize mempool-based estimates for their real-time accuracy.

For transactions with more flexible confirmation targets stretching into the future, we rely on history-based estimates to provide a more stable and predictable fee range.

This blended approach strikes a balance between real-time precision and long-term predictability, enabling us to optimize transaction fees effectively across a wide spectrum of scenarios.


## Improving LND's fee estimates

**In the rest of this post, we’ll look at how we combined the two techniques - mempool-based and history-based fee estimation.**

Given we primarily use the [Lightning Network Daemon (LND)](https://github.com/lightningnetwork/lnd) for our Lightning node needs, we’ll focus on that; however, a similar approach could be taken for other node implementations.


### Custom fee estimates with LND

By default, an LND node that is connected to a Bitcoin Core instance will use the [`estimatesmartfee` RPC](https://developer.bitcoin.org/reference/rpc/estimatesmartfee.html) from Bitcoin Core to provide its fee estimates. As we saw above, this is far less than ideal in some situations as its estimates are only based on historical data.

Wouldn’t it be better if we could plug a different fee estimator into LND? Well, we’re in luck because the engineers that work on LND thought of that and, of course, already made the fee service configurable.

It might not be immediately apparent, however if you look at the [sample config file](https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf) provided in the LND source code, you’ll find this code block:

```
; Optional URL for external fee estimation. If no URL is specified, the method
; for fee estimation will depend on the chosen backend and network. Must be set
; for neutrino on mainnet.
; Default:
;   feeurl=
; Example:
;   feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
```

As you can see, there is a `feeurl` config option, which can be set to a URL that provides fee estimates. And if we visit the [example url](https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json) from that same snippet, you’ll land on a page that serves some json that looks like this:

```
{
  "current_block_hash": "0000000000000000000075b86...6303e",
  "fee_by_block_target": {
    "2": 141428,
    "4": 96148,
    "85": 82688,
    "121": 79068
    "24": 171819,
    "25": 86680,
    "144": 58520,
    "504": 56192,
    "1008": 37896
  }
}

```

Examining this a little, what we notice is that it is providing a series of confirmation target estimates. From the example above, the estimated fee to have a transaction mined within the next 4 blocks is 96,148 (that is fee per kb - so that translates to a fee rate of ~96 sats/vbyte).

This is pretty nice. It means that we can point the `feeurl` setting to any url that returns json following this format, so in theory we could plug any fee estimation system into that, as long as it can return fee estimates in the expected format.


### Using selective mempool-based and historical-based estimates

Our goal was to use mempool-based fee estimates for transactions that should be confirmed within the next few blocks, but continue to use history-based estimates for transactions that should be confirmed further into the future.

When it comes to mempool-based fee estimators, we think the Mempool open source project is one of the better tools out there, so we wanted to use that for our short term fee estimates. And for the longer term estimates we think Bitcoin Core does a pretty good job so we wanted to continue to use that.

To achieve this, we created a [Bitcoin Blended Fee Estimator](https://github.com/LN-Zap/bitcoin-blended-fee-estimator). This is a basic service that provides a single endpoint that serves json with fee estimates in the expected format for LND.

Estimates for a confirmation target of 1 through 6 are provided by the [Mempool API](https://mempool.space/docs/api/rest), whilst estimates for confirmation targets further out into the future are provided by Bitcoin Core via the [Esplora API](https://github.com/Blockstream/esplora/blob/master/API.md).

By default it connects to the [mempool.space](https://mempool.space/) and [blockstream.info](https://github.com/Blockstream/esplora/blob/master/API.md) public APIs, however, it can be configured to connect directly to your own Mempool and Esplora instances to reduce the reliance on these hosted third party APIs.

### Running the blended fee estimation service

You can run this service in your own infrastructure alongside your LND node. Or, you can use our hosted version to get up and running quickly (read on for more details).

If you have Docker setup on your machine, you can try it out by running the [Docker image](https://hub.docker.com/repository/docker/lnzap/lnd-mempoolspace) which we provide for convenience.

```
docker run -p 3000:3000 lnzap/bitcoin-blended-fee-estimator:latest
```

After the docker image has downloaded, you should see the following output indicating that the service is up and running.

```
---
Using port: 3000
Using base URL: http://localhost:3000
Using Esplora base URL: https://blockstream.info
Using Mempool base URL: https://mempool.space
Using Mempool estimation depth: 6
Using fee multiplier: 1
Using cache stdTTL: 15
Using cache checkperiod: 20
---
Fee Estimates available at http://localhost:3000/v1/fee-estimates
```

Then, simply navigate to <http://localhost:3000/v1/fee-estimates> where you should see the the current fee estimates, nicely formatted for LND.

You can set this URL in your LND config file and restart your LND node:

```
; URL for external fee estimation.
feeurl=http://localhost:3000/v1/fee-estimates
```

With this in place, LND will now use fee estimates from Mempool for next block fee estimates, and estimates from Esplora for estimates further into the future.

### Leveraging the blended fee estimation service

Because we have plugged directly into LND, it will use this for all of its internal fee estimations that target a specific number of blocks into the future such as making on-chain transactions, opening channels, sweeps, etc. Additionally, anything that connects to or builds on LND will also benefit from the new fee estimation sources. So you’ll have a consistent approach to generating fee estimates throughout your stack.

For example, if you are using [Lightning Loop](https://lightning.engineering/loop/) to rebalance channels, the fee estimates provided by the Loop service will also be using our custom fee sources since it calls through to LND to get those estimates (we found this to drastically reduce our rebalancing costs by preventing Loop from overpaying onchain fees).

Or if you are building a wallet or other service on top of LND, that too will use the custom fee estimation sources.

Essentially, anything that calls LND’s [EstimateFee RPC](https://lightning.engineering/api-docs/api/lnd/wallet-kit/estimate-fee) - either directly or indirectly - will use the new fee estimation source.


## A Strike hosted fee estimation service for LND

Using a mix of mempool-based and history-based fee estimates in our tooling has provided us with better estimates for getting transactions mined. This helps keep costs down for our users as well as relieving fee pressure from the Bitcoin blockchain.

We figured it could be useful for other node operators, wallet service providers, or builders - so we have open sourced the code:

https://github.com/LN-Zap/bitcoin-blended-fee-estimator

Additionally, we wanted to make it super simple for you to try this out without needing to deploy an instance of the service to your own infrastructure, so we’ve setup a hosated version of the service for anyone to use. You can access it at the following URL:

https://bitcoinchainfees.strike.me

To use, simply add/update the `feeurl` setting in your lnd.conf file to point at the endpoint provided by the service:

```
feeurl=https://bitcoinchainfees.strike.me/v1/fee-estimates
```

We hope you find the blended fee estimation tool useful! Let us know if it works for you or if you have any questions or suggestions for improvements.

## Future improvements

Issues with Bitcoin Core's current history-based fee estimations are fairly well known and understood, and there are multiple efforts and proposals to improve this.

One recent proposal is the idea of Cluster Fee Estimation, emerging from discussions in the broader Bitcoin community. This approach aims to address some of the complexities of the Child Pays For Parent (CPFP) mechanism by clustering linked transactions and evaluating their collective fee rates. To understand the CPFP mechanism's impact on fee estimation and the Cluster Fee Estimation proposal in more detail, this [article from Bitcoin Optech](https://bitcoinops.org/en/topics/cluster-mempool/) is worth a read, or check out this more detailed [summary of the proposal](https://delvingbitcoin.org/t/an-overview-of-the-cluster-mempool-proposal/393) from Suhas Daftuar.

Though no fee estimation technique will ever be perfect given the impossible task of predicting the future, we can continue to implement more advanced, robust, and adaptive solutions that deliver overall improvements to the fee estimation problem.

**The more we collectively optimize our on-chain transaction fees, the better for everyone**; by reducing fee overpayment, we can help avoid the self-perpetuating cycle in which people paying unnecessarily high fees, can drive fee estimates further higher.

Combining mempool-based and history-based fee estimators

Blended Bitcoin Fee Estimations

[Peerswaps](https://www.peerswap.dev/) enable atomic swaps between Lightning Network and Bitcoin (BTC) or Liquid Bitcoin (L-BTC). This can enable a cost effective and capital efficient way to maintain well balanced Lightning channels.

We’ll take a practical look at how to go about performing a peerswap, and how you could add peerswaps to your channel rebalancing strategy.

## Run the Daemons
Alongside your Lightning node (peerswap currently supports [LND](https://github.com/lightningnetwork/lnd) or [CLN](https://github.com/ElementsProject/lightning)), run the [Peerswap daemon](https://github.com/ElementsProject/peerswap), and optionally the [Elements daemon](https://github.com/ElementsProject/elements) if you want to use L-BTC.

The Peerswap node will act as the swap coordinator.

The Elements node will act as a Liquid Bitcoin wallet which you can use to swap funds into and out of your Lighting channels. If you want to use regular BTC instead of L-BTC, you can use the on-chain bitcoin wallet that’s integrated with your Lightning node instead.

When you want to rebalance the channel, use the Peerswap daemon to initiate a peerswap. The peerswap daemon will coordinate the transactions with your channel peer. After initiating the swap, you just need to wait for 2 confirmations on the Liquid network for everything to complete. The whole process takes about 2 minutes (the time it takes for 2 blocks to confirm on the Liquid blockchain).

## Whitelist Peers
Peerswaps are direct swaps with direct channel partners. To use Peerswap your channel partner must also be running Peerswaps and must have whitelisted you in their peerswap config file (or set the `accept_all_peers` option). You must also whitelist them in yours. You can run `pcli listpeers` to check which of your connected channel peers support peerswaps and which chains they support (BTC and/or L-BTC).

Why the whitelist? Consider that a peerswap is an operation that has a cost (on-chain fees), a time opportunity cost (funds locked during the swap operation), and an effect on your liquidity profile (swapping capital between Lightning and BTC or L-BTC). It’s probably not something that you want to blindly allow anybody to do. However, it is something that you could reasonably enable between proven node operators within your own network of channel peers, or even your own nodes if you run multiple.

## Rebalancing Use Bitcoin (BTC) or Liquid Bitcoin (L-BTC)
Peerswaps supports swapping using both the Bitcoin base chain, and the [Liquid](https://liquid.net/) Bitcoin federated sidechain. Each has their pros and cons, but for the purposes of rebalancing channels, the Liquid Network has a distinct advantage in two important areas - speed, and cost.

### Speed
Blocks on the Liquid network are produced every minute and only 2 confirmations are required to complete a peerswap. So it takes ~2+ minutes to finalize a peerswap.

On the Bitcoin network blocks are produced on average every 10 minutes and it will take 3 confirmations to complete a peerswap. So it takes ~30+ minutes to finalize a peerswap.

### Cost
The average transaction fee on the Liquid network is currently 0.1 sat/vbyte to get into the next block (although this may change over time). Given an average transaction size of ~2000 vbytes it would cost you about 200 sats to perform a swap. That is about $0.025 by today's exchange rates.

On the Bitcoin base chain, fees are variable but generally much higher. At the time of writing, it will cost about 50 sat/vbyte to get into the next block. Given an average transaction size of ~300 vbytes it would cost you about 12,000 sats to perform a swap. That is about $5.62 by today's exchange rates. In other words, about 225 times more expensive than L-BTC, and a material consideration if you are a Lightning routing node operator or are running a business in which channels need to be regularly rebalanced.

### Other Considerations
Of course, cost and speed aren’t the only considerations. To use Peerswaps you will also have some additional overhead.

Running peerswaps itself is pretty straightforward. It’s only acting as a coordinator so it doesn’t directly hold funds, although it does need access to your nodes, and it does need to maintain state so you will need to ensure you have robust secrets management and backup solutions in place.

If you want to take advantage of Liquid you also need to run the Elements daemon where there is more to consider, as the Elements wallet will be holding an L-BTC balance. And there is also the different [trust model](https://blog.liquid.net/the-truth-about-liquid/) of the Liquid federation itself to consider.

### BTC vs L-BTC
All in all, if you're looking for a fast, very cost effective way to maintain balanced channels between semi-trusted direct channel peers, L-BTC is a good option. Although using BTC for peerswaps may also be useful and preferable in certain situations. This comparison from the Peerswaps team shows some of those considerations:

![](https://www.datocms-assets.com/99305/1702226228-peerswaps-btc-lbtc.png)

## Performing Swaps
Depending on the state of your channel, you’ll perform a swap-in or a swap-out to rebalance it:

### The Swap-Out
When most of the liquidity is at your end of the channel (you are short of inbound liquidity) you swap some of your Lightning Bitcoin with your peer’s L-BTC (or BTC); you perform a swap-out.

![](https://www.datocms-assets.com/99305/1702226245-peerswaps-swap-out.png)

In the swap-out, you will generate an L-BTC (or BTC) on-chain address, your peer will generate a Lightning invoice for the same amount, and you will then pay this invoice using the  unbalanced outbound heavy channel. This pushes Lighting Bitcoin along the channel, to your peer, rebalancing the channel. As part of the same process your peer will send the required BTC amount to your on-chain address.

### The Swap-In
Conversely, when most of the liquidity is at your peers end of the channel (you are short of outbound liquidity) you swap your L-BTC (or BTC) with your peers Lightning Bitcoin; you perform a swap-in.

![](https://www.datocms-assets.com/99305/1702226238-peerswaps-swap-in.png)

In the swap-in, you will generate a Lightning invoice, your peer will generate an L-BTC (or BTC) on-chain address, and they will then pay your invoice using the unbalanced inbound heavy channel, pushing their Lighting Bitcoin along the channel to your side of the channel making it yours, and in the process rebalancing the channel. As part of the same process you will pay the required amount of BTC to your peer’s on-chain address.

The end result - ~2 minutes later your channel will be back at your preferred liquidity profile for a cost of less than $0.03, if you used liquid. You could do this dozens of times in a single day and only pay $1 total at today’s rates.

## Automation to keep the channel balanced
With both yourself and your peer running peerswaps and elements, you now have the ability to keep channels between each other balanced for a very low cost.

One way to do this would be to maintain a pool of working capital in the form of L-BTC, which you peg into the Liquid sidechain from the Bitcoin chain when on-chain fee rates are relatively low. You could then automate things such that if all the liquidity in the channel moves towards 100% in either direction you can use peerswap to bring it back towards 50% by swapping into or out from the channel balance to and from your L-BTC working capital pool.

This can enable you to maintain fewer, smaller, well balanced channels with a very small on-chain footprint.

## Testing with Peerswap Playground
We put together this simple [PeerSwap Playground](https://github.com/LN-Zap/peerswap-playground) which you can use to try it out. It provides a Docker stack that comprises bitcoind (running on regtest), elementsd, 2x lnd nodes, 2x peerswap clients, and 2x L-BTC wallets. It connects everything together, initializes the wallets, and creates a channel between the two nodes.

You can use this to perform test swaps or just practice your skills with lnd, elementsd, and peerswapd! There are some simple instructions in the project’s readme which will walk you through the setup and the process of performing a swap.

## Rebalancing channels with Strike using Peerswaps
If you support Peerswaps and are one of our existing channel partners or run a reliable routing node and would like to maintain a balanced channel with the [Strike routing node](https://1ml.com/node/034d7f4bbbd6c1c1d8fbe0a42dd1f59e10b66540c6872dfcaa095d8d5cffebcf46), reach to our liquidity team at [liquidity@strike.me](mailto:liquidity@strike.me).

### Other Rebalancing Tools and Techniques
Peerswaps is a relatively new rebalancing technique. This comparison from the Peerswaps team conveys some of the key properties and tradeoffs of peerswaps as compared to other approaches to rebalancing channels.

![](https://www.datocms-assets.com/99305/1702226252-channel-balancing-options.png)

All in all, Peerswaps between Lightning and L-BTC can be a reliable, cost effective, and capital efficient way to keep channels between semi-trusted peers well balanced.

## More About Peerswaps
Peerswaps was created by the team at [Blockstream](https://blockstream.com/). It's in its early stages and under active development. Peerswaps currently supports LND and CLN. There is only a command line interface at the moment, although a GUI integration with [Ride the Lightning](https://www.ridethelightning.info/) is in the works. The Peerswaps team has an active [Discord](http://discord.gg/MSNt8eyZrT) where they engage with the community so if you need help or would like to help with the project you can head over to there.