What Is RSK (Rootstock)? The Bitcoin Sidechain Explained

RSK is a smart contract platform that runs as a sidechain to Bitcoin. A sidechain is a separate blockchain with its own blocks, validators and rules, connected to a main chain through a mechanism that moves value between the two. In RSK's case the main chain is Bitcoin, and the goal is to let people use bitcoin in programmable applications that Bitcoin's own scripting language does not support well.

The network's native coin is RBTC. It is designed to track the price of bitcoin one for one, and users receive it by sending BTC through a peg. On RSK, RBTC pays transaction fees, much as ETH does on Ethereum.

Three features define the project:

• Bitcoin-linked security. RSK is merge-mined with Bitcoin, so Bitcoin miners can secure it at the same time.
• EVM compatibility. Developers can write contracts in Solidity and use familiar Ethereum tools.
• A bitcoin-denominated economy. Fees, collateral and many applications are priced in BTC terms rather than in a separate volatile gas token.

A note on naming. The project was originally called RSK and has since been presented as Rootstock. Both names refer to the same network, and you will see both in wallets, explorers and documentation. The letters RSK are also used by unrelated companies, including an environmental and engineering consultancy, so a plain web search for the term can return results that have nothing to do with crypto.

RSK is not Bitcoin and is not a Bitcoin upgrade. It is a separate network that depends on its own peg and validator setup, which is why understanding the mechanics matters before you move funds.

RSK was conceived in the mid-2010s, when Bitcoin had no practical smart contract layer and Ethereum was gaining developers. Its whitepaper was authored by Sergio Demian Lerner, a well-known Bitcoin security researcher, and the project was led commercially by Diego Gutierrez Zaldivar. The main network launched in early 2018, and a federated peg connected it to Bitcoin from the start.

The main contributor has been the company IOV Labs, which has also used the Rootstock Labs name. Check the project's current documentation for the present organisational structure, since that kind of detail changes.

A few themes stand out in the network's history:

• Early design. RSK was built to reuse Bitcoin's proof-of-work security rather than create a new mining base.
• Peg evolution. The original peg relied on a federation of known participants. Later it moved to a design called PowPeg, which adds hardware security modules and ties peg operations more closely to Bitcoin mining.
• Ecosystem tooling. The RIF (Rootstock Infrastructure Framework) project introduced a token and infrastructure services around the chain.
• Governance experiments. Community-led structures for funding and decisions have been introduced and revised over time.

Because the roadmap, branding and governance have shifted, treat older articles with care. A guide written in 2019 may describe a federation that no longer operates in the same way. When you read about RSK, look for the date and compare the claims to the official developer documentation and to independent explorers.

RSK uses merge mining, a technique that lets Bitcoin miners secure a second chain without spending extra energy. A miner builds a Bitcoin block header that also commits to an RSK block. If the work meets RSK's difficulty target, the same proof of work counts for both chains.

In practice, miners who join the arrangement add a small piece of data to their Bitcoin block and earn RSK transaction fees on top of Bitcoin rewards. They do not need separate hardware or extra electricity.

What this gives RSK:

• Shared hash power. RSK can draw on a share of Bitcoin's mining capacity. The proportion that participates changes over time, so check a current figure on the project's own statistics or an independent tracker instead of relying on a number quoted in an article.
• Familiar consensus. Blocks are produced and ordered by proof of work, not by a small validator set that stakes tokens.
• Low added cost for miners. The incentive is extra fee revenue rather than a new block subsidy.

What it does not give you:

• Bitcoin's full security. Merge mining protects the ordering of RSK blocks. It does not make RSK's smart contracts or its peg as secure as Bitcoin itself.
• Guaranteed participation. If fewer miners merge-mine, RSK's security budget falls.

Merge mining is the main reason RSK describes itself as the most Bitcoin-aligned smart contract chain. It is a real technical link, but it covers block production only. The peg and the applications are separate trust questions.

To use RSK you need RBTC, and the way to get it is the two-way peg. The idea is simple: lock BTC on Bitcoin, receive the same amount of RBTC on RSK, and reverse the process to go back.

The peg is run by a system called PowPeg. Instead of a loose federation, it uses a set of functionaries running hardware security modules (HSMs), which are devices designed to protect signing keys and to enforce rules about what they sign. Peg-out requests are meant to be processed only after being confirmed in RSK blocks that carry Bitcoin-linked proof of work. The exact parameters, such as the number of signers and confirmation times, are set in the protocol and may change, so confirm them in the official docs.

The basic flow:

1. Send BTC to the peg address generated for your RSK address.
2. Wait for the required Bitcoin confirmations.
3. Receive RBTC on RSK.
4. To exit, send RBTC to the designated peg-out contract and wait for the payout on Bitcoin.

The native peg can take a while, so the project has also built a faster option called Flyover, where liquidity providers front the funds for a fee. Exchanges and bridges may offer other ways to get RBTC, but each adds its own trust assumptions.

The key point is that the peg is the weakest link in any sidechain. If the signers fail, collude or lose keys, the RBTC could stop being redeemable one for one. PowPeg tries to reduce that risk with hardware and process controls, but it does not remove it.

RSK runs a virtual machine compatible with the Ethereum Virtual Machine. That means most Solidity smart contracts can be deployed with little or no change, and common developer tools work with the network: Hardhat, Foundry, ethers.js, web3 libraries and wallets such as MetaMask.

What stays familiar:

• Addresses and signing. You use the same style of 0x address and the same wallet interface.
• Token standards. ERC-20 and ERC-721 style tokens work as they do elsewhere.
• Developer workflow. Compile, test and deploy in the same way as on other EVM chains.

What differs:

• Gas token. Fees are paid in RBTC, not ETH.
• Block timing. RSK produces blocks on a different schedule from Ethereum, roughly every half minute at the time of writing. Check current figures on an explorer.
• Chain details. You need the RSK network settings in your wallet. The mainnet chain ID has been 30 and the public testnet 31, but copy the settings from the official documentation to avoid fake network entries.
• Fee behaviour. Gas prices and transaction costs can be low, but they vary with demand.

Because the EVM is shared, tools that work on other EVM chains often work here, but never assume compatibility for a specific contract or token without checking. Differences in opcodes, precompiled contracts or oracle availability can matter for complex DeFi code.

Treat any wallet setup carefully. Add the network from the project's official documentation, not from a pop-up on an unfamiliar site, and send a small test transaction before moving larger amounts.

Most activity on RSK is decentralised finance with a bitcoin flavour. The core idea is to put BTC to work without leaving a bitcoin-denominated environment.

Typical categories include:

• Lending and borrowing. Users deposit RBTC or other assets as collateral and borrow against them.
• Decentralised exchanges. Swap RBTC and tokens through automated market makers or order-book style protocols.
• Bitcoin-collateralised stablecoins and leveraged products. Several RSK projects have focused on stable assets or yield products backed by RBTC.
• Payments and identity. RIF services have offered name registration and relaying tools to simplify user experience.

Examples of projects that have operated on RSK include Sovryn, Money on Chain and Tropykus. Project status, liquidity and activity change often, and some may have wound down or changed direction, so check each project's own channels and a neutral data tracker before using it.

What to compare when picking a protocol:

1. Audit history. Look for published audits and whether issues were fixed.
2. Liquidity and volume. Thin markets can mean high slippage and difficult exits.
3. Admin controls. Find out who can upgrade contracts or pause markets.
4. Oracle design. Lending protocols depend on reliable price feeds.

RSK's DeFi scene is smaller than Ethereum's, so expect fewer protocols, thinner liquidity and fewer integrations with major wallets and aggregators. That can mean higher costs when swapping or borrowing, and fewer safety nets if something breaks. Start with small positions and avoid assuming that a brand name guarantees depth.

RIF stands for Rootstock Infrastructure Framework. It began as a set of services and standards meant to make building on RSK easier, and it has a token of the same name. RIF is a separate asset from RBTC, and it is not required to pay gas.

Over time RIF-related work has covered:

• Naming. The RIF Name Service lets users register readable names that map to addresses.
• Relaying. Tools that let applications sponsor or abstract gas fees for users.
• Data and storage. Services intended to give applications decentralised alternatives to centralised back ends.
• Community funding. The Rootstock Collective introduced governance and grants in which token holders take part in directing resources.

The RIF token's role has been revised more than once, so confirm its current uses in official documentation rather than relying on older summaries. Also check the token's contract address on a trusted explorer before trading, since fake tokens with similar names exist on many chains.

If you are only interested in using RSK for BTC-based DeFi, you can ignore RIF and hold only RBTC for gas. If you are a developer, RIF tooling may save time, but evaluate each service for maintenance status and documentation quality before building on it. A framework that is no longer updated can become a liability for an application you intend to run long term.

RSK is one of several ways to use bitcoin outside the base chain. Each option makes a different trade-off between security, speed, features and trust.

Option	How it works	Main trade-off
RSK	Merge-mined EVM sidechain with a PowPeg to Bitcoin	Peg and smart contract risk; smaller ecosystem
Lightning Network	Payment channels settled on Bitcoin	Great for payments, not general smart contracts
Wrapped BTC on Ethereum	BTC represented as a token on another chain	Depends on the wrapper's custodian or protocol
Decentralised BTC bridges such as tBTC	Threshold-signer system mints a BTC-backed token on Ethereum	Different trust model; relies on the signer network
Exchange-held BTC	BTC held at a centralised venue	Custody and counterparty risk

When RSK is a reasonable fit:

• You want to keep exposure to bitcoin while using lending, swaps or stable assets.
• You prefer an EVM environment with a Bitcoin-linked mining base.
• You are building an application aimed at Bitcoin holders.

When another route may be better:

• You mainly want to pay or get paid in bitcoin, where Lightning may be simpler.
• You want deep DeFi liquidity, which is usually found on Ethereum and its larger rollups.
• You are not comfortable with a peg-based asset and prefer to hold BTC on Bitcoin.

There is no single correct answer. The honest comparison is about which trust assumptions you accept, how much liquidity you need and whether you can exit easily when conditions change.

Using RSK involves the same categories of risk as other crypto networks, plus a few specific to pegged sidechains.

Peg risk. RBTC is only worth one BTC if the peg works. A failure of signers, hardware, software or governance could break redemptions.

Smart contract risk. Bugs and exploits can drain protocols even after audits. Smaller ecosystems may have fewer reviewers and less bug-bounty coverage.

Liquidity risk. Thin markets mean wider spreads, slippage and difficulty exiting during stress.

Security budget risk. Merge mining depends on miners choosing to participate. Lower participation weakens protection against reorganisations.

Bridge risk. Third-party bridges and wrapped assets carry their own trust assumptions beyond the native peg.

Phishing and fake tokens. Fake network entries, lookalike sites and copycat tokens target newcomers.

Defensive habits that help:

• Add the network and contract addresses only from official documentation.
• Test with a small transaction first.
• Use a hardware wallet for meaningful amounts and keep a separate wallet for experimenting.
• Review token approvals regularly and revoke those you no longer need.
• Check audits, admin keys and upgradeability before depositing.
• Do not borrow more than you can repay if prices move quickly.

Nothing here is financial advice. Crypto assets can lose value quickly, and DeFi positions can be liquidated. If a tool or platform is restricted where you live, follow local rules and do not try to bypass them.

If you decide to try RSK, a cautious, step-by-step approach reduces avoidable mistakes.

1. Read the official documentation. Find the developer portal through the project's verified channels and note the current network settings, explorer and peg instructions.
2. Set up a wallet. Use a wallet that supports custom EVM networks. Consider a new address that holds only what you plan to use. Back up the recovery phrase offline and never share it.
3. Add the network. Enter the settings exactly as published, including the chain ID and currency symbol (RBTC).
4. Get a small amount of RBTC. You can use the native peg, a faster liquidity-provider route, or an exchange that supports RBTC withdrawals on the RSK network. Confirm the network and address format before sending, because a wrong-network transfer can be unrecoverable.
5. Send a test transaction. Move a small amount between your own addresses and confirm it on an explorer.
6. Explore applications gradually. Start with a simple swap or a small deposit, and read each protocol's documentation, audits and risk disclosures.
7. Keep track of fees and approvals. Gas costs are paid in RBTC, so leave a reserve to exit positions.
8. Plan your exit. Know how you would return to BTC and how long that takes in stressed conditions.

Also check your local tax and regulatory rules for crypto activity. Prices, yields, liquidity and protocol status all change often, so look them up on independent dashboards at the time you act instead of trusting figures in old articles.