Scaling on RSK Network

Looking ahead, I foresee that Sovryn will face similar issues to existing DeFi platforms on the Ethereum network like Compound, Maker, SUSHI, etc.

Starting a thread for discussions around scaling of the RSK network as adoption on Sovryn increases traffic on the RSK network.


  • How many transactions per second are allowed today on RSK?

The number of transactions per second executable on the RSK platform is determined by the block gas limit and the average block rate. The current average block rate is one block every 30 seconds. At each mined block, the miner can vote to increase the block gas limit. Currently the block gas limit is 6.8M gas units per block. A simple RBTC transaction consumes 21K gas, so the RSK platform can execute 11 transactions per second today. This limit could increase in the future as there are several improvement proposals that lower the resources required to process transactions on the RSK network.

For example, RSKIP04 enables parallel processing of transactions. If the proposal is accepted by the community, the block gas limit could easily double.

Both the LTCP protocol, as described in the white-paper and in RSKIP53, and the shrinking-chain scaling technique could result in a ten-fold reduction in the amount of space required.

If these proposals are accepted by the community, transaction speeds could be expected to reach 100 transactions per second.

  • How many transactions per second will the RSK Network withstand?

Beta releases of improved RSK nodes have been tested to accommodate 100 tx/s without incident. As the technology improves, transactions per second may similarly increase. The goal of RSK Labs is to reach up to 20,000 tx/sec using its Lumino technology, which is a second layer off-chain payment network that will be embedded on RSK’s reference node in the following release.

  • What is the transaction confirmation time?

On average, the network currently generates a block every 30 seconds. Miners can reduce the average block time to 15 seconds by optimizing their merge-mining operations. Systems that receive payments over RSK in exchange for a good or service outside the RSK blockchain should wait a variable number of confirmation blocks, depending on the amount involved in the payments. A minimum of 12 confirmations is recomended, which corresponds to an average delay of 6 minutes.

RIF - Layer 3 scaling solution for RSK


I don’t think the right approach is to try scale RSK L1. Scaling occurs on L@. Which is why we are working on a Rollup.


Yo Edan! I just listened to your talk with Anthony Pompliano. So cool to hear about your history and vision. I was left with one remaining question after participating in Origin presale and using RSK network to move some rBTC to cover gas for claiming SOV when time comes… how will RSK scale? That’s what brought me here. I see the merit in your scrutiny of wBTC as well and the need for a vertical scaling solution. I’m just hoping that RIF layer 3 will solve scaling and transaction cost issues.