sdk: design the layers above the state machine.

[shanzzam]

Create a draft doc for the layers above the state machine.
These include components previously discussed:
Transport
Payments, Withdraw, Add funds
Tx information

[leighmcculloch]

When we say design the layers above the state machine, this is what I'm currently thinking, and is approximately what I think we discussed on Thursday.

We're currently working on the two boxes in the bottom left. The state box is responsible for maintaining the state of the channel itself, protecting the channel so it is always in a valid state, and preventing the participant from signing a transaction they shouldn't.

The other things need figuring out and we probably have things we can learn from #44 and #45.

I think what is most unclear is what that big wide box is that makes up the future surface layer of the API, and if that should be an SDK API, or should be a service API.

Diagram source

[nikhilsaraf]

Yes, I agree. I think that's something we should take inspiration from the research of other L2 SDKs while combining that with what we think will be an intuitive interface for Stellar.

[leighmcculloch]

While working on #122, which is ongoing, it is becoming more evident that an orchestrator will take a load off an application implementing and I want to experiment more with this idea. I plan to pickup this issue next week, take the design doc linked above and iterate on that design in code inside the example application I am working on. I've self-assigned the task to myself for this work.