Scene 1: Setting Up the Channel
The morning sun streamed through Maya’s window, casting warm golden rectangles across her cluttered desk. Empty energy drink cans stood like sentinels around her keyboard. A half-eaten bag of chips had somehow migrated to her bookshelf overnight. But Maya noticed none of it. Her eyes were locked on her screen, burning with the intensity of a thousand suns.
She’d been up all night researching.
The discovery of state channels had ignited something in her—a fire that refused to be extinguished by something as trivial as sleep. She’d devoured every article, every tutorial, every forum post she could find. Her browser had thirty-seven tabs open, each one containing another piece of the puzzle.
“Okay,” she muttered, cracking her knuckles. “Let’s do this.”
The game launcher for Galactic Conquest loaded with its familiar orchestral fanfare. Maya navigated to the multiplayer lobby, her heart pounding with anticipation. The lobby was busier than usual—morning players from the Eastern hemisphere mixed with night owls from the West. Chat scrolled by at a dizzying pace.
She found Eli’s name in her friends list. He was online, which was unusual for this hour. He must have been just as excited as she was.
Maya: “Morning! You’re up early.”
Eli: “Couldn’t sleep. Too excited about this state channel thing.”
Maya: “Same. I’ve been reading about it all night.”
Eli: “I think I understand the basics. We deposit tokens, play off-chain, then settle.”
Maya: “Exactly. Ready to try it?”
Eli: “Born ready. How do we start?”
Maya pulled up the channel creation interface. It was buried deep in the game’s advanced settings—a feature that most players probably never even knew existed. The interface was clean but technical, filled with fields and parameters that would intimidate any casual gamer.
Maya, however, felt right at home.
“Let’s see,” she murmured, filling in the fields one by one. “Channel duration: 24 hours. Game parameters: Standard Galactic Conquest rules. Collateral: hmm…”
She paused at the collateral field. This was the most important decision. The collateral was the amount of tokens each player would deposit into the channel. It served as a security deposit—if either player tried to cheat, they could lose part or all of their deposit.
Fifty tokens was her initial thought. But after a night of research, she was second-guessing that number.
“What if something goes wrong?” she asked herself. “What if the channel bugs out or I make a mistake? I could lose everything.”
She thought about her total balance. Fifty-three tokens. That was all she had. If she deposited fifty and something went wrong, she’d be left with almost nothing.
But on the other hand, the collateral needed to be high enough to make the game meaningful. If the stakes were too low, what was the point?
“Forty tokens,” she decided. “Forty tokens each. That leaves me with thirteen in reserve. Enough to keep playing if this fails.”
She typed in the number, then moved to the next field.
“Game Type: Competitive Match. Winner takes collateral.”
Simple. Clean. No complicated split mechanisms.
“Channel Rules: Both parties must agree on final state. Dispute resolution enabled.”
Maya checked the “dispute resolution” box without fully understanding what it meant. The tutorial had mentioned it briefly, but the details were fuzzy. Something about challenge periods and fallback mechanisms. She made a mental note to look into it later.
“Alright. All set.” She took a deep breath. “Eli, I’m sending you the channel invitation.”
Maya: “Channel invitation sent. Check your notifications.”
Eli: “I see it. Looks like you set the collateral at 40 tokens.”
Maya: “Yeah, I figured that was a good amount. High enough to matter, low enough that we’re not risking everything.”
Eli: “Works for me. I’m accepting.”
A notification appeared on Maya’s screen:
“Eli has accepted your channel invitation. Channel opening in progress…”
Maya’s pulse quickened. This was it. The moment of truth.
“Required actions: Both parties must deposit collateral. Your deposit: 40 tokens. Eli’s deposit: 40 tokens.”
Maya opened her wallet. Her finger hovered over the confirmation button.
“Do it,” she whispered. “Do it, do it, do it.”
She pressed the button.
“Transaction submitted to blockchain. Confirmation pending…”
The spinning icon appeared. Maya watched it, barely breathing.
“Transaction confirmed. Collateral deposited: 40 tokens.”
“Okay, Eli’s turn. Come on, come on.”
“Waiting for Eli’s deposit…”
The seconds stretched into an eternity. Maya refreshed the screen. Still waiting.
“Eli’s deposit confirmed: 40 tokens. Total channel balance: 80 tokens.”
“YES!” Maya pumped her fist. “We did it!”
“Channel opened successfully. Initial state recorded. You may begin off-chain gameplay.”
Maya’s screen changed. A new interface appeared—the state channel dashboard. It showed the channel’s current status:
- Channel ID: GC-2026-04-15-MAYA-ELI
- Status: OPEN
- Current State: #0 (Initial)
- Total Moves Exchanged: 0
- Collateral: 80 tokens
- Last Update: Just now
“State #0,” Maya read aloud. “The initial state. Everything starts here.”
The game board loaded. Both fleets appeared in their starting positions. Everything looked normal, but Maya felt the weight of the moment. This wasn’t just another game. This was the future.
Eli: “I’m ready when you are. Let’s do this.”
Maya: “Wait. Before we start, let’s confirm how this works.”
Eli: “Okay, you go first.”
Maya: “Every move we make is a new state. We both have to sign each state. That proves we both agreed to it.”
Eli: “Right. And the latest signed state is the valid one.”
Maya: “Exactly. So if we both agree on the final state, we close the channel and settle.”
Eli: “Simple enough. Let’s play.”
Maya smiled. “Simple enough. Let’s play.”
Scene 2: The Game Begins
The match started like any other game of Galactic Conquest. The grid of stars appeared on Maya’s screen—a sprawling map of 144 sectors, each one a potential battlefield. Resource nodes shimmered in the distance. Planetary systems beckoned with the promise of strategic advantage.
But something was different. Something was profoundly, wonderfully different.
Maya executed her first move—a scouting action to identify the nearest resource nodes. The command processed instantly.
No delay.
No transaction confirmation.
No fee notification.
She blinked, waiting for the familiar ping that announced a fee deduction. It never came.
“Where’s the fee?” she whispered, almost disbelieving.
She checked her wallet balance. Still forty-three tokens. The initial deposit had been deducted, but that was it. No additional charges.
“Wait. Wait, wait, wait.” She scrolled through the transaction history. “One deposit transaction. That’s it. No fees for moves. No pending transactions. Nothing.”
She made another move. Then another. Then a complex series of maneuvers, sending her fleet in three different directions.
Still nothing. No fees. No delays. Just pure, unadulterated gameplay.
Maya laughed out loud. It was a giddy, unhinged laugh that echoed through her room. Pixel, her cat, shot her a look of utter disdain from his perch on the bed.
“This is amazing!” she shouted. “This is the best thing that’s ever happened to me!”
She executed a flanking maneuver that she’d been wanting to try for weeks but couldn’t justify because of the fees. The move required twenty separate commands over the course of thirty seconds. In a normal match, each command would have cost her 0.008 tokens. Twenty commands would have been 0.16 tokens.
In this match, it cost her exactly zero.
“ZERO TOKENS!” she screamed, drawing a muffled “Keep it down!” from her mother downstairs. She didn’t care. This was a revolutionary breakthrough.
Eli: “This is insane. I just made 45 moves in the last minute.”
Maya: “I know! I did 38! No fees at all!”
Eli: “Why doesn’t everyone use this? This should be the default.”
Maya: “I don’t know, but we’re going to tell everyone. This is the future.”
The game progressed rapidly. With no fees to worry about, Maya played more aggressively than ever before. She took risks that she would never have attempted in a fee-heavy match. She experimented with new strategies—risky resource grabs, daring flanking maneuvers, all-out assaults that could either win the game or lose it spectacularly.
She made mistakes. Lots of them. But unlike a normal match where mistakes cost tokens, here they cost nothing but time and pride.
And she learned from each one.
“Okay, that didn’t work,” she muttered after a failed ambush. “But now I know their defensive patterns. Next time, I’ll come from the other side.”
She adjusted her strategy, adapting to Eli’s tactics in real-time. The game became a conversation—a dialogue of attack and defense, each move responding to the last.
Eli: “You’re getting better at this.”
Maya: “No fees mean I can afford to experiment.”
Eli: “Same here. I’ve been trying some crazy stuff.”
Maya: “I noticed. That thing you did with the decoys was clever.”
Eli: “Thanks! I’ve always wanted to try it, but it takes like twenty moves to set up. Too expensive normally.”
Maya: “Not anymore!”
They continued playing, the states accumulating one after another. Maya glanced at the channel dashboard.
“States exchanged: 47. Current state: #47.”
“Forty-seven moves,” she marveled. “That would have cost me zero point three seven six tokens in fees. But here? Nothing.”
Eli: “How many moves are we at?”
Maya: “Forty-seven. You?”
Eli: “Same. We’re in sync.”
Maya: “That’s the magic of state channels. We both have the exact same state history. The signatures prove it.”
Eli: “This is so cool. I feel like we’re pioneers.”
Maya: “We kind of are. I don’t know anyone else using state channels for gaming.”
Eli: “We should document this. Make a guide or something.”
Maya: “Let’s finish this game first. Then we can be experts.”
The game continued. Maya’s strategy began to pay off. Her risky moves started yielding results. She captured two key resource nodes, then used the resources to upgrade her ships. Her fleet grew stronger while Eli’s struggled to keep up.
But Eli wasn’t giving up easily. He countered with a maneuver of his own—a stealth attack on Maya’s supply lines that caught her completely off guard.
“Nice one,” she admitted, scrambling to recover. “That was clever.”
Eli: “Thanks. I learned it from watching your last tournament match.”
Maya: “Really? I didn’t think anyone watched those.”
Eli: “Are you kidding? You’re a legend in the competitive scene. That move you made in the final—the one where you faked a retreat then double-flanked? Genius.”
Maya felt a warm glow of pride. “I appreciate that. But if you learned my moves, I’ll have to invent new ones.”
Eli: “That’s the fun of it, isn’t it? Always evolving.”
Maya: “Exactly.”
The game entered its mid-phase. Both players had established their territories. Both had substantial fleets. The outcome was still uncertain.
Maya checked the state count again.
“States exchanged: 327. Current state: #327.”
“Three hundred and twenty-seven moves,” she breathed. “That would have cost me…”
She did the math quickly. “Three hundred and twenty-seven times zero point zero zero eight… two point six one six tokens. Two point six tokens saved.”
Her eyes widened. “In one match. I saved two point six tokens in one match.”
She thought about the tournament. Fifty matches. If each match saved her two to three tokens in fees, she could save over a hundred tokens just by using state channels.
That changed everything.
Eli: “You’re thinking about the tournament, aren’t you?”
Maya: “How did you know?”
Eli: “Because I’m thinking about it too. If we can use state channels for tournament matches, we could actually afford to compete.”
Maya: “That’s exactly what I was thinking. This changes everything.”
Eli: “It really does.”
The game continued. Maya pressed her advantage, securing more territory, building more ships, expanding her influence. Eli fought back valiantly, but the gap was too wide.
Eli: “You’re crushing me. I can’t keep up with your resource generation.”
Maya: “It’s all about the early game. I sacrificed a few ships to capture those resource nodes, and it paid off.”
Eli: “I saw that. I thought you were making a mistake.”
Maya: “In a fee-heavy game, it would have been. Each sacrifice costs tokens. But here? It’s just strategy.”
Eli: “That’s going to change competitive play forever. People will take more risks. The game will be more dynamic.”
Maya: “More dynamic and more fun.”
Eli: “I can’t believe more people aren’t using this.”
Maya: “They will. Once they see the benefits, they’ll all switch.”
Eli: “We’ll be the pioneers. The ones who showed everyone the way.”
Maya: “I like the sound of that.”
Scene 3: The Final Move
The game had reached its climax. Maya’s fleet encircled Eli’s last stronghold, a heavily fortified planet in the northern sector. Eli’s forces were battered, depleted, and outnumbered.
But he wasn’t giving up. Maya could see his ships regrouping for one final desperate assault.
Eli: “I’m going to do something crazy.”
Maya: “That’s your right. I’m ready for it.”
Eli: “You sure about that? It might surprise you.”
Maya: “Try me.”
Eli’s fleet surged forward—not toward Maya’s ships, but toward the planet itself. It was a kamikaze run, sacrificing everything for a chance to destroy the planet and deny Maya the victory.
“Clever,” Maya admitted. “If he takes out the planet, I can’t claim the sector.”
But she’d anticipated something like this. Her ships had been positioned to intercept exactly this kind of desperate move.
“Now!” she commanded, and her fleet converged.
The battle was brief but intense. Laser fire crisscrossed the void. Explosions blossomed like flowers of light. Ships on both sides were destroyed in the chaos.
But when the dust settled, Maya’s fleet remained. Eli’s ships were gone.
“Maya has achieved Total Victory!”
Maya leaned back in her chair, grinning from ear to ear. She’d won. But more than that, she’d proven that state channels worked. The game had been fast, cheap, and just as competitive as any other match.
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 navigated to the channel closure interface. It was simple—select the final state, confirm the signatures, submit the transaction.
“This is it,” she murmured. “One final fee, and we’re done.”
She clicked the button.
“Channel close request submitted. Awaiting counterparty confirmation…”
She waited for Eli to confirm.
And waited.
And waited.
Eli: “Actually, hold on a second.”
Maya frowned. “What do you mean? It’s over.”
Eli: “I just… I need to check something. Give me a minute.”
Maya: “What’s wrong? We both agreed to the final state.”
Eli: “I know, but I think I might have made a mistake.”
Maya’s frown deepened. A mistake? What kind of mistake?
Maya: “Eli, what are you talking about? Just confirm the closure.”
Eli: “Just give me a minute, okay? I need to look at something.”
Maya watched as Eli’s avatar went idle. His connection to the channel was still active, but he wasn’t responding.
“Come on, Eli,” she muttered. “Just confirm it. Let’s finish this.”
She waited another minute.
Then two minutes.
Then five.
Eli: “I’m sorry, Maya. I have to go.”
Maya: “What? Go where? We haven’t closed the channel!”
Eli: “Something came up. I’ll be back later.”
Maya: “Eli, you can’t just leave the channel open! We need to finalize the state!”
But Eli was already gone. His avatar grayed out. His connection dropped.
Maya stared at the screen in disbelief. “What just happened?”
She checked the channel status. It was still open. The final state hadn’t been submitted. The tokens were still locked in the channel.
“Eli just… left. With the channel open. Why would he do that?”
She tried messaging him again.
Maya: “Eli? Are you there?”
No response.
Maya: “I can’t close the channel without your confirmation.”
Still nothing.
Maya: “We need to resolve this. Please respond.”
Silence.
Maya’s frustration began to curdle into something else. Something darker.
Something suspicious.
“Why would he leave the channel open?” she asked herself again. “He knows we need to close it to get our tokens back. The only reason to leave it open is if…”
Her voice trailed off as the realization hit her.
“The only reason to leave it open is if he’s planning something.”
Maya’s heart started racing. She opened the blockchain explorer and searched for her channel address.
What she found made her blood run cold.
A transaction had been submitted. A state had been posted to the blockchain.
But it wasn’t the final state. It wasn’t State #847, the one where she had won.
It was State #412.
A state from the middle of the game.
A state where Eli was winning.
“Oh no,” Maya breathed. “No, no, no, no, no.”
Eli had submitted an outdated state to the blockchain. A state that made it look like he had won.
He was trying to cheat her out of her victory.
And if Maya didn’t act fast, he might just get away with it.
Maya’s fingers flew across the keyboard, pulling up every piece of information she could find. The state submission timestamp showed that Eli had acted just seconds after disconnecting from the channel. He’d planned this. The whole “something came up” excuse was a lie.
“He knew exactly what he was doing,” Maya said, anger replacing her shock. “He was just waiting for me to be alone in the channel so he could submit this.”
She scrolled through the channel rules that she’d set up earlier. There was a section on dispute resolution that she’d barely glanced at.
“Dispute Resolution: In the event of a disagreement, either party may submit their version of the state to the blockchain. The blockchain will evaluate both submissions and determine the correct state based on timestamps and sequence numbers.”
“The blockchain will evaluate both submissions,” Maya read aloud. “That means I can submit my version too.”
She opened the channel closure interface again. This time, instead of a cooperative closure, there was an option for a “Dispute Submission.”
“Submit Dispute: If you believe the other party has submitted an incorrect state, you may submit your own version. The blockchain will compare both submissions and determine the correct outcome.”
Maya’s heart leaped. “I can fight this. I have the correct state. I have the signatures. I have everything.”
She quickly prepared her submission. State #847—the final state, the one that showed her victory. She attached the signatures, the timestamp, the complete history of moves.
“Come on, come on,” she urged, as the transaction processed. “Submit. Submit.”
“Dispute submission confirmed. Both states are now recorded on the blockchain. Entering dispute resolution phase.”
Maya exhaled, feeling some of the tension leave her shoulders. “Okay. I’ve submitted my state. Now the blockchain will decide.”
She watched the status update on her screen:
“Dispute Resolution: Active. Challenge Period: 23 hours, 47 minutes remaining.”
“Challenge period,” she murmured. “That’s the window where we can submit evidence. After that, the blockchain makes its final decision.”
She leaned back in her chair, staring at the countdown timer. Twenty-three hours and forty-seven minutes. That was how long she had to wait.
But she wasn’t going to wait. She was going to research. She was going to understand exactly what was happening and make sure she was prepared for whatever came next.
“Eli,” she said, her voice cold and hard, “you just made the biggest mistake of your gaming career.”
She opened a new browser window and began to research.
Scene 4: Understanding the Challenge
Maya dove into the research with renewed intensity. The initial excitement of discovering state channels had given way to something more urgent—a desperate need to understand the dispute resolution system.
“It’s like a courtroom,” she explained to Pixel, who had decided to grace her with his presence. “Both sides present their evidence, and the blockchain—the judge—decides who’s right.”
Pixel yawned.
“Fine, be that way. But this is important.”
She found an article titled “State Channel Disputes: A Comprehensive Guide” and devoured it.
The Challenge Period
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 serves several purposes:
- Time to respond: The other party has time to notice the submission and respond.
- Evidence collection: Both parties can gather and submit evidence supporting their position.
- Prevention of quick fraud: A fraudster cannot instantly steal funds—the challenge period provides a window for response.
The typical challenge period is 24 hours. During this time, either party may submit their version of the state.
“Twenty-four hours,” Maya repeated. “That’s how long I have to submit my evidence. I already did that, but I need to make sure everything is perfect.”
She continued reading.
What Makes a State Valid?
For a state to be valid, it must meet several criteria:
- Valid Signatures: Both parties must have signed the state with their private keys.
- Sequence Number: The state must have a higher sequence number than any previously submitted state.
- Timestamp: The state must be newer than any previously submitted state.
In a dispute, the blockchain compares the submitted states and selects the one with the highest sequence number and most recent timestamp.
Maya checked State #847 against these criteria.
- Valid Signatures: Yes, both she and Eli had signed it.
- Sequence Number: 847—higher than Eli’s State #412.
- Timestamp: 3:00 PM—later than Eli’s State #412 (12:00 PM).
“Perfect,” she said. “My state wins on every single criterion. There’s no way Eli can beat this.”
But there was more to the article.
Watchtowers: Your Safety Net
Even with challenge periods, there’s a risk that the correct party might be offline during the dispute. To address this, many users subscribe to “watchtower” services. Watchtowers monitor state channels and automatically submit correct states during disputes, protecting users even when they’re not paying attention.
“Watchtowers,” Maya repeated. “Third-party services that protect you when you’re offline.”
She looked at the countdown timer: 23 hours, 22 minutes remaining.
“I have time to set up a watchtower,” she decided. “If anything goes wrong, I want backup.”
She searched for available watchtower services and found several options. Most had small fees—a few tokens per month—but offered 24/7 monitoring and automatic dispute submission.
Maya selected one and signed up.
- Service: Sentinel Watchtower
- Fee: 2 tokens/month
- Features: 24/7 monitoring, automatic dispute submission, priority response
- Channels Monitored: 1 (currently)
“Two tokens a month,” she said. “That’s worth the peace of mind.”
She linked her channel to the watchtower, granting it permission to submit states on her behalf.
“Now, even if I’m asleep or offline, the watchtower will protect me.”
She watched the countdown timer continue its slow descent. Twenty-three hours and eighteen minutes left.
“I’ve done everything I can,” she said to Pixel. “Now I just wait.”
She leaned back in her chair, exhausted. The adrenaline that had carried her through the night was fading, replaced by a bone-deep weariness.
“I should sleep,” she admitted. “I can’t keep going like this. But…”
She looked at the timer again. Twenty-three hours. A full day of waiting.
“I’ll sleep for a few hours,” she decided. “Then I’ll check everything again. Make sure nothing’s changed.”
She set an alarm on her phone, then pushed herself away from the desk.
But before she could stand, a notification pinged.
“Watchtower Alert: Dispute intervention executed.”
Maya’s heart stopped. “What? Already?”
She opened the notification.
“Sentinel Watchtower has detected a fraudulent state submission (State #412) on Channel GC-2026-04-15-MAYA-ELI. Your correct state (State #847) has been submitted to the blockchain on your behalf.”
Maya blinked. “But I already submitted it. Why would the watchtower…”
She checked the timestamp. The watchtower had submitted her state just minutes after Eli’s fraudulent submission—minutes before she had submitted it herself.
“It was already doing its job,” she realized. “Before I even thought to check. The watchtower was watching. It saw Eli submit the outdated state and automatically submitted my correct state.”
A wave of gratitude washed over her. “If I had been asleep, I would have lost. But the watchtower had my back.”
She looked at the watchtower interface. It showed a log of the actions:
- 12:03 PM: Eli submits State #412
- 12:05 PM: Watchtower detects fraudulent submission
- 12:06 PM: Watchtower submits State #847
- 12:08 PM: Maya submits State #847 (duplicate)
“Two submissions,” Maya said. “Mine and the watchtower’s. Double protection.”
She smiled. “Eli, you’re not just fighting me anymore. You’re fighting an entire system designed to catch cheaters like you.”
She closed her laptop and crawled into bed. Sleep came quickly.
Maya woke to the sound of her alarm. She’d slept for six hours straight—a luxury she rarely allowed herself during tournament season. But today, she needed the rest.
She stumbled to her desk and opened her laptop. The countdown timer showed 17 hours remaining.
“Still plenty of time,” she said, rubbing her eyes.
She opened her messages, hoping to see something from Eli. Instead, she found a notification from the watchtower.
“Watchtower Update: Dispute resolution phase is ongoing. No new submissions detected. Your state (State #847) remains the most recent and highest-sequence state.”
“Good,” Maya said. “The blockchain is still considering my state.”
She opened the channel dashboard. Both states were displayed side by side:
| State #412 (Eli) | State #847 (Maya) | |
|---|---|---|
| Sequence | 412 | 847 ✓ |
| Timestamp | 12:00 PM | 3:00 PM ✓ |
| Signatures | Valid | Valid |
| Game Winner | Eli (claimed) | Maya (claimed) |
“The blockchain is going to pick my state,” Maya said confidently. “It’s clearly the correct one.”
She checked her watchtower settings. Everything was still active.
“I could just wait,” she mused. “Wait for the challenge period to end and the blockchain to decide.”
But she couldn’t help herself. She needed to understand more.
She opened the detailed explanation of the dispute resolution process.
How the Blockchain Decides
When multiple states are submitted, the blockchain evaluates them using these criteria:
- Validity: Are all signatures valid?
- Recency: Which state has the highest sequence number and latest timestamp?
- Consistency: Does the state follow the channel’s rules?
The blockchain does not evaluate the “fairness” of the game. It only evaluates the cryptographic validity of the states. This is deliberate—the blockchain is not a judge of gameplay, only a guarantor of cryptographic truth.
Maya nodded. “That’s fair. The blockchain doesn’t know who won. It only knows which state is the most recent and the most valid.”
She scrolled to the final section.
Penalty Mechanism
If a party submits an outdated state during a dispute, they may be subject to penalties. Typical penalties include:
- Loss of Collateral: The cheating party may forfeit part or all of their collateral.
- Penalty Fee: Additional fees may be deducted from the cheating party’s wallet.
- Reputation Damage: The cheat is recorded on the blockchain, where it cannot be hidden.
Penalties serve as a deterrent, making cheating economically irrational.
“Eli’s going to lose his collateral,” Maya realized. “And maybe more than that.”
She thought about what this meant. Eli had deposited 40 tokens into the channel. If the penalty was 50%—a common amount—he’d lose 20 tokens. She’d gain them.
“That’s justice,” she said. “If you cheat, you pay. Simple as that.”
She checked the countdown timer again. Fifteen hours remaining.
“Might as well make myself useful,” she decided. “Let me document everything. This is going to be a great story to tell.”
She opened a document and started writing: “How I Won a Blockchain Dispute and Taught a Cheater a Lesson.”
The hours passed slowly. Maya checked the status periodically, but nothing changed. The blockchain was still in the dispute resolution phase. Neither party submitted anything new.
At hour 23, Maya started paying close attention.
“Almost there,” she said. “Just one more hour.”
She watched the countdown timer tick down.
59 minutes.
45 minutes.
30 minutes.
15 minutes.
5 minutes.
1 minute.
0 minutes.
“Challenge period expired. Evaluating submitted states…”
Maya held her breath.
“Evaluation complete. State #847 selected as valid state.”
“YES!” Maya jumped out of her chair. “I WON!”
“State #847 accepted as final state. Applying channel closure…”
Maya watched as the blockchain processed the settlement.
“Channel closure complete. Funds distribution:”
- Maya: 60 tokens (40 deposit + 20 penalty from Eli)
- Eli: 20 tokens (40 deposit – 20 penalty)
“Penalty applied: Eli submitted outdated state. Penalty: 50% of deposit.”
Maya grinned. “Sixty tokens. I made a profit while winning a game and teaching a cheater a lesson.”
She opened her chat window and typed a message to Eli.
Maya: “Hey. You awake now?”
She waited. A few minutes later, his avatar appeared.
Eli: “I’m here. Look, I’m sorry about what I did. I don’t know what I was thinking.”
Maya: “You were thinking you could cheat and get away with it.”
Eli: “I know. And I was wrong. The system caught me. I lost my deposit. My reputation is ruined. I’m a fool.”
Maya: “Yeah, you are. But I accept your apology.”
Eli: “Really? You’re not mad?”
Maya: “Oh, I’m mad. But I’m also relieved. The system worked. Justice was served.”
Eli: “I learned my lesson. No more cheating. I promise.”
Maya: “Good. Now, want to play another match? Fair and square this time?”
Eli: “You’d trust me again?”
Maya: “I trust the system. It’ll catch you if you try anything.”
Eli: “Fair enough. I’m in. And this time, I’ll play fair.”
Maya: “I’ll hold you to that.”
Maya smiled and opened a new channel.
Table of contents:
Introduction
Chapter 1: The High-Fee Network
Chapter 2: A State Channel Solution
Chapter 3: The Off-Chain Agreement <<<<<< NEXT
Chapter 4: The Dispute Resolution
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
