On Wed, Jun 19, 2013 at 05:28:15PM +0200, Adam Back wrote: > I think Timo's point is that while you cant do discrete log, you can do y-th > root. So if P = xG is a parent public key (x private key, G base point), > then your proposed multiplier address is hash of Q=yP. However its easy to > find another P such that Q=zP'. ie just "divide by z" (EC multiply by z^-1 > mod n, n the order of the curve). So P'=z^-1.Q, which will work because > Q=zP', substituting P' you get Q=z.z^-1.Q, Q=Q. > > Of course the attacker has just performed an unspenable DoS (maybe, or maybe > a useless collision) because he wont know the discrete log of Q, nor P, nor > P'. So thats the question, does the protocol have any reliance on knowing > the discrete log - is it a problem if someone can find different multipliers > of different (unknown, uncomputable discrete log) parent keys. > > If it was a concern I guess you could require a proof of knowledge of > discrete log. ie as well as public key parent, multiplier the address must > include ECDSA sig or Schnorr proof of knowledge (which both demonstrate > knowledge of the discrete log of Q to base G.)

The "concern" (if there is any) would be that the owner of the parent P=xG, i.e. the person knowing x, in addition to y creates another pair (P',z) such that yP=Q=zP' and uses that second pair maliciously later on (such as claiming the payment went to identity P' not P). Since the owner of P knows the private key for P' (x*y*z^-1) he can also produce proof of knowledge for discrete log for P'. I think adding proof of knowledge or signatures on the multiplier don't help to eliminate all possible concerns, which could involve proving something to a third party that has not seen the communication between payer and payee. If you consider only payer and payee then Alan's original proposal is just fine, as far as I can tell. Only if you start using it in a payment protocol or, more precisely, if you start interpreting P as an identity (as Alan suggested in subsequent posts) _and_ this identity is a public/global one rather than a local one that only the payer uses, then reasons can pop up to eliminate ambiguity about which identity each payment went to. Timo ps the fact that this post used the multiplicative rather than additive derivation scheme doesn't change the argument. -- Timo Hanke PGP 1EFF 69BC 6FB7 8744 14DB 631D 1BB5 D6E3 AB96 7DA8 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development