To further the preparation just in case the BTC makes an extended nosedive, which would create pressure on the sell side, I prepared a transaction that deposits funds to these gateways (I dare say we can't rely on ALPv2 at the moment):
The amounts for @Cybnate's gateways is considerably lower, because she limited here gateway operations to 15k
and already has 10k there
In total 65,000 NBT to gateways as listed above
Signed 1 of 3/5
@dysconnect, @ttutdxh, @jooize, @woodstockmerkle, please give this transaction only a second signature for now!
The intention is to get it signed and broadcast as fast as possible, once the need is detected.
This is why it's already created and should couch with 2 signatures for the BTC price drop.
Then only a third signature is required to get the funds sent to the gateways.
Ideally someone knowing the he/she will be available on short notice in the next days should withhold from signing it, whereas a less available (I wouldn't want to wait for 36 hours after a need is recognized; with "less available" I mean more than a few hours!) person should sign it as second signer.
I intentionally signed it already, although I should be highly available. As the deposit brings funds to my gateway, which already has some BTC and might receive 20,000 NBT soon, I don't want be the one in charge of depositing additonal funds to it.
We all know about the risks that go along with that.
On the other hand we might be in a quite bad position if not for the gateways. They are all that is supporting the peg at the moment. Taking this risk might pay out.