The current work-flow is as follows:
- Admin adds a JSON of allowed calls for a specific strategist by uploading it via the merkle-proof-manager form
- This JSON includes ALL calls that a strategist can use to form automations
Expected Behaviour
- ALL created presets are stored in some JSON file on IPFS
- UI loads ALL presets of ALL strategists ALWAYS
- UI allows to simulate ALL presets
- UI ONLY allows to execute a preset if connected wallet is strategist
- UI ONLY allows to adapt a preset if connected wallet is hub admin
- The same preset can belong to multiple strategists IF their merkle proof JSON allows to execute all calls
- A preset can ALWAYS be saved, even if simulation fails
- A stratgist can ALWAYS ONLY choose calls that are part if its merkle tree
Open Questions/Problems
- Anchoring presets in pool metdata need pool admin, making adapting presets really hard → for now I would accept IF only the pool admin can adapt presets BUT that makes it harder for the UI as theoretically a pool can have multiple strategists with a different set of allowed calls.
User Stories
Story 1
As a strategist I want to create a new preset by choosing cocatenating multiple contract calls together, so that I can automate workflows.
Story 2
As any connected wallet I want to be able to simulate presets of other strategist, so that I can verify they are working correctly and see the simulation results.
Story 3
As a strategist I want to be able to store presets so that I can re-execute them later.
The current work-flow is as follows:
Expected Behaviour
Open Questions/Problems
User Stories
Story 1
As a strategist I want to create a new preset by choosing cocatenating multiple contract calls together, so that I can automate workflows.
Story 2
As any connected wallet I want to be able to simulate presets of other strategist, so that I can verify they are working correctly and see the simulation results.
Story 3
As a strategist I want to be able to store presets so that I can re-execute them later.