State channels allow participants to transact
x number of times off-chain while only submitting two on-chain transactions to the Ethereum network. This allows for extremely high transaction throughput.
You should have a good understanding of all the foundational topics and a high-level understanding of Ethereum scaling. Implementing scaling solutions such as channels is an advanced topic as the technology is less battle-tested, and continues to be researched and developed.
Participants must lock a portion of Ethereum's state, like an ETH deposit, into a multisig contract. A multisig contract is a type of contract that requires the signatures (and thus agreement) of multiple private keys to execute.
Locking the state in this way is the first transaction and opens up the channel. The participants can then transact quickly and freely off-chain. When the interaction is finished, a final on-chain transaction is submitted, unlocking the state.
- lots of state updates
- when number of participants is known upfront
- when participants are always available
There are two types of channels right now: state channels and payment channels.
State channel are perhaps best explained through an example, such as a game of tic tac toe:
Create a multisig smart contract “Judge” on the Ethereum main-chain that understands the rules of tic-tac-toe, and can identify Alice and Bob as the two players in our game. This contract holds the 1ETH prize.
Then, Alice and Bob begin playing the game, opening the state channel. Each move creates an off-chain transaction containing a “nonce”, which simply means that we can always tell later in what order the moves happened.
When there's a winner, they close the channel by submitting the final state (e.g. a list of transactions) to the Judge contract, paying only a single transaction fee. The Judge ensures that this “final state” is signed by both parties, and waits a period of time to ensure that no one can legitimately challenge the result, and then pays out the 1ETH award to Alice.
Simplified state channels that only deal with payments (e.g. ETH transfers). They allow off-chain transfers between two participants, as long as the net sum of their transfers does not exceed the deposited tokens.
|Instant withdrawal/settling on Mainnet (if both parties to a channel cooperate)||Time and cost to set up and settle a channel - not so good for occasional one-off transactions between arbitrary users.|
|Extremely high throughput is possible||Need to periodically watch the network (liveness requirement) or delegate this responsibility to someone else to ensure the security of your funds.|
|Lowest cost per transaction - good for streaming micropayments||Have to lockup funds in open payment channels|
|Don't support open participation|
Multiple projects provide implementations of state channels that you can integrate into your dapps:
- EthHub on state channels
- Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit – Josh Stark, Feb 12 2018
- State Channels - an explanation Nov 6, 2015 - Jeff Coleman
- Basics of State Channels District0x
Know of a community resource that helped you? Edit this page and add it!
Help us with this page
If you're an expert on the topic and want to contribute, edit this page and sprinkle it with your wisdom.
You'll be credited and you'll be helping the Ethereum community!
Use this flexible documentation template
Questions? Ask us in the #content channel on our Discord serverEdit page