📢 Gate Square Exclusive: #WXTM Creative Contest# Is Now Live!
Celebrate CandyDrop Round 59 featuring MinoTari (WXTM) — compete for a 70,000 WXTM prize pool!
🎯 About MinoTari (WXTM)
Tari is a Rust-based blockchain protocol centered around digital assets.
It empowers creators to build new types of digital experiences and narratives.
With Tari, digitally scarce assets—like collectibles or in-game items—unlock new business opportunities for creators.
🎨 Event Period:
Aug 7, 2025, 09:00 – Aug 12, 2025, 16:00 (UTC)
📌 How to Participate:
Post original content on Gate Square related to WXTM or its
Off-chain Scalability Depth Analysis: From Concept to State Channel Practice
Off-chain Scalability Depth Analysis
1. The Necessity of Scaling
The future vision of blockchain is decentralization, security, and scalability, but usually only two of these can be achieved, which is known as the blockchain trilemma. For many years, people have been exploring how to improve the throughput and transaction speed of blockchain while ensuring decentralization and security, that is, to solve the scalability issue, which is one of the hot topics in the current development process of blockchain.
The decentralization, security, and scalability of blockchain are defined as follows:
Decentralization: Anyone can become a node to participate in the production and verification of the blockchain system. The more nodes there are, the higher the degree of decentralization, thus ensuring that the network is not controlled by a small group.
Security: The higher the cost to gain control over the blockchain system, the higher the security, and the chain can resist a larger proportion of participant attacks.
Scalability: The ability of blockchain to handle a large number of transactions.
The first significant hard fork of the Bitcoin network originated from scalability issues. As the number of users and transaction volume increased, the 1MB block limit of the Bitcoin network began to face congestion; since 2015, the Bitcoin community has had disagreements regarding scalability, with one side supporting larger blocks and the other side advocating for the Segwit solution to optimize the main chain structure. On August 1, 2017, the side supporting scalability independently developed an 8MB block client system that began operating, leading to the first significant hard fork in Bitcoin's history, resulting in the creation of the new cryptocurrency BCH.
The Ethereum network also chooses to sacrifice some scalability to ensure the security and decentralization of the network. Although Ethereum does not limit the block size like Bitcoin, it sets a cap on the gas fees that can be accommodated in a single block, but the goal is to achieve trustless consensus and ensure the widespread distribution of nodes.
From the rise of on-chain applications such as CryptoKitties in 2017, the DeFi summer, to later GameFi and NFTs, the market's demand for throughput has been increasing. However, Ethereum can still only process 15-45 transactions per second. This has led to increased transaction costs and longer settlement times, making it difficult for most DApps to bear operational costs, causing the entire network to become slow and expensive. The issue of blockchain scalability urgently needs to be addressed. The ideal scalability solution is to increase the transaction speed and throughput of the blockchain network as much as possible without sacrificing decentralization and security.
2. Types of Scalability Solutions
We categorize the scaling solutions into two main types: on-chain scaling and off-chain scaling, based on the criterion of "whether to change a layer of the mainnet."
2.1 On-chain Scaling
Core concept: a solution to achieve scalability by altering a layer of the mainnet protocol, with the current main solution being sharding.
There are various solutions for on-chain scalability, this article will not elaborate, briefly listing two:
The first solution is to expand the block space, which means increasing the number of transactions packed in each block. However, this will raise the requirements for high-performance node devices, increase the entry threshold for nodes, and reduce the degree of "decentralization".
Plan two is sharding, which divides the blockchain ledger into several parts. Instead of every node participating in all bookkeeping, different shards, that is, different nodes, are responsible for different bookkeeping. Parallel computing can handle multiple transactions simultaneously; this can reduce the computational pressure on nodes and the entry threshold, improving transaction processing speed and the degree of decentralization. However, this means that the entire network's computing power is dispersed, which will reduce the overall "security" of the network.
Modifying the code of a layer one mainnet protocol may result in unpredictable negative impacts, as any slight security vulnerability in the underlying layer could severely threaten the overall security of the network, which may be forced to undergo a fork or interrupt for repair upgrades.
2.2 off-chain scaling
Core concept: a scaling solution that does not change the existing Layer 1 mainnet protocol.
The off-chain scaling solutions can be further subdivided into Layer 2 and other solutions:
3. Off-chain scaling solutions
3.1 State Channels
3.1.1 Overview
State channels stipulate that users only need to interact with the main network when opening, closing, or resolving disputes in the channel, while keeping interactions between users off-chain to reduce transaction time and costs, and to achieve unlimited transaction frequency.
State channels are simple P2P protocols suitable for "turn-based applications" such as two-player chess games. Each channel is managed by a multi-signature smart contract running on the mainnet, which controls the assets deposited into the channel, validates state updates, and arbitrates disputes between participants. After the participants deploy the contract on the network, they deposit funds and lock them in place, and after both parties sign to confirm, the channel officially opens. The channel allows participants to conduct an unlimited number of off-chain free transactions ( as long as the net transfer value does not exceed the total amount deposited ). Participants take turns sending state updates to each other, waiting for the other party's signature confirmation. Once the other party's signature is confirmed, the state update is considered complete. Normally, state updates agreed upon by both parties are not uploaded to the mainnet; they only rely on the mainnet for confirmation in case of disputes or when the channel is closed. When it's necessary to close the channel, any participant can submit a transaction request on the mainnet, which will be executed on-chain immediately if it receives unanimous signature approval; if other participants do not give signature approval, then everyone must wait for the "challenge period" to end before receiving the remaining funds.
In summary, the state channel solution can greatly reduce the computational load on the mainnet, improve transaction speed, and lower transaction costs.
3.1.2 Timeline
3.1.3 Technical Principles
The general workflow of state channels is as follows:
Alice and Bob deposit funds from their personal EOA to the on-chain contract address, and these funds are locked in the contract until they are returned to the user when the channel is closed; after both parties sign to confirm, the state channel between the two is officially opened.
Alice and Bob can conduct unlimited off-chain transactions, with participants communicating with each other through encrypted signed messages ( instead of communicating with the blockchain network ). Both parties need to sign each transaction to prevent double spending. Through these messages, they propose updates to their account states and accept the state updates proposed by the other party.
If Alice wants to close the channel and end the transaction with Bob, Alice needs to submit the final state of her account to the contract. If Bob signs to approve, the contract will release the locked funds back to the corresponding user based on the final state. If Bob does not respond with a signature, the contract will release the locked funds back to the corresponding user after the challenge period ends.
3.1.4 Advantages and Disadvantages
Advantages:
Disadvantages:
3.1.5 Application
Bitcoin Lightning Network:
Overview: The Lightning Network is a micropayment channel on the Bitcoin network, with a technological evolution from unidirectional payment channels to bidirectional payment channels and then to multi-party payment networks. By using off-chain micropayment channels and leveraging intermediaries to form a transaction network, it can solve the scalability issue of the Bitcoin network. The process follows "Deposit ( establish channel ) → Lightning Network transaction ( update channel status ) → Refund/settlement ( close channel )"; theoretically, it can handle one million transactions per second.
Timeline:
Ecological Development: The Lightning Network ecosystem includes from bottom to top: the underlying BTC network, core infrastructure ( solutions, node and liquidity services ), and various DApps. As of November 2022, there are over 20 categories and more than 100 applications based on the Lightning Network, mainly including payments, wallets, node management, browser extensions, podcasts, and streaming.
Ethereum Lightning Network:
Overview: The Lightning Network is a micropayment channel based on Ethereum, similar to the Lightning Network, which expands on-chain transactions by establishing state channels, aiming to achieve near-instant, low-cost, and scalable ERC20 token payments.
Timeline:
Currently not widely adopted, reasons include:
Celer Network: