Skip to content

Revise Usecases.md for clarity and additional details #913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Luisfc68 merged 2 commits into from
Feb 25, 2026
Merged

Revise Usecases.md for clarity and additional details #913

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ab2c5e
Revise Usecases.md for clarity and additional details
owans Feb 6, 2026
3f1f4be
Merge branch 'master' into 6-update-flyover-index-doc
Luisfc68 Feb 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions docs/Usecases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,13 @@
The [RBTC Flyover](https://github.com/rsksmart/flyover-sdk) enables fast, trust-minimized onboarding of users into the Rootstock ecosystem from Bitcoin with less friction. It improves the usability for bitcoiners and integrators to interact with the Rootstock ecosystem via the Powpeg and Flyover SDK. See the [Comparison between the PowPeg and RBTC Flyover](/developers/integrate/flyover/powpeg-vs-flyover/)

Its main goal is to accelerate getting into Rootstock from Bitcoin by significantly reducing the wait times associated with the current PowPeg time. Developers, integrators or Liquidity Providers (LP) looking to provide RBTC access, Cross-chain swaps, and access to liquidity pools can integrate the Flyover SDK. Visit the [ LP integration section](/developers/integrate/flyover/LP/) to get started.
Its main goal is to accelerate getting into Rootstock from Bitcoin by significantly reducing the wait times associated with the current PowPeg. Developers, integrators, and Liquidity Providers (LPs) who want to offer rBTC access, cross-chain swaps, or liquidity can integrate the Flyover SDK. Visit the [LP integration section](/developers/integrate/flyover/LP/) to get started.

## Security and trust-minimization
Flyover preserves the PowPeg's trust-minimization model. User funds are never sent to the Liquidity Provider. On peg-in, the user's BTC goes to the PowPeg federation (a decentralized multi-signature entity). On peg-out, the user's rBTC is locked in the Liquidity Bridge Contract (smart contract), which releases BTC on Bitcoin. This design is important for institutional users who require custody and security.

## Features of the Flyover
* Flyover significantly reduces the amount of time required to transfer BTC and RBTC between the Bitcoin and Rootstock networks
* Uses a trustless intermediaries, a pool of Liquidity providers
* Flyover significantly reduces the time required to transfer BTC and rBTC between the Bitcoin and Rootstock networks.
* Trustless design: a pool of Liquidity Providers supplies liquidity, but user funds go to the federation (peg-in) or the smart contract (peg-out), never to the LP.
* Provides the same security guarantees as the Powpeg
* Customizable SDK for LPs and integrators

Expand All @@ -24,22 +27,22 @@ Here are some of the use cases provided by the Flyover:
The Flyover offers a way for developers to integrate Flyover into wallets, dApps, DEXs and swaps using the Flyover SDK.

**With Flyover:**
* Wallet or exchange platforms can integrate Flyover to offer a seamless experience for depositing and withdrawing BTC and RBTC within their platform utilizing the liquidity provided by the Flyover LP network. This eliminates the long wait times associated with traditional peg-in methods, allowing users to quickly move funds between their wallets to other platforms.
* Wallet or exchange platforms can integrate Flyover to offer faster depositing and withdrawing of BTC and rBTC within their platform using the Flyover LP network. Users can move funds between wallets and platforms without the long wait times of traditional peg-in.
* DeFi and Lending Platforms can integrate Flyover to allow users to easily deposit Bitcoin as collateral for borrowing assets on Rootstock. The faster peg-in times provided by Flyover would unlock borrowing opportunities for users who hold RBTC against other rootstock on-chain assets (MOC, USDRIF and others).

**Flyover offers;**

1. Streamlined and Customizable SDK Integration: The Flyover SDK provides developers with a user-friendly toolkit for integrating the Flyover functionalities into wallets, swaps, exchanges, and dApps, reducing development time and effort. The SDK can be configured to suit the user's needs.

2. Enhanced User Experience: By integrating Flyover, developers and integrators can offer their users a seamless experience for interacting with the Rootstock ecosystem, providing frictionless Bitcoin transfer options into Rootstock within their applications.
2. Enhanced user experience: Integrators can offer faster Bitcoin–Rootstock transfers within their applications, with trust-minimization preserved (user funds go to the federation or smart contract, not to the LP).

3. Increased security: Flyover is built on top of the proven security of the PowPeg.

Want to integrate the Flyover in your Exchange, dApp, Wallet or DeFi platform? See the section on [how to Integrate Flyover SDK](/developers/integrate/flyover/sdk/).


### For Liquidity Providers (LP)
An LP provides liquidity in Rootstock (RBTC) and Bitcoin (BTC) on behalf of users in exchange for a fee (configurable) as a reward. The LP can be wallets, exchanges, aggregators or individuals and institutions. See section on [LP Management](/developers/integrate/flyover/LP/management/) for more information.
An LP supplies BTC and rBTC liquidity so Flyover can offer faster transfers. The LP does not receive or custody user funds; the federation receives peg-in BTC and the Liquidity Bridge Contract holds peg-out rBTC. LPs can be wallets, exchanges, aggregators, or institutions. See [LP Management](/developers/integrate/flyover/LP/management/) for more information.

**With Flyover, the LP can:**
* Contribute to the growth of the Rootstock Ecosystem by joining the Flyover's network of LPs to ensure there's sufficient liquidity for users to transfer Bitcoin (BTC) between the Bitcoin network and Rootstock (RBTC) for their user base while also serving as LPs providing services to other users.
Expand Down Expand Up @@ -69,4 +72,4 @@ Flyover is integrated in the [PowPeg App](http://powpeg.rootstock.io) which prov
- [Liquidity Provider Server](https://github.com/rsksmart/liquidity-provider-server?tab=readme-ov-file)
- [Liquidity Bridge Contract](https://github.com/rsksmart/liquidity-bridge-contract)
- [Flyover LBC Mainnet Contract Address](https://explorer.rootstock.io/address/0xaa9caf1e3967600578727f975f283446a3da6612)
- [Flyover LBC Testnet Contract Address](https://explorer.testnet.rootstock.io/address/0xc2a630c053d12d63d32b025082f6ba268db18300)
- [Flyover LBC Testnet Contract Address](https://explorer.testnet.rootstock.io/address/0xc2a630c053d12d63d32b025082f6ba268db18300)
Loading