Back to collectionA New Constraint on the Board: Confirmation Breaks the Game’s Rhythm
Background: After deciding to keep battle resolution off-chain, the team began listing the ways blockchain could still get in the way of play. Today: The whiteboard gained a “Problems with the chain” column. Impact and next: The earlier compromise had mainly answered what would stay off-chain.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
Background: After deciding to keep battle resolution off-chain, the team began listing the ways blockchain could still get in the way of play. The problem column on the whiteboard was not just a technical checklist; it was meant to help engineering and design decide which waits players could tolerate and which would interrupt a match.
Today: The whiteboard gained a “Problems with the chain” column. Its first entry read: confirmation is too slow and breaks the game’s rhythm. That phrased abstract on-chain latency as a pause players would actually feel. It also reminded the team that even with only key assets on-chain, they still had to connect confirmation timing to the flow of a match.
Impact and next: The earlier compromise had mainly answered what would stay off-chain. Today brought a new question forward: how could the remaining on-chain steps avoid slowing the experience? The team next needed to identify which actions must wait for confirmation and which feedback could be shown sooner; no specific solution had been settled.