We should adopt a high-level spec organization, well-indexed with room for what is left for future specification.
Specs should laid out well an onchain version and an offchain one, with re-usability between both variances.
While working on the hackhaton this we, I think some complexity of basic messages may be moved to an invoice/offers style of the spec.. Maybe we can reuse LN-standard here with new fields.
Also base key negotiation may be build from LN open_channel/accept_channel, considering these ones as "session establishement" messages.
Anyway, I propose to work on a high-level review of topics to be addressed, make a call with @nkohen to get a reasonable proposal and then submit this during a future meeting.
We should adopt a high-level spec organization, well-indexed with room for what is left for future specification.
Specs should laid out well an onchain version and an offchain one, with re-usability between both variances.
While working on the hackhaton this we, I think some complexity of basic messages may be moved to an invoice/offers style of the spec.. Maybe we can reuse LN-standard here with new fields.
Also base key negotiation may be build from LN
open_channel/accept_channel
, considering these ones as "session establishement" messages.Anyway, I propose to work on a high-level review of topics to be addressed, make a call with @nkohen to get a reasonable proposal and then submit this during a future meeting.