My spv node received in a nTx = 2 in headers message

My spv node received in a nTx = 2 in headers message

I am coding an spv node for dogecoin. I am syncing the headers and I am exceping to have nTx=0 for all the headers received but for one of the headers i have a nTx = 2 and some weird data following...

{ version: 6422786,
 previousHash: 'b7ac5cc3ca94d8b154661cba795fc4912f3b6ce83a3c5669053e7f677b360dab',
 merklerootHash: 'd55d5c789080a64707a528ce06c80b36708910d80126f0b0f5c5a73534333354',
 time: 1407228150,
 nBits: 503697504,
 nonce: 0,
 hash: '47cf9eaf17f37672ef610c15c6aeb5257c318e76943b809d79c6fb486fd36115',
 transactionCount: 2 }

I am doing something wrong ?

https://ift.tt/2IQ5hsl

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