trueblocks-core
trueblocks-core copied to clipboard
One possible mode of operation
- User creates a file containing address (in exactly the same way he/she does now with
chifra monitor). - User runs scraper
- When scrape consolidates a block, and any of the addresses are in that chunks, and if the user has it so configured (consider two options
--pinand--allas perchifra init):- if not
--pinand not--all, store only the bloom on disc (remove the index chunk), - if not
--pinand--all, store both bloom and index chunk on disc, - if
--pinand not--all, store and pin the bloom, - if
--pinand--all, store and pin both, Otherwise, store nothing. (or maybe just the bloom).
- if not
Upshot: using monitors, we can allows the user to either init or scrape and pin only their own data even on an ongoing basis.
(This is not completely thought out, but it's close...) The idea is that now (as it works now), once the user starts scraping, he/she is taking on the burden of all chunks thereafter, whereas if they had a monitored addresses file, only those chunks that mattered could be stored.