Boltz Docs
Boltz API
Boltz API
  • 👋Introduction
  • 📙Libraries
  • 🤖REST API (latest)
  • 🔁Swap Types & States
  • 🙋‍♂️Claim & Refund Transactions
  • ⚠️Common Mistakes
  • 🚫Don't trust. Verify!
  • 🪄Magic Routing Hints
  • ⏩0-conf
  • 🪝Webhooks
  • ⚡BOLT12
  • 🏅Pro
  • 📜Claim covenants
  • 🤝Referral Program
  • 🚢Backend Deployment
  • 🐳Regtest Environment
  • 🤖REST API v1 (deprecated)
  • 🔙Back to Docs Home
Powered by GitBook
On this page
  • Swapping to BOLT12 invoices
  • Offers
  • BIP-353

BOLT12

Information about swaps with the new BOLT12 standard and some accompanying tips & tricks for how to handle BOLT12 offers.

PreviousWebhooksNextPro

Last updated 24 days ago

Swapping to BOLT12 invoices

We allow swaps to BOLT12 invoices in . The flow is the same as with BOLT11 invoices. BOLT12 for is currently not supported, but .

Offers

To make it as easy as possible for clients to fetch BOLT12 invoices for offers, we provide .

To verify the returned invoice belongs to the provided offer, the signing key of the invoice has to be checked. That singing key has to be either:

  • the signing key of the offer, if that is defined, or

  • the public key of the last hop of one of the message paths

Reference implementations for checking the signing key:

BIP-353

A common way to share BOLT12 offers is via . After , read the URL query parameters. BOLT12 offers are in the lno parameter, so if it's set, a swap can be created by fetching an invoice and creating a Submarine Swap with it.

⚡
will be in future
this API endpoint
Rust in boltz-client
TypeScript in boltz-web-app
BIP-353
resolving the BIP-353
Submarine Swaps
Reverse Swaps