Scene 1: Understanding Signed States
The morning light had faded to a dull gray by the time Maya finally closed her laptop. She’d been staring at the blockchain explorer for hours, tracing every transaction, every signature, every timestamp. The adrenaline that had carried her through the night was fading, but her mind was still racing.
She needed to understand exactly what had happened. Not just the betrayal—she understood that well enough—but the technical details. How had Eli been able to submit an outdated state? How had the system allowed it? And most importantly, how had she been able to stop him?
The answers lay in something called “signed states.”
Maya opened a fresh browser window and pulled up the state channel tutorial she’d bookmarked. The section on signatures was technical, filled with cryptographic jargon, but she forced herself to read it carefully.
Digital Signatures in State Channels
Every state update in a state channel is cryptographically signed by both parties. This serves several critical purposes:
- Authentication: Proves that both parties agreed to the state
- Non-repudiation: Neither party can later deny they agreed
- Integrity: The state cannot be altered after signing
- Sequence Verification: Signatures are tied to specific sequence numbers
The signatures are generated using private keys that only each party possesses. This means that only the actual parties to the channel can create valid signatures for their states.
Maya scrolled down to find a visual representation. There it was—a diagram showing two users, each with a private key, signing a document that represented the game state.
“Okay,” she murmured, tracing the diagram with her finger. “So every time we made a move, we both signed off on it. That means the state is locked. Neither of us can change it without the other’s agreement.”
She opened her channel history and scrolled through the states. There were 847 of them, each one a snapshot of the game at a specific moment. She clicked on State #847—the final state, the one that proved her victory.
The details appeared on her screen:
State #847 Channel: GC-2026-04-15-MAYA-ELI Timestamp: 2026-04-15 15:02:47 UTC Sequence: 847 Game Data: [COMPRESSED BINARY DATA] Signatures: - Maya: 0x7F3A...9C2D [VALID] - Eli: 0x4B8E...1F7A [VALID] Status: CONFIRMED
“Both signatures are valid,” Maya read aloud. “That means Eli agreed to this state. He signed it with his own private key. There’s no way he can deny it.”
She clicked on State #412—Eli’s fraudulent submission.
State #412 Channel: GC-2026-04-15-MAYA-ELI Timestamp: 2026-04-15 12:02:47 UTC Sequence: 412 Game Data: [COMPRESSED BINARY DATA] Signatures: - Maya: 0x7F3A...9C2D [VALID] - Eli: 0x4B8E...1F7A [VALID] Status: DISPUTED
“Same signatures. Same channel. Same game. But a different state,” Maya said, her voice tight with anger. “Eli signed this state too. He agreed to it at the time. But then we played for another three hours, and he signed all those later states too. And then he tried to pretend the later ones didn’t exist.”
She slammed her fist on the desk. “How dare he? How dare he think he could get away with that?”
Pixel, startled by the noise, jumped off the bed and scurried out of the room.
Maya took a deep breath, forcing herself to calm down. “Okay. Okay. Getting angry isn’t going to help. I need to understand this. I need to know exactly what happened so I can explain it to others.”
She pulled up a comparison view, showing State #412 and State #847 side by side:
| State #412 | State #847 | |
|---|---|---|
| Sequence | 412 | 847 |
| Timestamp | 12:02 PM | 3:02 PM |
| Maya’s Fleet | 45 ships | 120 ships |
| Eli’s Fleet | 78 ships | 22 ships |
| Territory | Eli leads | Maya leads |
| Winner | Eli (would have been) | Maya (actual) |
| Signatures | Both valid | Both valid |
“The only difference is the game state,” Maya said slowly. “Everything else is identical. Same signatures. Same channel. Same players. But the game state tells a completely different story.”
She leaned back in her chair, thinking. “That’s the key. The blockchain doesn’t know who won the game. It doesn’t care about the game at all. All it cares about is which state is the most recent and which one has the highest sequence number.”
She smiled grimly. “And in that regard, my state wins. Hands down. No contest.”
She pulled up the state channel tutorial again and found the section on how the blockchain evaluates states.
How the Blockchain Validates States
When a state is submitted to the blockchain, the smart contract performs several checks:
- Signature Verification: Are the signatures valid and do they correspond to the correct parties?
- Sequence Number Check: Is the sequence number higher than any previously submitted state?
- Timestamp Check: Is the timestamp more recent than any previously submitted state?
- Channel Rules Check: Does the state comply with the channel’s rules?
If a state fails any of these checks, it is rejected. If multiple states pass all checks, the one with the highest sequence number and most recent timestamp is accepted as the final state.
“That’s why I won,” Maya realized. “My state had the higher sequence number and the more recent timestamp. Eli’s state failed the sequence number check and the timestamp check. It was rejected.”
She pulled up the transaction history for her channel and found the exact moment when the blockchain had processed her submission.
Transaction: 0x9F3A...7C2D Type: State Submission Channel: GC-2026-04-15-MAYA-ELI State: #847 Timestamp: 2026-04-15 15:08:12 UTC Result: ACCEPTED
Then she found Eli’s submission:
Transaction: 0x4B8E...1F7A Type: State Submission Channel: GC-2026-04-15-MAYA-ELI State: #412 Timestamp: 2026-04-15 12:03:15 UTC Result: DISPUTED - LATER STATE EXISTS
“Later state exists,” Maya read aloud. “The blockchain recognized that there was a more recent state. It rejected Eli’s submission automatically.”
She felt a wave of satisfaction wash over her. “Eli thought he could cheat the system. But the system is designed to catch exactly this kind of fraud. He never stood a chance.”
But then a troubling thought occurred to her. “What if I hadn’t been paying attention? What if I had been offline when Eli submitted his state?”
She opened the watchtower interface. There it was—the record of the watchtower’s actions:
Watchtower: Sentinel Channel: GC-2026-04-15-MAYA-ELI Event: Fraudulent State Detected Timestamp: 2026-04-15 12:03:18 UTC Action: Submitted Correct State (#847) Result: Successful Note: User (Maya) was offline at time of detection.
“If I had been offline,” Maya said slowly, “the watchtower would have protected me. It would have submitted my state automatically, just like it did.”
She felt a surge of gratitude toward the watchtower service. “Two tokens a month. That’s a small price to pay for protection against cheaters.”
She looked at the channel status one more time:
Channel: GC-2026-04-15-MAYA-ELI Status: CLOSED Final State: #847 Winner: Maya Collateral Distribution: - Maya: 60 tokens - Eli: 20 tokens - Penalty Applied: Yes
“It’s over,” Maya said softly. “I won. Eli lost. Justice was served.”
She closed the blockchain explorer and leaned back in her chair, exhausted. The past twelve hours had been a whirlwind of discovery, betrayal, and victory. She’d learned more about state channels than she ever thought possible.
But there was still more to learn. She opened a new document and started typing:
“State Channels: A Beginner’s Guide to Blockchain Gaming”
She was going to share everything she’d learned with the gaming community. No one else should have to go through what she’d just experienced without knowing how to protect themselves.
Scene 2: The Betrayal
The memory of Eli’s betrayal was still fresh in Maya’s mind. She couldn’t stop replaying the moment when she’d seen his submission on the blockchain.
“It was midnight,” she told Pixel, who had returned to his spot on the bed. “I was tired, but I couldn’t sleep. Something felt wrong.”
She opened her chat history with Eli, scrolling back to the end of the game.
Eli: “GG. That was honestly the best match I’ve played in months.”
Maya: “Same here. No lag, no fees, just the game. This is how it should be.”
Eli: “So, we close the channel with the final state?”
Maya: “Yeah. I’ll submit the final state to the blockchain, and we split the deposit based on the result.”
Eli: “Sounds good to me. I’m ready to close it out.”
Maya had felt so good at that moment. So triumphant. She’d won the game fair and square. She’d proven that state channels worked. Everything was perfect.
Then Eli had gone silent.
Maya: “Eli?”
No response.
Maya: “I can’t close the channel without your confirmation.”
Still nothing.
Maya: “We need to resolve this. Please respond.”
More silence.
“I should have known something was wrong,” Maya said bitterly. “Eli never just logs off. He’s always online. Always available. The only reason he would go silent is if he was planning something.”
She scrolled to the next set of messages—the ones after she’d discovered his fraud.
Maya: “Eli, I know what you did. You submitted State #412.”
Eli: “I don’t know what you’re talking about.”
Maya: “Don’t lie to me. I can see it on the blockchain. You submitted an outdated state.”
Eli: “I was just checking something. It was a mistake.”
Maya: “A mistake? You don’t ‘accidentally’ submit a state to the blockchain. It requires multiple confirmations.”
There was a long pause before Eli responded.
Eli: “Okay, fine. I submitted it. But I was just trying to see if it would work. I didn’t think you’d notice.”
Maya: “You didn’t think I’d notice? You submitted a state that shows you winning, and you didn’t think I’d notice?”
Eli: “I was going to withdraw it. I swear.”
Maya: “Withdraw it? States on the blockchain can’t be withdrawn. They’re permanent. You were trying to steal the win.”
Another long pause.
Eli: “I’m sorry, Maya. I don’t know what came over me. I just… I really wanted to win.”
Maya: “You were winning! You were in the lead until the middle of the game. But then I outplayed you. Fair and square. And you couldn’t accept it.”
Eli: “I know. I’m sorry. I didn’t think you would find out.”
Maya: “The blockchain is transparent, Eli. Everything is recorded. Anyone can see it. Did you really think you could hide it?”
Eli: “I don’t know what I was thinking. I messed up.”
Maya shook her head as she read the messages again. “He didn’t think I’d find out. That’s the part that gets me. He didn’t think I’d be paying attention. He thought I’d just accept whatever the blockchain said.”
She opened the blockchain explorer and found Eli’s state submission again.
Transaction: 0x4B8E...1F7A Type: State Submission Channel: GC-2026-04-15-MAYA-ELI State: #412 Timestamp: 2026-04-15 12:03:15 UTC
“He submitted it at 12:03 PM,” Maya said. “Just three minutes after the game ended. He didn’t even wait. He didn’t hesitate. He had this planned all along.”
She felt a cold anger rising in her chest. “Eli wasn’t just a sore loser. He was a cheater. He planned to submit an outdated state from the very beginning.”
She thought back to the game. Had Eli been playing differently? Had he been setting up for this? She reviewed the game’s state history and found something interesting.
State #412 had been saved at 12:00 PM—the exact moment when Eli had taken the lead. It was the high point of his game, the moment when he’d thought he would win.
“He saved that state deliberately,” Maya realized. “He knew he might lose, so he saved a state where he was winning. Then, when he actually lost, he submitted the saved state instead of the final one.”
She was furious. But she was also impressed. It was a clever plan—if it had worked.
“If I hadn’t been paying attention,” she said slowly, “if I hadn’t been online at the exact right moment, Eli would have succeeded. The blockchain would have accepted his state, and I would have lost everything.”
She pulled up her watchtower logs again. “But I had the watchtower. And the watchtower submitted my state before I even knew what was happening.”
She smiled grimly. “Eli’s plan was clever, but it wasn’t clever enough. He didn’t account for the watchtower. He didn’t account for the challenge period. He didn’t account for the fact that I would fight back.”
She closed the chat history and looked at her current balance. Sixty tokens. That was more than she’d had before the match. She’d actually made a profit while teaching a cheater a lesson.
“The universe has a sense of justice,” she said to Pixel. “Sometimes it just needs a little help from technology.”
Scene 3: The Battle Plan
After the initial shock of the betrayal had faded, Maya had switched into full battle mode. She’d opened every research window she could find, pulled up every tutorial, every forum post, every technical document she could get her hands on.
“I need to understand everything,” she’d told herself. “Every possible outcome. Every counter-strategy. I’m not going to lose because I didn’t prepare.”
She’d started with the basics: what was a state channel, how did it work, and what were its vulnerabilities?
State Channel Vulnerabilities
While state channels are generally secure, there are several attack vectors:
- Outdated State Submission: One party submits an old state instead of the current one.
- Force Close Abuse: A party force-closes a channel to lock in a favorable state.
- Watchtower Failures: If a watchtower fails to act, the correct party may lose.
- Timing Attacks: Submitting states at times when the other party is likely to be offline.
Maya had studied each vulnerability carefully. “Eli used the first one—outdated state submission. He submitted an old state hoping I wouldn’t notice.”
She’d then researched how to defend against each attack:
Defenses Against State Channel Attacks
- Watchtowers: Third-party services that monitor channels and submit correct states.
- Challenge Periods: Time windows for disputing fraudulent submissions.
- Penalty Mechanisms: Automatic penalties for fraudulent behavior.
- Multi-Signature Requirements: Requiring both parties to sign off on state changes.
“Watchtowers and challenge periods,” Maya said. “Those are my best defenses. I need to make sure I have both set up for every match.”
She’d opened the watchtower interface again and reviewed the settings.
Watchtower: Sentinel Status: Active Channels Monitored: 1 Current Channel: GC-2026-04-15-MAYA-ELI State Stored: #847 (Correct) Action History: 1 dispute intervention
“Sentinel did exactly what it was supposed to,” Maya said. “It detected the fraudulent state and submitted my correct state. Without it, I might have lost.”
She’d then reviewed the challenge period rules.
Challenge Periods: A Critical Window
When a state is submitted to the blockchain, there is a designated “challenge period” during which the other party can dispute the submission. The challenge period is typically 24 hours, giving the correct party time to respond.
During the challenge period, either party may:
- Submit their own version of the state
- Submit additional evidence
- Force close the channel
If no challenge is submitted, the state is finalized at the end of the challenge period.
“I submitted my state within minutes,” Maya said. “But I had a full 24 hours. Plenty of time to respond.”
She’d thought about what would have happened if she’d been offline. “If I’d been asleep, the watchtower would have submitted the state for me. But if I didn’t have the watchtower, and I was offline for 24 hours, I would have lost.”
She’d decided to always have a watchtower active. “Two tokens a month. That’s all it takes for complete protection. It’s the best insurance I could buy.”
She’d then researched the penalty mechanism.
Penalties for Fraudulent Behavior
To discourage fraud, state channel smart contracts typically include penalty mechanisms. Common penalties include:
- Collateral Forfeiture: The cheating party loses all or part of their collateral.
- Fee Penalties: Additional fees are deducted from the cheating party’s wallet.
- Reputation Damage: The fraud is recorded on the blockchain, where it cannot be hidden.
- Channel Closure: The channel is force-closed, ending the relationship.
“Eli lost 50% of his collateral,” Maya said. “Twenty tokens. That’s a significant penalty. It should make him think twice before cheating again.”
She’d also researched the force close mechanism.
Force Close: A Last Resort
If one party refuses to cooperate in closing a channel, the other party can “force close” the channel. This involves submitting the final state to the blockchain and waiting for the challenge period to expire.
Force close should be used when:
- The other party is unresponsive
- The other party has submitted a fraudulent state
- There is a dispute that cannot be resolved cooperatively
“I used the force close mechanism,” Maya said. “That’s what submitted my state to the blockchain. It was the only way to finalize the channel without Eli’s cooperation.”
She’d closed all the research windows and looked at the clock. It was 3:00 AM.
“I should sleep,” she said to Pixel. “But I can’t. I’m too wired.”
She’d opened a new document and started writing a guide for other gamers.
How to Protect Yourself in State Channels
- Use a watchtower: It’s worth the small fee.
- Know the challenge period: 24 hours is typical.
- Understand penalties: Know what happens if someone cheats.
- Learn the force close process: Sometimes you need to act unilaterally.
- Keep your private key safe: Your signature proves your agreement.
She’d smiled as she typed. “I’m going to make sure no one else goes through what I just did. If I can help even one person avoid being cheated, it’ll be worth it.”
Scene 4: The Aftermath
The morning after the dispute, Maya had woken up feeling strange. It was over. The channel was closed. Eli had been penalized. She had won.
But she still felt unsettled.
“I trusted Eli,” she told Pixel. “I thought we were friends. Or at least friendly rivals. I never thought he would try to cheat me.”
She’d opened her messages and found a new one from Eli.
Eli: “Maya, I’m really sorry about what I did. I don’t have any excuse. I just wanted to win so badly that I didn’t think about the consequences. You deserved better. I hope you can forgive me someday.”
Maya had stared at the message for a long time. Part of her wanted to delete it and never speak to Eli again. Another part of her wanted to respond with anger, to let him know exactly how much his betrayal had hurt.
But instead, she’d taken a deep breath and responded calmly.
Maya: “I accept your apology. But I want you to understand something. It wasn’t just about the game. It was about trust. You broke my trust, and that’s not something that can be fixed easily.”
Eli: “I know. I understand. I’ll never do anything like that again. I promise.”
Maya: “I believe you. But I’m going to be more careful from now on. And you should too. The blockchain records everything. Every mistake, every cheat, every wrong decision. It’s all permanent.”
Eli: “I learned that lesson the hard way. I’ve lost my deposit, my reputation, and your trust. It wasn’t worth it.”
Maya: “No, it wasn’t. But now you know. And maybe you can help others avoid the same mistake.”
Eli: “What do you mean?”
Maya: “I’m writing a guide about state channels. About how to use them safely. About how to avoid getting cheated. I think you should contribute. Tell your side of the story. Help others understand why cheating is never worth it.”
There was a long pause before Eli responded.
Eli: “You’d let me help with your guide? After what I did?”
Maya: “It’s the best way to make sure this never happens again. If we can educate people, we can prevent future attempts at fraud. That benefits everyone.”
Eli: “I… I don’t know what to say. Thank you. I’ll help. I’ll tell the truth about what I did. Maybe it’ll help someone avoid making the same mistake.”
Maya: “That’s all I ask.”
She’d closed the messages and looked at the guide she was writing. It was coming together nicely—a comprehensive overview of state channels, their benefits, their vulnerabilities, and how to protect against fraud.
“State channels are fast, cheap, and secure,” she wrote. “But they’re only as secure as the people using them. The technology can protect you, but you also need to protect yourself. Use watchtowers. Understand challenge periods. Know your rights.”
She’d added a section on penalties.
“Cheating in state channels is a losing proposition. The penalty mechanism ensures that cheaters lose their deposits, their reputation, and their ability to play in future games. It’s just not worth the risk.”
She’d smiled as she wrote that last sentence. “Eli learned that lesson. Hopefully, others will learn it too.”
Scene 5: A New Beginning
Two weeks after the dispute, Maya was back in the gaming lobby. She’d been playing matches regularly, always using state channels, always with a watchtower active.
The experience with Eli had changed her. She was more careful now, more vigilant. She checked her channel status regularly. She monitored the blockchain for any unusual activity. She’d even started a small group of gamers who were interested in learning about state channels.
“Welcome to the State Channel Society,” she said to the group’s first meeting. “I’m Maya, and I’m going to teach you everything I know about playing blockchain games without paying excessive fees.”
The group was small—only six people—but they were enthusiastic. They’d all heard horror stories about high transaction fees. They were ready for a solution.
“State channels are the answer,” Maya continued. “They allow you to make thousands of moves off-chain, with no fees, and then settle the final result on-chain. It’s fast, cheap, and secure.”
“But what about cheaters?” one of the group members asked. “I heard about someone who tried to submit an outdated state.”
“That was me,” Maya said calmly. “And yes, it happened. But I was protected by a watchtower and the challenge period. I won the dispute, and the cheater was penalized.”
She explained the entire story—the game, the betrayal, the dispute, the resolution. The group listened in silence, their eyes wide.
“So you’re saying,” one of them said slowly, “that if I use a watchtower, I’ll never lose to a cheater?”
“Nothing is guaranteed,” Maya said. “But the system is designed to protect honest players. If you understand how it works, you can protect yourself.”
The group nodded, absorbing the information. Maya could see their confidence growing. They were no longer afraid of being cheated.
“State channels are the future of blockchain gaming,” Maya concluded. “They’re fast, cheap, and disputable. And if we all work together to educate the community, we can make cheating a thing of the past.”
That evening, Maya sat in her room and looked at the view from her window. The sun was setting, casting a warm orange glow over the neighborhood. It was peaceful. Calm.
She thought about everything that had happened. The discovery of state channels. The first match with Eli. The betrayal. The dispute. The victory.
“Fast, cheap, and disputable,” she murmured. “That’s the motto of state channels. And now I understand what it really means.”
She opened her guide and added a final section.
The Three Pillars of State Channels
- Fast: Thousands of moves off-chain, instant confirmations.
- Cheap: Only one on-chain transaction for settlement.
- Disputable: Built-in mechanisms for resolving conflicts.
State channels combine the speed and efficiency of off-chain interactions with the security and accountability of on-chain disputes. They’re the perfect solution for blockchain gaming, payments, and more.
She saved the document and looked at her next gaming session. She had a tournament match tomorrow—the first round of the championship she’d been training for.
“Here we go,” she said to Pixel. “Time to show everyone what state channels can do.”
She opened the channel creation interface and sent an invitation to her next opponent. Within seconds, the channel was open.
“Let the games begin,” Maya said, and she started to play.
Table of contents:
Introduction
Chapter 1: The High-Fee Network
Chapter 2: A State Channel Solution
Chapter 3: The Off-Chain Agreement
Chapter 4: The Dispute Resolution <<<<<< NEXT
Chapter 5: The Watchtower
Chapter 6: The Force Close
Chapter 7: The Outdated State
Chapter 8: The Challenge Period
Chapter 9: The Penalty Mechanism
Chapter 10: Fast, Cheap, and Disputable
