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

Publish 2-Party chaincode protocol specification #14

Open
oleiba opened this issue Dec 10, 2018 · 10 comments
Open

Publish 2-Party chaincode protocol specification #14

oleiba opened this issue Dec 10, 2018 · 10 comments

Comments

@oleiba
Copy link
Contributor

oleiba commented Dec 10, 2018

We need a specification of the protocol to better support binding tools, i.e., libs-core-bindings.

@omershlo
Copy link
Contributor

chain code is the result of a ECDH key exchange:

  • input: each party choose random number a,b
  • output: abG where G is the EC generator

is this what you meant ?

@Wahahahahahahahahahaha
Copy link

hi,
What's the difference between abG and public key Q?

@Wahahahahahahahahahaha
Copy link

And,
In the 2P-algorithm of the whilt paper, there is a symbol that its meaning was not explained. Please confirm it.

@omershlo
Copy link
Contributor

If I understand you correctly, Q and abG are the same.

What symbol do you refer to?

@Wahahahahahahahahahaha
Copy link

I dont't think so. Because abG is chain code that is used for all key derivations. So the chain code abG cann't be opened. However the pubilc key Q can be opened that is used for Verifying the signature of the transaction. And what do you think about it ? Thanks

@Wahahahahahahahahahaha
Copy link

If the chain code abG is opened everyone could deduce all keys. Then assets eof blockchain's wallets is unsafe.

@Wahahahahahahahahahaha
Copy link

I will tell you the symbol I refer to because formulas cannot be edited on Git

@omershlo
Copy link
Contributor

right right, sorry for misleading you.
Q the public key and cc= abG have the same structure but different meaning.
cc is computed using diffie helman key exchange and we don't really care about the a and b, cc is used for key generation, known to both parties and even if it goes public an attacker will only be able to derive public keys and not compromise the secret keys.
Q is a specific public key that in our case is the result of multiplicative secret sharing

@Wahahahahahahahahahaha
Copy link

Wahahahahahahahahahaha commented Aug 19, 2019 via email

@omershlo
Copy link
Contributor

no problem.
Can you be more specific about your question please?
what vector of indices are you referring to? maybe put a link to the code?

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

No branches or pull requests

3 participants