In Day 7 of my 10 Days of Blockchain series, I focus on a super real problem in decentralized apps: non-participation. In a normal client/server world, if someone stops responding you throw an error and move on. But in a smart contract, if one player disappears at the wrong time, funds can get locked in the contract forever. So I walk through what happens in our Rock, Paper, Scissors dApp if Alice pays a wager and Bob never accepts—or if Bob pays and Alice never reveals her hand. To fix it, I add Reach timeouts and wire them all the way through the participant interfaces so the front end can react when a timeout occurs. Alice publishes a shared “deadline” value, and then I add timeout handlers that close the contract and transfer funds to the appropriate party (plus call an `informTimeout` callback for both players). I also explain why we don’t “refund both sides” in certain cases—because it would let someone strategically time out to avoid a loss once information is revealed. Finally, I manually test by making Bob randomly “take his sweet time,” hit a deprecation warning about bare time values, and fix it by wrapping the deadline with `relativeTime`.