Suggestions for bitcoin api | Bitcointalksearch.org

jseverson

hero member

Activity: 1834

Merit: 759

Quote from: justusranvier on October 24, 2013, 02:31:58 PM

You should look into using alternatives like Bits of Proof or btcd instead of limiting yourself to bitcoind.

from the wiki:

"One key difference between btcd and bitcoind is that btcd does NOT include wallet functionality and this was a very intentional design decision. See the blog entry here for more details. This means you can't actually make or receive payments directly with btcd. That functionality will be provided by the forthcoming btcwallet and btcgui."

so btcd is not an option

justusranvier

legendary

Activity: 1400

Merit: 1013

You should look into using alternatives like Bits of Proof or btcd instead of limiting yourself to bitcoind.

danneu

newbie

Activity: 32

Merit: 0

The most naive implementation would be to run bitcoind locally and let your webapp talk to it synchronously through the rpc interface.

From there, as needed, you can abstract your own async api around bitcoind, even move bitcoind to another server, and even spin up multiple bitcoind.

In general, I'd rather my mission-critical components be at the mercy of my own code rather than a "probabilistic" foreign api that does unexpected things.

jseverson

hero member

Activity: 1834

Merit: 759

We have been developing a bitcoin gaming site that is just about ready to launch. The last hurdle we've been struggling with is a reliable api that works 100% of the time. We were using blockchain.info's api, but have had issues with it in the past not sending callbacks to our site. We switched over to coinbase's api but that also seems to be somewhat untested and unreliable. Probably just need time to work out the kinks in their system, but we need a solution now.

We need the api for wallet creation with callbacks tied to that wallet address so that any btc payments sent to that new address will update the users balance on the site. So each new user gets their own unique wallet address generated and then they can send btc to that address and it will update their balance. We're just processing withdrawals manually right now, but eventually would need an api for sending btc from one wallet to another as well.

Should this just be done with the raw bitcoind api? https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)

Are there advantages to using 3rd party vs bitcoind? This api is mission critical for the website so we can't really afford it to work only 90% of the time.

Topic: Suggestions for bitcoin api (Read 523 times)