Skip to content
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

Alternative construction of HTLC Execution Delivery Transaction #1

Open
neocarmack opened this issue Jan 28, 2020 · 0 comments
Open
Assignees

Comments

@neocarmack
Copy link
Member

neocarmack commented Jan 28, 2020

image

The transaction in RED box is the HTLC execution delivery transaction, which is locked by custom locking script.

To unlock this transaction, Bob shall provide three arguments: the preimage R, Alice2 and Bob2's signature. And in the process of HTLC, this preimage R is used to exchange money(token) in a channel.

But current Omnicore does not support custom redeem script in locking and unlocking a transaction. So can we just transform this non-standard transaction to a standard 3-3 multisig transaction, replacing R by another private key of an address(public key), which is already well supported by Omnicore.

This transformation is a little bit different from the original process in the white paper. There is no potential risk if we use 3-3 multiSig transaction, because essentially the two solutions are the same: given a number, image or private key, there is no polynomial algorithm to find its preimage or public key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant