[BOUNTY] $5000 BitUSD - LibSecp256k1 integration with FC

testz · March 06, 2015, 10:46:16 AM

Quote from: pc on March 06, 2015, 08:40:08 AM
I'll take the challenge.

+5%

cube · March 06, 2015, 10:25:10 AM

Quote from: cass on March 06, 2015, 09:16:19 AM
Quote from: pc on March 06, 2015, 08:40:08 AM
I'll take the challenge.

+5%

Way to go!

cass · March 06, 2015, 09:16:19 AM

Quote from: pc on March 06, 2015, 08:40:08 AM
I'll take the challenge.

+5%

svk · March 06, 2015, 08:50:51 AM

Quote from: pc on March 06, 2015, 08:40:08 AM
I'll take the challenge.

Awesome! :) I asked about this on github a while back, it looks like it could be a real gamechanger in terms of scanning speed for the client.

This is a quote from Gavin Andresen in his blog post talking about increasing the block size of Bitcoin:

QuoteOf course, we won't be running current code on tomorrow's hardware; we'll be running better code. CPU usage should go down by a factor of about eight in the next release when we switch to Pieter's libsecp256k1 library for validating transactions.

pc · March 06, 2015, 08:40:08 AM

I'll take the challenge.

cube · March 06, 2015, 08:16:27 AM

Quote from: bitmarket on March 06, 2015, 03:53:23 AM
For the non-techies.... what is this about?

Bitcoin uses secp256k1 to digitally sign and verify transactions. This link may give a clue - http://bitcoin.stackexchange.com/questions/36136/is-libsecp256k1-faster-than-openssl

xeroc · March 06, 2015, 07:54:31 AM

Quote from: jsidhu on March 06, 2015, 07:32:17 AM
Btw secp256k1 is experimental and bitcoin hasnt given it the nod yet.. Why do this?

secp256k1 is a set of parameters for a elliptic curve and not a piece of software
https://en.bitcoin.it/wiki/Secp256k1

jsidhu · March 06, 2015, 07:32:17 AM

Quote from: testz on March 06, 2015, 02:09:55 AM
Good starting point/example can be Auroracoin sources where it's implemented (see define USE_SECP256K1):
https://compilr.com/einsteinz/auroracoin-core/src/key.cpp

Whole sources from compilr.com can be found here: https://mega.co.nz/#!VJYRXQ7A!7LjU3M8iXWZlf4WIoRdrZw7gYXL_abtNgjxeQTyYxPQ

They just based off of latest btc.... Best to look here instead https://github.com/bitcoin/bitcoin/commit/16a58a86442ad587449f321c0dbab08cc028c2bd

Btw secp256k1 is experimental and bitcoin hasnt given it the nod yet.. Why do this?

bitmarket · March 06, 2015, 03:53:23 AM

For the non-techies.... what is this about?

testz · March 06, 2015, 02:09:55 AM

Good starting point/example can be Auroracoin sources where it's implemented (see define USE_SECP256K1):
https://compilr.com/einsteinz/auroracoin-core/src/key.cpp

Whole sources from compilr.com can be found here: https://mega.co.nz/#!VJYRXQ7A!7LjU3M8iXWZlf4WIoRdrZw7gYXL_abtNgjxeQTyYxPQ

eagleeye · March 06, 2015, 01:20:06 AM

Bytemaster read Rgcryptos blog https://rgcrypto.wordpress.com

He may have found the secret sauce for bitshares success or failure. I understand this is not related.

bytemaster · March 06, 2015, 12:09:10 AM

I would like to have a drop in replacement that implements this api:
https://github.com/BitShares/fc/blob/master/include/fc/crypto/elliptic.hpp

Using:
https://github.com/bitcoin/secp256k1

To get the bounty the pull request must be merged and proven to work with BitShares main client.