Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
There are a few activities ongoing that require the development of so called light client protocols for Cardano. The ones that came to my awareness are:
There are various ways how to implement light clients on Cardano (whereas because of the core protocol not providing so called state proofs out of the box, there is no canonical light client design available for Cardano at the moment). In that sense, I wanted to create a common point of reference and problem description with this CPS to which concrete light client designs can refer to when they are documented as a CIP.
At least for the IBC implementation we plan to document the Mithril based light client as a CIP and the same would make sense for the respective light client protocol to be developed for a Bitcoin-Cardano bridge (in case the bridge follows a light client based security model), because both designs can be used for other use cases as well.
Any feedback is highly appreciated.
Kind regards