All Wednesdays are now Tuesdays

Author: LexaMichaelides

.DS_Store

@@ -10,7 +10,8 @@ The ICS testnet is **public**, meaning that anyone can join, run a validator, an
 ## Quick links
 * Join the ICS testnet by following the instructions [here](VALIDATOR_JOINING_GUIDE.md)
 * Register using the Google form [here](https://docs.google.com/forms/d/e/1FAIpQLSeXlXu89uyAgsfck0wpjtUVqaXWRzyJQwLMM-9dlJk9WIH3Zg/viewform)
-* Stay tuned for Testnet Wednesday events by following our schedule [here](SCHEDULE.md) (and in Discord)
+  * Resubmit this form if either your `provider` or `cosmoshub-4` keys change
+* Stay tuned for Testnet Tuesday events by following our schedule [here](SCHEDULE.md) (and in Discord)
 * Track validator participation using the Google sheet [here](https://docs.google.com/spreadsheets/d/1CR-gtLgHUXvP2Ww8KFqnOej7ma_GwDjNt8IhdTXbGGw/edit?gid=1605434271#gid=1605434271)
 
 
@@ -31,7 +32,8 @@ We accept two ways of proving this:
 ## What are the criteria for getting paid?
 Each period, we evaluate the following three criteria:
 * **Criteria 1:** Be an active mainnet validator. Submit proof via our Google form
-* **Criteria 2:** Validate all available Top N consumer chains secured by the Cosmos Hub (Neutron and Stride) with *assigned consumer keys* (i.e., do not reuse your Hub key).
+* **Criteria 2.1:** Validate all available Top N consumer chains secured by the Cosmos Hub (Neutron and Stride) with > 50% uptime.
+* **Criteria 2.2:** Use *assigned consumer keys* for all available Top N consumer chains (i.e., do not reuse your Hub key).
 * **Criteria 3:** Run a testnet infrastructure setup that closely mimics mainnet. 
 
 If you meet these three criteria (most testnet validators do), you can participate in testnet events and earn points. At the end of each period, we'll translate those points into USDC and pay you for your testnet work! There are even bonus points for completing all events perfectly and remaining unjailed.

interchain-security/Testnet_Incentives_Program.md

@@ -0,0 +1,11 @@
+# :ribbon: Testnet Tuesdays (formerly Testnet Wednesdays) :ribbon:
+
+With the successful launch of Neutron on Cosmos Hub, we’ve learned a lot about administering the Hub’s testnet infrastructure, as well as what it means to rally 80+ validators together for many coordinated upgrades and new consumer chain launches. Together we’ve laughed, we’ve learned, and we’ve banged our heads on our desks after seeing the 17th AppHash error in a row.
+
+Currently, testnet rehearsals for launches and upgrades are scheduled on an as-needed basis, with one or two rehearsals a week. Consumer chains represent a growth in complexity for not only The Hub, but also for the Testnets Program. Coupled with the regular cadence of coordinated Gaia upgrades, it’s clear that as more consumer chains onboard onto The Hub, the demand on the Testnets Program will also grow. 
+
+**All coordinated upgrade and launch activities will now take place on the `provider` testnet at ~14:00 UTC each week**. Some weeks, there might not be anything – we’ll let validators know by Monday if the agenda is empty, therefore no rehearsal is needed. In other weeks, there may be a `provider` chain upgrade and a new chain launch at the same time. We’ll do our best to space things out so that there aren’t more than two events in a single day. As we continue doing launches and upgrades together, we’ll hopefully get better and faster each week.
+
+Emergency release tests for the Hub and for consumer chain teams will still be scheduled, as needed, outside of the normal rehearsal cadence. This will only be invoked in the event of critical security patches that represent a major risk to the Hub.
+
+For chain development teams, this means that we’ll be working more closely with you to make sure that your release cycles line up with testnet rehearsal days. If a binary is not ready with enough lead time to build confidence, the rehearsal will be pushed to the following week. Committing to a public timeline for release and testing should also create more predictability for validators who want to run their own tests ahead of time.