".may contain transactions that are interesting. but the check may be wrong (you may think a block is interesting while it isn't) svav: i wouldn't call it "representation" they don't encode the full block - more like a fancy checksum, which allows you to quickly check whether the block may be interesting to you what does that mean? It seems they've been implemented I looked up bips 157, 158, and they are both in "Draft" status. A blockfilter is a filter on the data in a block, allowing a compact representation of the data. it's just a way to quickly test whether a block may contain transactions that are interesting or not the light client requests the entire block if the filter indicates there's something they're interested in Kaizen_K_ : they enable a similar use case as the bloom filters but they are actually a replacement for the bloom filters where it allows a smaller amout of data to be sent around the network and reconstructed on the other end? A block filter is a compressed list of prevouts and UTXOs in a block Blockfilters are a replacement to bloom filters that allow light nodes to significantly reduce bandwidth, storage and verification without sacrificing privacy like bloom filters did. dergoegge: I understand it as something related to the bloom filter Does ACK stand for acknowledge or is it an acronym? It'd be nice to be able to comment on them inline just like for the code. I think it's a shame that the github review process de-emphasizes commit logs. ok next question: What are blockfilters and what are they used for? (hint: see BIP157 and BIP158) If you open a PR with just one commit, then github will use the commit log as the PR description by default. jnewbery: oh i pointed that out for the PR description, did not see it for the commit I'd like Matt to fix his commit log before I ACK it though :) ok lets get started: Did you review the PR? Concept ACK, approach ACK, tested ACK, or NACK? notes and questions are in the usual place: 2nd time and no clue, just lurking, thx :) today we are looking at #17631 - Expose block filters over REST feel free to say hi to let people know you are here Hi everyone! Welcome to this week's PR Review Club! Suggesting that the REST interface should be removed entirely in favour Want this ability for the REST interface? The JSON-RPC interface is already capable of serving blockfilters, why do we What are the main differences between the JSON-RPC and REST interface? What are blockfilters and what are they used for (hint: see BIP157 and BIP158) Just like the JSON-RPC interface it is not recommended to expose the RESTĭid you review the PR? Concept ACK, approach ACK, tested ACK, or NACK? Most of the endpoints support responding in three different formats: binary, Query the contents of a node’s mempool: /rest/mempool/contents.json.Query transactions by their ID: /rest/tx/.It can be enabled using the -rest config option. Is a lightweight interface that serves public data over HTTP on the same portĪs the JSON-RPC interface. The PR branch HEAD was 3684fb7ae at the time of this review club meeting. Expose block filters over REST ( rpc/rest/zmq) Oct 20, 2021
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |