Back to collectionA Party in Los Angeles, a Security Reckoning Elsewhere
Background: The studio and The Tiger Archives were holding a Los Angeles party during NFT LA, an evening for people who knew one another online to talk about games face to face. Today: The party went ahead, with beer, tacos and beer pong drawing people away from their screens for a while. Impact and next steps: The narrator often thought back to the layout of that day: first the gathering, then the accounting of risk, both crowded into a single date.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
Background: The studio and The Tiger Archives were holding a Los Angeles party during NFT LA, an evening for people who knew one another online to talk about games face to face. Meanwhile, the wallets, contracts and cross-chain bridges used in blockchain gaming made asset security a concern for everyone. The team did not yet know that news would rewrite the evening's agenda.
Today: The party went ahead, with beer, tacos and beer pong drawing people away from their screens for a while. Then came news from elsewhere: USD 620 million had been stolen from Axie's Ronin cross-chain bridge, and the attack had gone undetected for six days. A bridge had been compromised for six days without anyone noticing. Security in blockchain gaming suddenly became an industry-wide focus. The studio spent the night reviewing its own contracts and multisignature permissions, still turning over the access list after the party ended. In the group, the Night Watchman said, “In blockchain games, the wallet is the real health bar.”
Impact and next steps: The narrator often thought back to the layout of that day: first the gathering, then the accounting of risk, both crowded into a single date. The party showed that people wanted to meet beyond the group chat; the Ronin news forced the team to turn back to where assets entered its systems and who could sign for them. The overnight review had no conclusion yet. Next, the team had to work out which permissions to narrow and which assets to isolate, so the excitement would have something dependable beneath it.