Oh true they parse it all
You can also look into blockchain.info code or Bitcoin abe
Topic: Transactions returned by getdata (Read 702 times)
Armory is also able to find transactions somehow, look into their code
I think they just trust the node they connect to. When a new block arrives, they download the entire block (I assume).
By local I meant rpc yes
Armory is also able to find transactions somehow, look into their code
Armory is also able to find transactions somehow, look into their code
From a remote node? You'd ask for the whole block. But which one? Locally you can use txindex=1
Ok, so a connection from localhost bypasses the flood protection? If txindex=1, then you can ask for any transaction?
I assume even without txindex=1, the UTXO set is indexed.
I looked it up from the code code (should have done that before).
From what I can see, there is no localhost exception. I guess RPC is the only way to do it.
From a remote node? You'd ask for the whole block. But which one? Locally you can use txindex=1
When pruning was added, random requests for transactions are no longer supported.
The wiki says that transactions must be in the "memory pool or relay set".
What transactions does that cover?
The memory pool contains all transactions that could be included in the next block. I assume the relay set is the subset of those transactions that would be relayed?
Are transactions with unspent outputs included too? They should be available, even with pruning.
The wiki says that transactions must be in the "memory pool or relay set".
What transactions does that cover?
The memory pool contains all transactions that could be included in the next block. I assume the relay set is the subset of those transactions that would be relayed?
Are transactions with unspent outputs included too? They should be available, even with pruning.
Jump to: