29

First you must configure your bitcoin.conf file for JSON-RPC rpcallowip=127.0.0.1 rpcuser=yourusername rpcpassword=reallystrongpasswordthatsnothis rpcport=7788 walletnotify=/home/scripts/transaction.sh %s Where transaction.sh is some bash program. One approach is to have it make an http request to some process to notify you of the deposit. An example: #!/...


6

Using walletnotify has proven to work and is used by a lot of scalable apps today. I would not rely on it completely though. walletnotify's job is to execute a shell command every time it receives a wallet transaction. This means data is flowing between processes, which does not make me entirely comfortable as a developer. After all, it only takes one error ...


2

I don't know of a solution that works out-of-the-box with the requirements you've set. However, you can do some of what you need using some command-line tools available on github. Pycoin has a key utility which can be used to derive bip0032 addresses given a root. Here's a quick primer on how to use it: $ git clone http://github.com/richardkiss/pycoin $ cd ...


2

This is not possible with the current version of Bitcoin-Core (0.13.1). Consider opening a issue (feature request) https://github.com/bitcoin/bitcoin or start implementing it yourself.


2

Jeff Garzik's PyNode will, by default, connect to a Bitcoin Core running on local host a as a full node and download each transaction your node relays to it. If you know Python, you can add extra triggers and post-processing to it. Note, PyNode seems to be abandonware, and I think you currently need to hack it to get it to work with the latest versions of ...


2

You could also use our own Websockets API. More specifically, you need to check the addresses event in order to subscribe to one or multiple address and receive balance updates for them. An example request command would be: { "event": "addresses:update", "filters": { "addresses": ["1Biteasym3p5E4soZq8So6NjkjYugEnz2X"] } } And when the ...


2

walletnotify will execute every time you either 1.receive bitcoin 2.send bitcoin 3.when a bitcoin gets its first confirmation. @Dawg are you transfer payment in your wallet it self ? if yes then OK , if not try to send/receive the payments from other bitcoin node then you can observe clearly ,Cheers


1

You are in blocks only mode as you have blocksonly=1 set in your bitcoin.conf. This means that your node will not receive or relay unconfirmed transactions. You only see blocks and the transactions that come in blocks. Thus the first time your node will see an incoming transaction is when it is first included in a block.


1

Without installing software on your own servers, the only way to accomplish this is with 3rd Party services. Some offer Email notification of payments via email. blockcypher.com is an example of this.


1

You need a server which indexes by address. Libbitcoin-server provides this index. All tx’s to or from an address of interest will trigger a notification to your subscribing client. https://github.com/libbitcoin/libbitcoin-server/wiki Of course you can always build your own address index.


1

Yeah, All bitcoin forks support walletnotfiy. most digital-currencies have a walletnotfiy with some a few code changes. that's a list of all Bitcoin forks


1

In your example you are telling it to place the transaction id as a GET request in the URI under the tx parameter. walletnotify=curl http://My.IP.Address:PortAppUses/walletnotify.js?tx=%s All you would need to do inside of walletnotify.js is pull the tx GET, in nodejs express that would be something like: const express = require("express"); const app = ...


1

Probably there's no technical problems and its highly depending on your server. if your server is having no issues so nothing to worry about. I have tried to send 1000 request to bitcoin-core server in the same time with a basic server and everything is worked great. Also you can get like more than one bitcoin core server and deal the requests to these ...


1

1) Your command line looks fine. Remember that %s will be replaced by a transaction id, such as 9de5056696618f22237eb280bbefe94c1d19661de960a1f2c546a0e3a2bc4600. So if you can run the script at the command line like this you should be ok: C:\Python27\python.exe D:\LiVe\listener.py 9de5056696618f22237eb280bbefe94c1d19661de960a1f2c546a0e3a2bc4600 2) The ...


Only top voted, non community-wiki answers of a minimum length are eligible