Post-Bizzy Launch Debrief The core issue began with a single point of failure: a sudden surge in chain activity. At the moment of launch, Base network request volume spiked from 70,000 to over 500,000, placing significant load on the chain. This led to syncing delays across downstream infrastructure, affecting RPC providers which affected us. As a result, several issues emerged across the ecosystem. Here’s what happened, and how we’re addressing each one: 1. Mamo Liquidity Pool Delay (Virtuals’ Side) Mamo’s liquidity pool was delayed by one hour due to congestion during deployment. This created an arbitrage window that distorted the intended launch market. Solution: To recognize early participation and show good faith, all Mamo trades within the first 24 hours of launch will receive boosted Genesis Points. 2. Bizzy Token Claim Delay The claim process for Bizzy was delayed due to congestion. Solution: We’re implementing solutions recommended by the @base team, including manually submitting transactions to the mainnet sequencer. To recognize early participation, all Bizzy trades within the first 24 hours of launch will receive boosted Genesis Points. 3. Pledging Display Issue Some users who pledged points during the Bizzy Genesis launch saw missing or incorrect pledge point displays due to congestion. In some cases, this led to unintended point overcommitment. Solution: Because this directly affected how Virgen’s pledges were handled, we will refund affected Virgens at 1.2x the overcommitted points as a gesture of trust and acknowledgment. 4. Point Distribution Delay Daily point distributions were delayed due to the same syncing issues affecting other high-frequency operations. Solution: Points will appear once infrastructure fully catches up. No action is required from Virgens. Thank you for your patience. We remain committed to protecting the integrity of Genesis, honoring the trust of Virgens, and continuing to build with fairness at the core. Special thanks to the @base team for working directly with us to resolve these infrastructure-level challenges.