Blockchain.info compatibility about bitcoinlib HOT 7 CLOSED

BitcoinLib has not been tested against blockchain.info's API.

A request to provide us with further info has just been made to blockchain.info. Should they respond in timely manner we'll get to track down what the issue really is.

In the meantime I would suggest debugging the RPC calls with Fiddler: http://www.telerik.com/fiddler (switch the calls on the right hand side to JSON).

You can also use the raw RPC connector class provided by this library for debugging (and only): https://github.com/GeorgeKimionis/BitcoinLib/blob/master/CoinWrapper/RPC/Connector/RawRpcConnector.cs

BTW a quick search revealed that this is a rather old problem: https://bitcointalk.org/index.php?topic=139620.0 so let's wait and see what will be blockchain.info's response.

from bitcoinlib.

FYI Blockchain.info's response:

There is a significant amount of work to be done to make BitcoinLib compatible with Blockchain.info's API which cannot be provided at the moment, I am aware of a few developers from the community though who could perform these changes in exchange for some bounty.

from bitcoinlib.

I'm confused, blockchain.info has an API which is supposed to be a "Bitcoind compatible RPC api" https://blockchain.info/en/api/json_rpc_api
and in facts most of the call I have tested already work with BitcoinLib, it is only the calls for which a second password is needed that I could not make work.
So could you tell me more about what needs to be done to make BitcoinLib fully compatible, and why is it a significant amount of work?

from bitcoinlib.

I requested an API key on https://blockchain.info/api/api_create_code on June 19th, stating explicitly that it is for making this library compatible with their API, however I never received any code from them, so that is a bit of a problem. I just opened a new ticket to their support, stating the above.

There are structural changes that need to be performed for this library to be able to deal with the second password parameter. For instance, the credentials are being encapsulated into a NetworkCredential instance which is then broadcasted over an HttpWebRequest, however NetworkCredential doesn't have an option for a second password, so it will have to be fit to the domain parameter or another approach must be used, and this is just one of the parts that will need refactoring. Modifying core components will require us to perform all tests all over again, which is a significant amount of work.

from bitcoinlib.

I throw in the towel.

from bitcoinlib.

Actually I just tested again and BitcoinLib already works with blochaininfo RPC API.

Previously I was confused, I thought the second password of your blockchain info wallet should be set as the walletPassword (4th parameter) of the BitcoinService constructor, but it turns out that this second password should actually be used as a wallet passphrase. So if you want to use methods such as SendToAddress you need to call WalletPassphrase method just before that.

from bitcoinlib.

That's great news, thanks for the update.

from bitcoinlib.