Update Across DAO Osnap parameters

Author(s): Britt **Related Discussions:**N/A

Summary:

Across has been using Osnap successfully for a while now, and we'd like to update our parameters to allow for automatic proposal/execution by UMA's Osnap bot.

Motivation:

Our current Osnap parameters include a 5-day liveness and a 10WETH bond. These early parameters allowed us to introduce Osnap to Across and test our ability to monitor the use of a new tool. After several months of use, the current liveness period and bond are starting to feel excessive and prohibitive to the progress of genuine proposals. If we adjust our parameters to comply with the rigid requirements of UMA's Osnap bot, our proposals will automatically be proposed and executed with Osnap after they pass on Snapshot, reducing the amount of human involvement required to move things along.

Specification & Implementation:

Making these updates will require a batch transaction that includes one transaction to update the bond from 10WETH to 2WETH, and one transaction to lower the liveness from 5 days to 3 days.

The first transaction will be a contract interaction with our deployed Osnap module that calls the setCollateralAndBond function. The collateral address should still be WETH, and the bond amount should be 2 WETH, which is 2000000000000000000 in unit256.

The second transaction will be a contract interaction with our deployed Osnap module that calls the setLiveness function. This is designated in seconds and should be 172,800 to give us a liveness of 3 days.

Rationale:

We chose the parameters above for the following reasons:

1.) the Osnap bot significantly improves the UX of using Osnap for on-chain execution of off-chain voting. Complying with the parameter requirements of the bot means setting the bond to 2 WETH, which we feel is an adequate deterrent for spam proposals.

2.) The liveness period of 3 days was selected because we feel confident that our monitoring setup will provide more than enough time for us to take action in the event of any malicious proposal. Additionally, it was always the intention to reduce down from 5 days once we felt prepared to do so. Note, this does not actually change the voting period of our Snapshot space - it reduces the liveness period for dispute opportunity of the Osnap transaction. Osnap transactions only get proposed after passing on Snapshot.

Voting:

A "Yes" vote will result in Osnap execution of the updated parameters to Osnap, as listed above. This includes lowering the Osnap bond from 10WETH to 2WETH and the Osnap liveness window from 5 days to 3 days.

A "No" vote will mean that our Osnap parameters do not change at all as a result of this vote.