mirror of
https://github.com/dashpay/dash.git
synced 2024-12-26 04:22:55 +01:00
60b3c5a64e
3d0a82cff8cbb809876e82dbe62d14d2adc07d94 devtools: Accomodate block-style copyright blocks (Ben Woosley) 0ef0e51fe4bb592e67255776b5a0ba04679fb8c4 lint: Bump flake8 to 3.7.8 (Ben Woosley) 838920704ad90a71cf288b700052503db8abb17e lint: Disable flake8 W504 warning (Ben Woosley) b21680baf5391a602b295b9d7d0ef66553661cb9 test/contrib: Fix invalid escapes in regex strings (Ben Woosley) Pull request description: This is a second go at #15221, fixing new lints in: W504 line break after binary operator W605 invalid escape sequence F841 local variable 'e' is assigned to but never used This time around: * One commit per rule, for easier review * I went with the PEP-8 style of breaking before binary operators * I looked into the raw regex newline issue, and found that raw strings with newlines embedded do work appropriately. E.g. run `re.match(r" \n ", " \n ")` to check this for yourself. `re.MULTILINE` exists to modify `^` and `$` in multiline scenarios, but all of these searches are per-line. ACKs for top commit: practicalswift: ACK 3d0a82cff8cbb809876e82dbe62d14d2adc07d94 -- diff looks correct Tree-SHA512: bea0c144cadd72e4adf2e9a4b4ee0535dd91a8e694206924cf8a389dc9253f364a717edfe9abda88108fbb67fda19b9e823f46822d7303c0aaa72e48909a6105 |
||
|---|---|---|
| .. | ||
| example-linearize-testnet.cfg | ||
| example-linearize.cfg | ||
| linearize-data.py | ||
| linearize-hashes.py | ||
| README.md | ||
Linearize
Construct a linear, no-fork, best version of the Dash blockchain.
Step 0: Install dash_hash
https://github.com/dashpay/dash_hash
Step 1: Download hash list
$ ./linearize-hashes.py linearize.cfg > hashlist.txt
Required configuration file settings for linearize-hashes:
- RPC:
datadir(Required ifrpcuserandrpcpasswordare not specified) - RPC:
rpcuser,rpcpassword(Required ifdatadiris not specified)
Optional config file setting for linearize-hashes:
- RPC:
host(Default:127.0.0.1) - RPC:
port(Default:9998) - Blockchain:
min_height,max_height rev_hash_bytes: If true, the written block hash list will be byte-reversed. (In other words, the hash returned by getblockhash will have its bytes reversed.) False by default. Intended for generation of standalone hash lists but safe to use with linearize-data.py, which will output the same data no matter which byte format is chosen.
The linearize-hashes script requires a connection, local or remote, to a
JSON-RPC server. Running dashd or dash-qt -server will be sufficient.
Step 2: Copy local block data
$ ./linearize-data.py linearize.cfg
Required configuration file settings:
output_file: The file that will contain the final blockchain. oroutput: Output directory for linearizedblocks/blkNNNNN.datoutput.
Optional config file setting for linearize-data:
debug_output: Some printouts may not always be desired. If true, such output will be printed.file_timestamp: Set each file's last-accessed and last-modified times, respectively, to the current time and to the timestamp of the most recent block written to the script's blockchain.genesis: The hash of the genesis block in the blockchain. (default is '00000ffd590b1485b3caadc19b22e6379c733355108f107a430458cdf3407ab6', mainnet)input: dashd blocks/ directory containing blkNNNNN.dathashlist: text file containing list of block hashes created by linearize-hashes.py.max_out_sz: Maximum size for files created by theoutput_fileoption. (Default:1000*1000*1000 bytes)netmagic: Network magic number. (default is 'bf0c6bbd', mainnet)out_of_order_cache_sz: If out-of-order blocks are being read, the block can be written to a cache so that the blockchain doesn't have to be sought again. This option specifies the cache size. (Default:100*1000*1000 bytes)rev_hash_bytes: If true, the block hash list written by linearize-hashes.py will be byte-reversed when read by linearize-data.py. See the linearize-hashes entry for more information.split_timestamp: Split blockchain files when a new month is first seen, in addition to reaching a maximum file size (max_out_sz).