mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 20:12:57 +01:00
4aa197dbdb
fa4632c41714dfaa699bacc6a947d72668a4deef test: Move boost/stdlib includes last (MarcoFalke) fa488f131fd4f5bab0d01376c5a5013306f1abcd scripted-diff: Bump copyright headers (MarcoFalke) fac5c373006a9e4bcbb56843bb85f1aca4d87599 scripted-diff: Sort test includes (MarcoFalke) Pull request description: When writing tests, often includes need to be added or removed. Currently the list of includes is not sorted, so developers that write tests and have `clang-format` installed will either have an unrelated change (sorting) included in their commit or they will have to manually undo the sort. This pull preempts both issues by just sorting all includes in one commit. Please be aware that this is **NOT** a change to policy to enforce clang-format or any other developer guideline or process. Developers are free to use whatever tool they want, see also #18651. Edit: Also includes a commit to bump the copyright headers, so that the touched files don't need to be touched again for that. ACKs for top commit: practicalswift: ACK fa4632c41714dfaa699bacc6a947d72668a4deef jonatack: ACK fa4632c41714dfaa, light review and sanity checks with gcc build and clang fuzz build Tree-SHA512: 130a8d073a379ba556b1e64104d37c46b671425c0aef0ed725fd60156a95e8dc83fb6f0b5330b2f8152cf5daaf3983b4aca5e75812598f2626c39fd12b88b180 |
||
---|---|---|
.. | ||
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 ifrpcuser
andrpcpassword
are not specified) - RPC:
rpcuser
,rpcpassword
(Required ifdatadir
is 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.dat
output.
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_file
option. (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
).