| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
|
|
| |
Note that the test address was invalid in Bitcoin Core, and as such rather than
re-encoding as a Dogecoin address, I've simply swapped the first byte. Still
invalid, but looks correct at least.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce a PlatformStyle to handle platform-specific customization of
the UI.
This replaces 'scicon', as well as #ifdefs to determine whether to place
icons on buttons.
The selected PlatformStyle defaults to the platform that the application
was compiled on, but can be overridden from the command line with
`-uiplatform=<x>`.
Also fixes the warning from #6328.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
* Cleanup SVG code
* Unify design ("Typicons" seem to have round edges)
* Fix transparency issue with clock5.png
|
| |
|
|
|
| |
Update QT client messages and translations to Doge equivalents. Where specific contributions
were made in languages for Dogecoin, those translations are used in preference.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Make low-s verification mandatory for standard script verification
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change makes a node only accept transactions with low-s
signature encoding for relay and mining, but allows transactions
with high-s signature encoding in mined blocks (no blocks will
be rejected)
Pros:
- If deployed by all miners, this will eliminate this particular
malleability attack.
- There is no impact on consensus
Cons:
- Wallets that do not implement low-s signature encoding will
see their transactions be rejected by growing numbers of peers
and ultimately not be able to get any transaction mined.
Follow ups:
- Eventually, this verification needs to be confirmed through a
consensus rule (enforcement of BIP62)
|
| | |
| |
| |
| |
| | |
Displays NODE_BLOOM service as "BLOOM" instead of "UNKNOWN[2]"
in qt->debug->peers
|
| | |
| |
| |
| |
| | |
Marked as deprecated but still used in many pool implementations,
as well as rpc-tests. This restores AuxPoW compatibility to 100%.
|
| |/
|
|
|
|
|
|
|
| |
Contains:
0cca0248f030ea32bd8de778b5a2782e0d191978
9f3e48e5219a09b5ddfd6883d1f0498910eff4b6
888c595cffe73b0d49434acf49a9611cbff1ea1d
00c5a73136e13813219c7b0846fa1bfd91757e5d
|
| |\
| |
| | |
Update block height used to determine relevant parameters
|
| | | |
|
| | |
| |
| |
| |
| | |
Purge all support for zero-fee transactions
Disable IsDust() for backwards compatibility
|
| |\ \
| | |
| | | |
Update testnet checkpoints and remove old seed
|
| | |/ |
|
| |\ \
| | |
| | | |
Corrected missing new lines in error messages
|
| | |/ |
|
| |\ \
| |/
|/| |
Add NODE_BLOOM service bit
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Lets nodes advertise that they offer bloom filter support explicitly.
The protocol version bump allows SPV nodes to assume that NODE_BLOOM is
set if NODE_NETWORK is set for pre-70002 nodes.
Also adds an undocumented option to turn bloom filter support off for
testing purposes. Nodes attempting to use bloom filters are immediately
dropped so as to not waste their bandwidth.
ensure backward compatible service bits
update protocol version to 70004
|
| |\ \
| | |
| | | |
[auxpow] Check for auxpow fork strictly
|
| | |/
| |
| |
| |
| |
| | |
Disallow any auxpow block before the blockheight where auxpow gets enabled.
For consistency, this also re-enables legacy headers on regtest.
|
| |/
|
|
|
| |
Adds a wrapper around getauxblock to return boolean responses
for getauxblock rather than bip22 responses.
|
| | |
|
| |\
| |
| | |
Update fork detection parameters for Dogecoin block time
|
| | |
| |
| |
| |
| |
| | |
I've multiplied fork detection parameters by 5 - the wall clock time elapsed for "long" forks
is therefore half that of Bitcoin, but IMHO those figures are excessive for a chain with 1
minute block times.
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Disable payment protocol certificate unit tests
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Disable payment protocol certificate unit tests; we don't modify this code,
and regenerating the test data is likely to be significantly time consuming.
Will re-enable once discussion on spec is concluded.
|
| |\ \ \
| | | |
| | | | |
Re-enable SuperMajority triggered activation for v2 block constraints
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Start validating v2 blocks when there is a v3 supermajority, because
v2 clients (1.5->1.8) had supermajority checks disabled.
This is needed for future-proofing, so that a currently accepted,
but invalid v2 block will also be accepted on newer nodes.
|
| | |/ /
|/| |
| | |
| | |
| | | |
BIP16 and BIP30 have both been enabled on Dogecoin since inception
and should not be conditional.
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | | |
changing CAmount (is a int64_t) to arith_uint256 for nTotalAmount
|
| | | |
| | |
| | |
| | | |
CCoinsStats to prevent overflow
|
| |\ \ \
| | | |
| | | | |
Revised payment request handling to use genesis block hash
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
network name
Revised payment request handling to use genesis block hash instead of network name, enabling
support for more networks that just Bitcoin main and test net.
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This updated various time-based constants to more closely reflect values
appropriate to Dogecoin:
* Number of blocks to look back for BIP 66 enforcement is doubled on
main net (to about a day and a half's worth, vs 5 days on Bitcoin),
and raised to 1,000 on testnet (bringing it up to the same quantity
as Bitcoin testnet).
* BIP 66 enforcement cut-offs are scaled up appropriate.
* Minimum number of blocks and blockchain size are increased for
pruning. In comparison to Bitcoin this uses 24 hours as a minimum,
rather than 48, although given blocks are rarely full this likely
reflects a lot longer in reality.
|
| |/ / |
|