DA0-DA0
Allow executing messages in proposal one at a time.
Might be corner cases here to consider, but it would be nice to be able to execute a proposal in multiple transactions. This would allow more complex proposals that otherwise would have gas issues.
Suggested by @ben2x4 re: updating many rewards contracts at once.
What should this look like an Option<u64> on the message for an optional index? And then if so how should we store already executed messages? Store two vecs, one for the ones not executed and the other for ones that have been? Then on execute we move them over?
at first brush I would think a wrapper type around msg which can indicate whether its been executed or not, and execute_execute could take in message index or identifier(s) which would allow specifying which message(s) to execute
Store two vecs, one for the ones not executed and the other for ones that have been
I really like this design. Given that you don't even need the optional index. Executing a single message can just pop from the unexecuted list and push to the executed one.