mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 03:52:49 +01:00
d1200755f1
c8176b3cc7556d7bcec39a55ae4d6ba16453baaa Add linter: Make sure we explicitly open all text files using UTF-8 or ASCII encoding in Python (practicalswift) 634bd970013eca90f4b4c1f9044eec8c97ba62c2 Explicitly specify encoding when opening text files in Python code (practicalswift) Pull request description: Add linter: Make sure we explicitly open all text files using UTF-8 encoding in Python. As requested by @laanwj in #13440. Tree-SHA512: 1651c00fe220ceb273324abd6703aee504029b96c7ef0e3029145901762c733c9b9d24927da281394fd4681a5bff774336c04eed01fafea997bb32192c334c06 Signed-off-by: pasta <pasta@dashboost.org> # Conflicts: # contrib/devtools/circular-dependencies.py # contrib/linearize/linearize-data.py # contrib/linearize/linearize-hashes.py # contrib/seeds/generate-seeds.py # contrib/verify-commits/verify-commits.py # test/functional/multiwallet.py # test/functional/notifications.py # test/functional/test_runner.py # test/util/rpcauth-test.py |
||
---|---|---|
.. | ||
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. The scripts run using Python 3 but are compatible with Python 2.
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
).