Open djmbritt opened 1 year ago
As the Guardians we want new DAO cycles to start transparently and semi-automated.
At the moment starting a new cycle requires the following steps:
cycle
entry in daoproposals
with the correct date and budget.processcycle
: this tallies the votes for the cycleupdatecycle
: this increments the DAO's current active cycleexecuteprop
(which is a High Guard action)These steps take time and are complicated to execute, which makes operating the DAO harder that needs to be (which is why Jesse has to do it each time).
I think that steps 2, 3, 4, and 5 can all be automated in a single transaction.
Step 6 can later be performed on the High Guard dashboard.
This can be stored on the blockchain where you have a list of accounts and a % of the left over funds to receive:
{"feepool.efx": 0.3, "treasury.efx": 0.7}
Just like the pancake swap fee calculator, create a CI pipeline to create a transaction to be signed by guardians to instantiate the new cycle.
This should be some kind of server that can run on a cron job so that it can run publish a new cycle when the old one finishes.
This needs to be some kind of node server that can use the eosjs library so that we can create the transactions and publish them. Afterward, a notification can be sent to discord, where the high guards can then sign the transaction to initiate the next cycle.
@jeisses Needs to be consulted to see what the steps are, what the eosio actions are that need to be called. We probably also have to expand the eosio account that is used with more permissions from the high guards, so they have the proper permissions to execute the needed actions.