oSnap test round 2

Author(s): Britt Status: Proposed Related Discussions: This snapshot proposal

Note:

The previous oSnap test was unsuccessful and required us to redeploy the oSnap module. This occurred because the proposed transaction was accidentally constructed to send a fake ACX token rather than the real one. This was not caught until the liveness window for the execution of the transaction began. In order to prevent interacting with a potentially malicious token, the module was unplugged and redeployed. While this isn't the outcome we hoped for on the first test, it is a valuable opportunity to learn and improve. Updates to the Snapshot interface are underway now to filter out unverified tokens, which should prevent this type of mistake in the future.

Summary:

This proposal is meant to test the oSnap implementation we've just deployed. If this vote passes, we will use oSnap to have the treasury send 1 ACX to me. In anticipation of this, I have sent 1 ACX to the treasury. You can see that transaction here

Motivation:

This proposal is being done as an end-to-end test to make sure that our deployment of oSnap is functioning properly and reporting to all of the expected platforms.

Specification & Implementation:

Here are a few things you can expect to see as this proposal occurs:

Voting period

• After posting on snapshot, there will be a notification in the Across Discord that should tag all members with the "voter" role.
• This event also notifies in the Risk Labs internal chat.
• Typically a Tweet would also go out, but this is still a manual process, so it's not something we're testing for here.
• After 7 days, the vote will close on Snapshot.

Execution Steps

• If the vote has met quorum (6M), oSnap will enable an execution button on Snapshot. If the vote has not met quorum, this button will be disabled.
• Assuming that the vote meets quorum, a Risk Labs engineer will post a bond and propose the execution of this proposal.
• Proposing the execution transaction will appear in the UMA oracle
• Proposing the execution transaction will send a notification to the UMA Discord
• Proposing the execution transaction will send a notification in the Across Discord to the same channel as the Snapshot notifications mentioned above.
• Proposing the execution of this will send a notification to the Risk Labs internal chat and trigger pager duty.

Dispute Steps

• If the proposal was not valid (met quorum but did not pass), it should be disputed. There is a 5 day liveness period for this, but we expect to see disputes within 12-24 hours.
• A dispute triggers a notification in all of the locations above. It will then continue on through the UMA DVM, which includes a series of notifications that go out to all $UMA tokenholders.

Voting:

A "YES" vote results in the treasury sending 1 ACX to my address: 0x33DB27C21E0f7a2f3351A4C6DDceDFB9F713410b

A "NO" vote means that the treasury should not send any ACX as a result of this proposal.

Note: Before voting, please confirm that the proposed transaction matches with the description above. This vote is eligible for oSnap execution.