User comment on docs (so we don't lose it)

[tjayrush]

so the index is obviously a huge deal but you don't give a short & sweet TLDR on what that actually is. It sounds like it's an index of ALL addresses that appear anywhere on the Ethereum chain with a pointer to where they appear (which block/tx/storage/event/etc). And I need to download or build it so that later on I can efficiently query it (I know there's some way to do parts of it on the fly). Is that correct?
2:24 PM
I'm not very smart so I just follow your docs step by step.

1. install - all worked fine, thanks for the detailed docs here!
   2:25 PM
2. Build Unchained Index - here I start running into issues. I have my fully synced and archived Erigon main net node, so I am obviously going for the full tin foil hat option of building the index locally from my node. The overview table on
   https://trueblocks.io/docs/install/get-the-index/
   tells me to use chifra scrape for that case. But it seems like I need to do an init first? So did that and then it seems chifra scrape needs an additional argument. That process is not so well documented.
   2:29 PM
   Since I don't quite understand what indexer or monitor means, I decide to do chifra scrape both just to be on the safe side and I got enough NVMe disk space anyway all for TrueBlocks so I don't care ;-)
   Turns out chifra scrape both needs a --file option for the monitor (which I don't know what it is so I ignore it)
   2:31 PM
   So now I go for chifra scrape indexer and I'm expecting it to take 3 days but somehow I came back after maybe 8h and it's done - is that expected?
   so now that it's done - it would be great to somehow verify that my local index got build entirely. I'm not sure how to do that.
   anwyay, I can probably figure it out but wanted to give some pointers where you can expand the docs a bit for naive users like myself. Great job on building this tool ser!
   2:34 PM
   Hm running it again with -v and seeing that maybe there's something wrong, any idea if this means all ok?

00019949 (    391)- <WARNG> : Blaze quit without finishing. Reprocessing...
INFO[31-05|20:35:16.786] Close enough to head. Sleeping for 13 seconds.

2:36 PM
Do you mind terribly if I copy this into my public discord? That way others can benefit from the discussion.
If not, that's totally cool, I can answer it here. Just thought I'd ask.
3:15 PM
Wow -- you've found me out -- the docs SUCK.
Thank you so much for putting this together. I'm going to copy it into an issue so I don't lost this super helpful report.
I have a few things to do this week, but docs is now high on my agenda for the coming weeks.
3:17 PM
github.com
Separate chifra scrape indexer and chifra scrape monitors · Issue #2144 · TrueBlocks/trueblocks-core
First, ignore monitor for now. That's an unrelated thing and there should even be a both. Issue:
Second, if you do chifra status --terse you can see where the two primary data folders are: cachePath and indexPath. For the scraper, you're only really interested in the indexPath.
If you do ls -lR on that path, you'll see a bunch of stuff. If you wanted to, you can remove all the contents of that folder (but leave the folder intact).
Then you can do chifra init --all and get the latest published index.
If you do ls -lR again, you should see two subfolders, finalized and blooms.
Then you can run chifra scrape indexer to catch up to the head of the chain and stay caught up.
3:37 PM
I run chifra scrape indexer in an ssh session, so I can close it down, but someone wrote this article about making it an os service: https://magnushansson.xyz/blog_posts/crypto_defi/2022-01-10-Erigon-Trueblocks. It's for Ubuntu, but you can figure it out for a Mac.
3:38 PM
Before you do any of that stuff above -- do git pull on the develop branch, then cmake ../src and make in the build folder. That should correct the weird issue you're seeing with blaze.
Let me know if any of that doesn't work out and I will further clarify.
Thanks so much for your interest and support. It's appreciated.
3:42 PM
No file chosen