Docs improvements #3368
Docs improvements #3368
Conversation
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
nnsW3
requested review from
petermetz,
takeutak,
izuru0,
jagpreetsinghsasan,
VRamakrishna,
sandeepnRES and
outSH
as code owners
| @@ -11,7 +11,7 @@ | |||
| ## Introduction | |||
| Recent years have witnessed a growing demand for enabling interoperability across independent blockchains. Cross-chain asset exchange is a significant step towards blockchain interoperability. For public blockchains, the most popular application for asset exchange is cryptocurrency exchange. For permissioned blockchains, cross-chain asset exchange can be useful in [Delivery Versus Payment (DvP)](https://www.mas.gov.sg/-/media/MAS/ProjectUbin/Project-Ubin-DvP-on-Distributed-Ledger-Technologies.pdf) and [cross-border payment](https://www.mas.gov.sg/-/media/Jasper-Ubin-Design-Paper.pdf) scenarios. There exist various protocols designed for asset exchange on public blockchains. However, a widely adopted standard for designing such protocols for permissioned blockchains still does not exist. Moreover, most existing protocols are designed for public blockchains and their suitability to be applied to permissioned blockchains is unclear. | |||
|
|
|||
| In this article, we aim to lay out a set of requirements for designing cross-chain asset exchange protocols between permissioned blockchains. First we present a canonical motivating use case and then list the various patterns that such cases will follow in real-life scenarios. We then present a short survey of existing cross-chain exchange protocols for public blockchains, following which we summarise the building blocks, core mechanisms and security properties commonly involved in the protocol designs. We then analyse the requirements imposed by permissioned blockchains in comparison to public blockchains, and discuss the additional properties with respect to these restrictions. | |||
| In this article, we aim to lay out a set of requirements for designing cross-chain asset exchange protocols between permissioned blockchains. First we present a canonical motivating use case and then list the various patterns that such cases will follow in real-life scenarios. We then present a short survey of existing cross-chain exchange protocols for public blockchains, following which we summarise the building blocks, core mechanisms and security properties commonly involved in the protocol designs. We then analyze the requirements imposed by permissioned blockchains in comparison to public blockchains, and discuss the additional properties with respect to these restrictions. | |||
|
Also you need to follow the guidelines specified in |
Signed-off-by: Elias Rad <146735585+nnsW3@users.noreply.github.com>
There was a problem hiding this comment.
Thank you for the contribution @nnsW3! LGTM once the comments from @sandeepnRES have been addressed!
+1 |
|
|
@nnsW3 Read the |
|
@nnsW3 Plus one to the above. Are you still working on this PR? If not, that's OK too I'm just asking for house-keeping purposes, we'd like to not have dangling PRs open for too long if possible. :-) |
This PR addresses several typographical errors across various files in the project. The changes improve readability and maintain the professional standard of the documentation and code comments.
Justification
Typographical errors, while minor, can detract from the overall quality of the project. Correcting these errors ensures clarity and professionalism, making the project more accessible and understandable for current and future contributors.
Hope it helps.