BSC is setting aside 5% of block capacity for payments. Could transfers spend less time waiting in line during congestion?
On October 16, BNB Chain released v1.8.1, which includes a change that could matter to everyday users: Payment Lane. Under this design, 5% of the block’s gas capacity is reserved by default for eligible BNB transfers and transactions involving payment contracts on an approved list.
First, a note on the rollout: this version is for the Chapel testnet, with the Jenner upgrade scheduled for October 29 at 10:30 a.m. Beijing time. No mainnet activation date has been set for this release, so “the code is out” does not mean your transfers are already faster today.
Why reserve space separately? Imagine a popular project opening for a token sale, and a flood of transactions hits the chain all at once. You just want to send someone money, but now you have to compete with everyone trying to get their transactions through. Even a fast chain can get especially busy at times. Payment Lane is intended to stop payments from being pushed out by other traffic.
One thing to be clear about: 5% does not mean a 5% discount on every transfer, nor does it mean a 5% return. Here, gas refers to the amount of computational work a block can process; what’s reserved is processing capacity. Payments can still compete for other capacity, so 5% is not a cap on how much payment traffic can use.
There’s another easy-to-miss detail: under the current proposal, if the reserved capacity goes unused, regular transactions generally can’t use it. The upside is that payments have a guaranteed baseline of capacity; the trade-off is that some capacity may occasionally sit idle.
For people who use the BNB network for everyday payments, the key thing to watch is the wait during congestion. But this ensures only that payment transactions have some space; it doesn’t promise that your specific transaction will be included in a block. Existing fee and ordering rules still apply, and this is not the same as eliminating gas fees or guaranteeing instant delivery. Which contracts make the approved list and how the capacity is adjusted will depend on governance and future deployments.
I’ll keep an eye on congestion tests on the testnet, parameter changes, and mainnet plans. More than how many times faster it gets, I want to know: when everyone is competing to get through, can an ordinary transfer still go through smoothly? Which matters more to you: low fees in everyday use, or reliable delivery even when things get busy?
Sources: BNB Chain v1.8.1 and BEP-703, checked October 17
https://github.com/bnb-chain/bsc/releases/tag/v1.8.1
https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP-703.md
#BNB #BSC #OnchainPayments
On October 16, BNB Chain released v1.8.1, which includes a change that could matter to everyday users: Payment Lane. Under this design, 5% of the block’s gas capacity is reserved by default for eligible BNB transfers and transactions involving payment contracts on an approved list.
First, a note on the rollout: this version is for the Chapel testnet, with the Jenner upgrade scheduled for October 29 at 10:30 a.m. Beijing time. No mainnet activation date has been set for this release, so “the code is out” does not mean your transfers are already faster today.
Why reserve space separately? Imagine a popular project opening for a token sale, and a flood of transactions hits the chain all at once. You just want to send someone money, but now you have to compete with everyone trying to get their transactions through. Even a fast chain can get especially busy at times. Payment Lane is intended to stop payments from being pushed out by other traffic.
One thing to be clear about: 5% does not mean a 5% discount on every transfer, nor does it mean a 5% return. Here, gas refers to the amount of computational work a block can process; what’s reserved is processing capacity. Payments can still compete for other capacity, so 5% is not a cap on how much payment traffic can use.
There’s another easy-to-miss detail: under the current proposal, if the reserved capacity goes unused, regular transactions generally can’t use it. The upside is that payments have a guaranteed baseline of capacity; the trade-off is that some capacity may occasionally sit idle.
For people who use the BNB network for everyday payments, the key thing to watch is the wait during congestion. But this ensures only that payment transactions have some space; it doesn’t promise that your specific transaction will be included in a block. Existing fee and ordering rules still apply, and this is not the same as eliminating gas fees or guaranteeing instant delivery. Which contracts make the approved list and how the capacity is adjusted will depend on governance and future deployments.
I’ll keep an eye on congestion tests on the testnet, parameter changes, and mainnet plans. More than how many times faster it gets, I want to know: when everyone is competing to get through, can an ordinary transfer still go through smoothly? Which matters more to you: low fees in everyday use, or reliable delivery even when things get busy?
Sources: BNB Chain v1.8.1 and BEP-703, checked October 17
https://github.com/bnb-chain/bsc/releases/tag/v1.8.1
https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP-703.md
#BNB #BSC #OnchainPayments