BitcoinD Fails to Return Transaction Data After Receiving GetData P2P Message

Question: I’m developing a Neutrino client that communicates with BitcoinD. Most P2P messages are working as expected, but when I send a GetData message for a transaction (Tx type), BitcoinD doesn't respond with the expected transaction data. I’ve verified that the transaction is indeed present on the node. Below is the log from BitcoinD:

2024-10-16T11:24:22Z [net] received getdata (1 invsz) peer=32  
2024-10-16T11:24:22Z [net] received getdata for: tx  
c1b5b6fb155a8fd41d241abe5efb5aa9de7c8942fdd923ad1e6d94e9deedc3f9 peer=32

Here are the details of my setup:

BitcoinD version: 24

Configuration:

bitcoind  
-server=1  
-regtest=1  
-rpcauth=:  
-debug=1  
-zmqpubrawblock=tcp://0.0.0.0:28334  
-zmqpubrawtx=tcp://0.0.0.0:28335  
-zmqpubhashblock=tcp://0.0.0.0:28336  
-txindex=1  
-dnsseed=0  
-upnp=0  
-rpcbind=0.0.0.0  
-rpcallowip=0.0.0.0/0  
-rpcport=18443  
-rest  
-listen=1  
-listenonion=0  
-fallbackfee=0.0002  
-blockfilterindex=1  
-peerblockfilters=1  

Has anyone encountered a similar issue? Any suggestions on what could be going wrong here or how I might troubleshoot this further?



from Recent Questions - Bitcoin Stack Exchange https://ift.tt/UawqMiC
via IFTTT

Popular posts from this blog

Bitcoin Mining Could Be Strengthening The Ruble, Russian Central Bank Says

Crypto Exec Warns Tokenization Is Moving Faster Than Expected

Bitwise Clients Pour $69M Into Solana as Bulls Fight to Reclaim $200 Resistance Zone