Blockchain scaling· 11 min read
Channels are the quickest option on paper. But they only work when somebody has funds parked on the receiving side, so this paper is mostly about that: capacity lockup, rebalancing, routing, and what happens when liquidity runs out mid-route.
The summary above is the current state of it. The full post goes up once the work behind it is finished and reviewed, which is the same rule we apply to everything else on the site.
Back to all postsState Channels · Channel Liquidity
Throughput limits, block capacity, congestion, fees that jump around, and confirmation times. Many small frequent transfers turn out to be a hard traffic pattern for a base layer to handle.
· 9 min read
Doubling the shards roughly doubles the capacity, but only for transfers that stay inside one shard. A remittance has three parties by default, so it is cross-shard from the start, and adding shards makes that more likely rather than less.
· 9 min read
A sidechain is fast because it runs on its own small validator set, and that is the same reason Ronin lost $625 million. Whether one could carry remittances comes down to whether its validators, its bridge and its settlement are chosen on purpose rather than inherited.
· 9 min read
