You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+27-38Lines changed: 27 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ It assumes a local copy of the blockchain, typically downloaded by Bitcoin core.
15
15
The program flow is split up in two parts.
16
16
Lets call it ParseModes:
17
17
18
-
***HeaderOnly**
18
+
***Indexing**
19
19
20
20
If the parser is started the first time, it iterates over all blk.dat files and seeks from header to header. It doesn't evaluates the whole block it just calculates the block hashes to determine the main chain. So we only need to keep ~50 Mb in RAM instead of the whole Blockchain. This process is very fast and takes only **7-8 minutes with 2-3 threads and a average HDD (bottleneck here is I/O)***.
21
21
The main chain is saved as a JSON file, lets call it ChainStorage. (The path can be specified with `--chain-storage`)
@@ -117,7 +117,7 @@ Transaction Types:
117
117
118
118
***Resume scans**
119
119
120
-
If you sync the blockchain at some point later, you don't need to make a FullData rescan. Just use `--resume` to force a HeaderOnly scan followed by a FullData scan which parses only new blocks. If you want a complete FullData rescan delete the ChainStorage json file.
120
+
If you sync the blockchain at some point later, you don't need to make a FullData rescan. Just use `--resume` to force a Reindexing followed by a FullData scan which parses only new blocks. If you want a complete FullData rescan delete the ChainStorage json file.
121
121
122
122
## Installing
123
123
@@ -179,51 +179,42 @@ Now export this wrappper with: `export RUSTC="./rustc-wrapper.sh"` and execute `
0 commit comments