Quote from: xeroc on July 23, 2015, 07:52:22 AM

Quote from: arhag on July 23, 2015, 05:47:19 AM
We still need libsecp256k1-zkp ported to Javascript for the web wallet. Have you looked into emscripten for that? I suppose one of the advantages of the Qt lightweight wallet that Nathan is working over the web wallet is that it can directly link with the C code. 

What would it cost to have YOU do it right away?
I feel you know the graphene code well already and am pretty damn certain the devs can need your assistance almost everywhere!!

Ahh.... Yes please!  +5%

Well done BM, good effort to bring that together.

Quote from: cube on July 23, 2015, 09:11:15 AM
Good to know privacy protection is (or going to be) back.  +5%

Amen.

Good to know privacy protection is (or going to be) back.  +5%

Quote from: arhag on July 23, 2015, 05:47:19 AM
We still need libsecp256k1-zkp ported to Javascript for the web wallet. Have you looked into emscripten for that? I suppose one of the advantages of the Qt lightweight wallet that Nathan is working over the web wallet is that it can directly link with the C code. 

What would it cost to have YOU do it right away?
I feel you know the graphene code well already and am pretty damn certain the devs can need your assistance almost everywhere!!

Quote from: jsidhu on July 23, 2015, 04:04:13 AM
Besides after blinded signatures were figured out (bounty?) then i think rest fell inplace

Just to clarify, confidential transactions (aka blinded amounts) don't really have much to do with the blinded signature algorithm that a bounty was offered for (aka Oleg Andreev's algorithm). The former hides the amount of stake an account holds or transfers. The latter allows for multisig / two-factor authentication where the third-party is unable to tell which transaction they signed. The latter is useful in stealth transactions because it allows the recipient to use multisig without revealing to anyone (including the signing third-party) the metadata of which balance belongs to which user (even if they still couldn't tell the actual amount of the balance since it would be blinded using the confidential transactions algorithm).

Quote from: bytemaster on July 22, 2015, 09:33:23 PM
No wallet support yet, but that is relatively easy.

We still need libsecp256k1-zkp ported to Javascript for the web wallet. Have you looked into emscripten for that? I suppose one of the advantages of the Qt lightweight wallet that Nathan is working over the web wallet is that it can directly link with the C code. 

Quote from: roadscape on July 22, 2015, 11:59:05 PM
+5%

But I thought you said the privacy solution was not going to be 'that' easy. Is there a catch?

sometimes in software thr tallest mountains have the easiest paths up and the shorter ones are taller than they first seem. Besides after blinded signatures were figured out (bounty?) then i think rest fell inplace

 +5%

But I thought you said the privacy solution was not going to be 'that' easy. Is there a catch?

Well done! :)

 +5%
Though I know nothing of coding  :P

Will this get implemented into the initial 2.0 release by chance?

https://github.com/cryptonomex/graphene/commit/be65c277c96b96cfa6e31773cce9805d3d51be87

No wallet support yet, but that is relatively easy.