accesses the full stored blockchain files (blk*.dat)?
Background: I'm wondering if it's worth it too store these in an Amazon S3 bucket symlinked to the blocks directory. Storage is cheap, but Amazon also charges for read/write requests, so this could get too expensive quickly if the whole chain is read often.
Quote from our Slack by kittywhiskers: the entire chain isn't read in one sitting per se by default but a certain amount of blocks going backwards are sanity-checked during launch, blocks are read from disk if they need to be given to peers who are requesting it (this could be anywhere across the entire chain), the entire db will be read if you decide to run a reindex or if the client believes there is corruption in the block index and needs to rebuild it, data will be written at every flush interval (so, this would flush the latest chain tip to disk for example) or when the client is shut down (forcing a flush to disk). also, the database will be locked by that instance of the client so it can't be shared between instances.
Thanks! That's very helpful. Did you actually pass my question on?
Обсуждают сегодня