Refactor strategy to work in terms of future

Open kanej opened this issue 2 years ago • 2 comments

Analyze execution strategy to see if we can swap future for exState in the strategy interface. This will significantly reduce our exposed public api surface area.

Sep 11 '23 10:09 kanej

Digging into this, I am not sure we can just use futures instead of exStates. Execution states have been resolved down to base values, we would be moving the resolution onto the execution strategy if we inject future.

Futures don't currently have an artifactId either.

Sep 11 '23 11:09 kanej

We are moving this to the beta follow on. We will tackle it with the create2 work.

Sep 13 '23 09:09 kanej