-
Notifications
You must be signed in to change notification settings - Fork 648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTLC Operations memo (optional) item #1967
Comments
Perhaps include this in bitshares/bsips#195 . |
I like the idea. Should it work like transactions, where there is a separate memo signing key? I think not, as the information should probably be public. |
I think memos should be encrypted using sender's and recipient's memo keys, as in transactions. |
On some chains they are encrypting it, on some they don't. I believe for the sake of protecting memo it should be encrypted because the usage itself of the memo will be only in case of HTLC contract already created and sent to particular BTS account, there is no need for someone else to read it. |
Added to BSIP 64. |
Fixed via #1998. |
HTLC Operations memo (optional) item
Introducing this feature is very helpful step to satisfy the future of Cross Chain Swaps, parties involved within the Cross Chain Swaps will have to communicate their external addresses or references and info within the HTLC transaction upon creation.
In case we implement Cross Chain Swap feature within our UI in future, the memo (optional) item field will be used to communicate and to confirm external addresses and will be used as reference for transaction.
The text was updated successfully, but these errors were encountered: