GitLab

The current logic for syncing headers may lead to lots of duplicate
getheaders requests being sent:  If a new block arrives while the node
is in headers sync, it will send getheaders in response to the block
announcement.  When the headers arrive, the message will be of maximum
size and so a follow-up request will be sent---all of that in addition
to the existing headers syncing.  This will create a second "chain" of
getheaders requests.  If more blocks arrive, this may even lead to
arbitrarily many parallel chains of redundant requests.

This patch changes the behaviour to only request more headers after a
maximum-sized message when it contained at least one unknown header.
This avoids sustaining parallel chains of redundant requests.

Note that this patch avoids the issues raised in the discussion of
https://github.com/bitcoin/bitcoin/pull/6821:  There is no risk of the
node being permanently blocked.  At the latest when a new block arrives
this will trigger a new getheaders request and restart syncing.

Compare the block download timeout to what the timeout would be if calculated
based on current time and current value of nQueuedValidatedHeaders, but
ignoring other in-flight blocks from the same peer. If the calculation based on
present conditions is shorter, then set that to be the time after which we
disconnect the peer for not delivering this block.

SendMessages will now call getheaders on both inbound and outbound peers,
once the headers chain is close to synced.  It will also try downloading
blocks from inbound peers once we're out of initial block download (so
inbound peers will participate in parallel block fetching for the last day
or two of blocks being downloaded).

Not used, and REGTEST already allows creating blocks at
the lowerst possible difficulty.

It shouldn't know or care about bitcoind's chain param selection

Also add conversion from/to uint256 where needed.

Replace x=0 with .SetNull(),
x==0 with IsNull(), x!=0 with !IsNull().
Replace uses of uint256(0) with uint256().

Lower block reward by 10% increase throne reward by 5%. Both miners and thrones receive equal payments now


Former-commit-id: 9a5ad2c1ad8f84677de149234bfa23aeb5e5fe1c

change dash-tx -> crown-tx

change dash-config.h

change das
h- -> crown-

change dashrpc->crownrpc

change dash_qt -> crown_qt

change dash_cli -> crown_cli

chang
e dash_tx -> crown_tx

change test_dash -> test_crown


Former-commit-id: f22ef63258e4b6b7ae790be64ba079162262415f

Former-commit-id: 7bd564e7406d6b0a4d65689248fd82d8d358c822

Former-commit-id: baf86891f001bb428dc335c81b201151c9274b15

Former-commit-id: 538ea1fd3eb6ef70ce75be987134173cad0eb75c

Former-commit-id: 5347d237910da79e5da8961f3c6e4d5bc9589b49

Former-commit-id: ec56b0a1d855649c5e0d920b89ce69293b99c25d

Former-commit-id: e8fe5b96b617c98f07abf8d0b34c889016778b57

Former-commit-id: 4cfe88e5323e952c926652f4db03f1ad5f8305a0

Former-commit-id: 66f0baa03b21f972e974b89cd89890568043f2a7

https://github.com/bitcoin/bitcoin/pull/6931
BIP-0034 should've been active by the time crown started.
PLEASE TEST.

https://github.com/bitcoin/bitcoin/pull/6931
BIP-0034 should've been active by the time crown started.
PLEASE TEST.
Former-commit-id: c765f367e2e3323e413f3a2ed0f68017419156a0

Former-commit-id: 27ea40292b1061972f3742eaf9191703cc4b0e16

Former-commit-id: 88e56abad7e5780aafecb4b05fbb5b38732f010f

Former-commit-id: 0b81c6f358edd56ccd4919318f36659b99410fc0