Testing oSnap

Voting ended almost 3 years agoSucceeded

Author(s): Britt Status: Proposed Related Discussions: n/a

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.

Off-Chain Vote

For

7.07M ACX97.9%

Against

144.82K ACX2%

Abstain

3.77K ACX0.1%

Quorum:120%

Download mobile app to vote

Timeline

Apr 17, 2023Proposal created

Apr 17, 2023Proposal vote started

Apr 24, 2023Proposal vote ended

Apr 11, 2025Proposal updated

Author(s): Britt Status: Proposed Related Discussions: n/a

Summary:

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.