Onboarding process on the technical front
- Keep team completes user acceptance tests
- Keep team deploys the upgrade
- Keep team asks TC to execute the first batch of transactions (stitching the veto mechanism with existing contracts)
- Keep team asks TC to execute the second batch that will enable the mechanism with initial guardians set
- Guardians clear out stalled redemptions
- Keep team releases the new client with RFC 12 and disables the wallet coordinator contract
- New guardians are added by Token Holder DAO (not TC!) → [I'd also recommend to add 1-2 additional guardians to the initial set (if possible) because this is the only opportunity for TC to do so. After the mechanism is enabled, only the Token Holder DAO can add guardians and this is a much slower process]
Guardians Addresses and Details
NotJustLaw:
- Telegram: @NotJustLaw
- ETH address:
- Guardian Address - 0xc6776e23F25cd56791D9D136648862D994770680
- Payment Address - 0x01192f3dcc34fbc4a6d2d223bd1e6416BdD9C024
- Timezone: UTC
James: