Skip to main content

Timeline for How exactly does SPV work?

Current License: CC BY-SA 4.0

7 events
when toggle format what by license comment
Jun 18, 2018 at 15:15 comment added Kyle Graham Ahh alright, the table is very helpful. Thanks for the information
Jun 18, 2018 at 14:50 comment added MCCCS Actually, my mistake. They do hand out public keys along with some fake public keys. (Only pre-Bip37 download-everything nodes don't share public keys, aka "pruned".) As described in the table below merkleblock, the nodes send [all transactions in those blocks]'s hashes. Filteradd tells the nodes which pubkeys the SPV is interested in. If the block didn't pass the bloom filter, the nodes can omit tx hashes and save data. May give some more details: bitcoin.stackexchange.com/a/11721/38618
Jun 18, 2018 at 14:12 comment added Kyle Graham Oh, I thought filteradd was a rpc command. If they do not hand out public keys, then when an spv has gone away for a while, he will download the headers once he is back and then what does he send to the node, to get the relevant information? I see data in filteradd, but what is the data? Thanks again for the help
Jun 18, 2018 at 14:05 comment added MCCCS They don't use gettxout. Here's what they use. Furthermore, SPVs never hand out the public keys, that'd damage privacy.
Jun 18, 2018 at 14:03 history edited MCCCS CC BY-SA 4.0
added 36 characters in body
Jun 18, 2018 at 13:50 comment added Kyle Graham If mobile/light clients do not use rpc, how is it possible for them to query nodes using commands like gettxout? Or other people to query nodes using gettxout? Also, if I give the node the public key and not a transaction then it would need to scan the whole chain? Because light wallets give public keys to the full node and not transactions to my understanding
Jun 18, 2018 at 13:46 history answered MCCCS CC BY-SA 4.0