Synopsis#

Update Nance interface and API to relieve burden of multisig ops queuing from filipv.

Motivation#

No one should be doing this burdensome administrative work. Its time consuming and not fun.

Payment will be use to support development time from twodam, jigglyjams, and filipv.

Specification#

Nance features needed to alleviate multisig ops:

1. Milestone based actions
   • update frontend actions to allow for a checkbox to mark a proposal as milestone based
   • update frontend to allow for any DAO member to click a button that will trigger a Discord poll asking the DAO if the milestone has been met
   • update backend to support the status of actions that have been approved (most likely a new table)
   • update backend to check for milestone based polls and tally the results
   • update backend to move status of action upon completion of poll
   • update backend to add timeout for triggering of poll so a DAO member can only trigger a poll once per cycle
2. Action to occur at future governance cycle
   • update frontend actions to allow for proposer to add a specific governance cycle number on when the action should occur
   • update backend to accept an action with a governance cycle start that is different than current governance cycle
3. Multi governance cycle transfer action
   • required for https://nance.app/s/juicebox/488 support
   • update frontend to include a governance cycle start and count for Transfer actions
4. Send transaction thread describing relevant proposals
   • update backend to compile current governance cycle transactions (currently in a script state, needs to be functionized)
   • update backend to send reconfiguration to Tenderly for simulation (currently in broken state)
   • write backend tests for Tenderly transaction sending
   • update backend transaction message to show all relevant proposals
   • update backend transaction message to show the difference in funding distribution limit
5. Queue transactions from nance.app with gas reimbursement enabled
   • to eliminate subsequent reimbursement transactions, this is a never ending cycle unless we reimburse gas from safe
   • add gas amount parameter to safe transaction when queuing from nance.app (see https://docs.onchainden.com/pay-gas-from-safe/overview)
   • write backend test for proper accumulation of distribution limit and payouts
   • write shared function to calculate distribution limit and payout allocations
6. Decide upon reimbursement plan for off-chain subscriptions (Notion, Gmail, Figma)
   • explore options on how to implement the lowest administrative methods of reimbursements of offchain expenditures
   • define a plan on how to implement above decision
   • create Reimbursement action
   • update frontend to support Reimbursement action
   • define reimbursement process so all DAO members know how to act upon a reimbursement

Timeline#

Pay initial deposit of $10,000 to @nance project to secure developer time. Pay subsequent $10,000 to @nance upon completion of above.

--- nance-actions
- type: Payout
  uuid: 5a0d12e98a384317b839cae4266e9540
  payload:
    type: project
    count: "1"
    amountUSD: "10000"
    project: 477
    address: "0xAF28bcB48C40dBC86f52D459A6562F658fc94B1e"