Back to collectionPeak Load Pushes Card Confirmations into Minutes
Background: The two candidate chains for card NFTs had entered stress testing, and A-Zhen was responsible for judging whether either technical approach would still suit players during real peaks. Today: A-Zhen stress-tested the candidate chains and found that confirmations during peak periods took minutes. Impact and next steps: Until now, the two candidates had mainly been compared as proposals; the test brought a peak-delay risk that had to be addressed.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
Background: The two candidate chains for card NFTs had entered stress testing, and A-Zhen was responsible for judging whether either technical approach would still suit players during real peaks. Before choosing, the team needed to understand the scale of the wait; a smooth demo in ordinary conditions might not predict a crowded experience.
Today: A-Zhen stress-tested the candidate chains and found that confirmations during peak periods took minutes. She was troubled by the result: if a card action made players wait several minutes, technical feasibility could itself become an obstacle to play. The test exposed a confirmation problem under congestion, not a final chain decision.
Impact and next steps: Until now, the two candidates had mainly been compared as proposals; the test brought a peak-delay risk that had to be addressed. A-Zhen planned to record the time spent at each step and discuss with the team whether they could reduce player waits or change which actions needed to go on-chain. The final choice remained open pending further checks.