Quote from: skyzer on September 15, 2014, 08:36:09 AM

Quote from: BitCoinDream on September 14, 2014, 02:05:11 PM

Quote from: skyzer on September 13, 2014, 10:58:41 PM

hey,
we don't have a demo for that, you can install it yourself it easily. this was the idea that you can host on your own same kind of API like blockchain.info so you are not dependent on any third party provider. you can find the documentation in the github. it is neatly split up how to install environment, bitcoind and the project itself.

answering your question, the wallet folder you pointed is actually unfinished demo app that used our built API. without it the API still works seamlessly, because API is not dependent on the wallet.
the blockchain.info api_send is in the api.php file https://github.com/goethewins/EzBitcoin-Api-Wallet/blob/master/applications/api/controllers/api.php
more exactly public function receive() method, which starts from line 611.
when payment is received the bitcoind shoots the txid to method public function callback() which starts from line 335. And there it does the same thing as blockchain.info - shoots the response to the provided callback url.

next week we are going to announce the release of our payment processor and also mention this open source API for bitcoin.

The functionality u have described in red is the functionality of https://blockchain.info/api/api_receive. But I was asking for https://blockchain.info/api/api_send, which is actually canonical to https://blockchain.info/api/blockchain_wallet_api. Is not it done in the project ?

If yes, then do u access blockchain.info wallet directly or use own Bitcoin-QT wallet running on the installed BitcoinD ?

Sorry for confusing. Actually it is done and this is the initial functionality we did, and receive was built additionally.
We don't use blockchain.info for that, that's the initial idea not to be dependent on 3rd party. We use own installed bitcoind on own hardware. The tutorial is here. So as the idea was if u're using the blockchain.info API and want to switch to your own and not be dependent on them (3rd party) then this is what we made exactly. The URI's, arguments and JSON response are also same as blockchain.info so all u have to do is change the domain.

The code for send is also in the same api.php file.
We didn't do 100% of all of them, but we have all necessary ones:
Making Outgoing Payments - payment() function
Fetching the wallet balance - balance()
Generating a new address - new_address()
Http Callbacks - callback()

So other stuff like address archiving, listing addresses and sending multiple transactions is really not necessary.
Maybe the only 2 things that may be useful is the resending the callback to callback_url up to 1000 times if the client didn't respond with *ok* (right now it sends callback twice - once transaction hits mempool and on 1st confirmation just like bitcoind shoots on walletnotify). The second one is get the balance of an address, because we didn't find a good way for that. Bitcoind doesn't have RPC command for address'es current balance and didn't decide to parse from rawtransactions to get the outputs. Does anybody know more solutions how to get current balance of specific address in bitcoind?

But for now the above implemented commands are enough to build quite any bitcoin startup. We are using it already in 3 different projects.

1. I think send to many is a necessary feature for real businesses as it saves on miner's fee.

2. Getting current balance of specific address in bitcoind requires to traverse the whole blockchain to sum up all the transactions which has this address either in i/p or o/p. This is actually done in a block explorer. Abe is an open source block explorer which does this. U may read more about Abe here => https://bitcointalk.org/index.php?topic=22785.0