Dear EthStorage V1 Ceremony Participants, Thank you for being part of our trusted setup ceremony! We’re deeply grateful for the incredible participation from the community — with more than 2,000 contributors, the response has far exceeded our expectations. Your enthusiasm and support mean so much to us. With so many people joining, the queue has occasionally become stuck. This can cause participants to lose visibility of their position or encounter FirebaseErrors. We understand how frustrating this can be, and we’re in constant communication with the PSE team @PrivacyEthereum (a research and development lab delivering privacy to the Ethereum ecosystem) to resolve these issues. Please know that we’re here to support you every step of the way. To make things easier, we’ve gathered the most common questions and put together the following unified guidance: 1 Unable to see your queue position If your terminal does not display your current position in the waiting queue (as shown in the following screenshot), this does not mean your contribution is stuck. Please remain patient — The CLI will automatically begin your contribution when it’s your turn.

2 FirebaseError issue If you encounter a FirebaseError like the one shown below, try the following recovery steps: phase2cli clean phase2cli logout phase2cli auth phase2cli contribute -c ethstorage-v1-trusted-setup-ceremony If the problem persists, DM @es_kp in discord channel with the following: Your GitHub username Your email address A screenshot of the error message. ⚠️ Please note: messages sent in the public channel will be ignored. Once we receive your information, we will escalate the issue to the PSE team, who can manually update your status if needed.

3 High Demand, Limited Capacity for Manual Handling We’ve already forwarded part of the contributor list to the PSE team for manual processing. However, due to the high volume of DM requests and the manual nature of these interventions, we cannot guarantee that every individual case will be addressed in time. We appreciate your understanding and patience as the team works through the list.

4 Contribution Window Closing for Late Queue Positions If your current position in the queue is around or above 800, it is unlikely—though not impossible—that you will be able to contribute before the ceremony ends on August 22nd. ⚠️ Please note: 800 is an estimate, not a hard cutoff. Even if your position is below 800, there is no guarantee that your contribution will be processed in time, depending on the ceremony's progress and other participants’ activity. In light of this uncertainty, we do not recommend waiting if your position is significantly high and you’re not prepared for extended delays.

5 Contribution Timeout If you see the following message (see pic below) This means your contribution process timed out because some steps took longer than expected. When this happens: - You are automatically removed as the active contributor. - You must wait for the predefined timeout period to expire before rejoining. - After the timeout, you can restart from the same circuit. To reduce the chance of repeated timeouts, we recommend using a machine with a faster and more stable internet connection before trying again.