BlockNotify not working

BlockNotify not working

Hi my configured jsonrpc is following

maxconnections=200
maxuploadtarget=20
rpcuser=someusername
rpcpassword=somepassword
daemon=1
keypool=10000
walletnotify=curl "https://someurl.com/walletnotify?transaction_hash=%s"
blocknotify=curl "https://someurl.com/blocknotify?transaction_hash=%s"

I am getting notified on both wallet notify and block notify but the problem is the transaction is not the same for both. For Example I get f793d590bacffce8efd37c1b1e3db254950e925dd5bbd7f3a92c1db142f4dc37 from wallet notify and

00000000000000000038ffec8f035d54558a78e94ae1138ac5bdf1470fb0863f

from block notify. Please help what have I missed or done wrong here?

https://ift.tt/2IZ2BGd

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more