2 ms·
I can discern two different approaches in the articles. A) Hard Bitcoin Fork article's approach: You publish a zero-knowledge proof that you have a solution, b
by SilasX 12y ago
I can discern two different approaches in the articles.
A) Hard Bitcoin Fork article's approach: You publish a zero-knowledge proof that you have a solution, but not the solution itself. See my summary: https://news.ycombinator.com/item?id=7891243 https://news.ycombinator.com/item?id=7891243
B) Current article's approach: require that the solution be signed with the (primary?) recipient's private key.
A) prevents collaboration because a member who finds the solution can keep it for themselves, and its content is not revealed (only a ZKP is) so the pool doesn't even recognize it as "their" solution.
B) prevents collaboration because you'd have to give out the private key to any contributor, all of whom would send out competing spend messages as soon as the solution went out.
Can anyone who understands them confirm my summary?