ADD verushash2.2 #1863
Open
ADD verushash2.2 #1863
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While limitations on the influence of attackers on addrman already exist (affected buckets are restricted to a subset based on incoming IP / network group), there is no reason to permit them to let them feed us addresses at more than a multiple of the normal network rate. This commit introduces a "token bucket" rate limiter for the processing of addresses in incoming ADDR and ADDRV2 messages. Every connection gets an associated token bucket. Processing an address in an ADDR or ADDRV2 message from non-whitelisted peers consumes a token from the bucket. If the bucket is empty, the address is ignored (it is not forwarded or processed). The token counter increases at a rate of 0.1 tokens per second, and will accrue up to a maximum of 1000 tokens (the maximum we accept in a single ADDR or ADDRV2). When a GETADDR is sent to a peer, it immediately gets 1000 additional tokens, as we actively desire many addresses from such peers (this may temporarily cause the token count to exceed 1000). The rate limit of 0.1 addr/s was chosen based on observation of honest nodes on the network. Activity in general from most nodes is either 0, or up to a maximum around 0.025 addr/s for recent Bitcoin Core nodes. A few (self-identified, through subver) crawler nodes occasionally exceed 0.1 addr/s. Backport of: - zcash@7c739e2 - bitcoin/bitcoin@0d64b8f
Back-merge hotfixes to dev
rust: speed up build by disabling rust docs
https://github.com/KomodoPlatform/kips/blob/main/kip-0001.mediawiki TODO: don't forget to change 7113400 to nS7HardforkHeight, after date of S7 HF will be determined.
error handling improvements + get rid of consistency checks
remove debug sleep on darwin platform
… into patch-kip-0001
Add S7 pubkeys and HF estimate
reduce AUR 5% -> 0.01% after nS7HardforkHeight
In the real KMD chain (not in the first blocks), block.nBits will always be greater than KOMODO_MINDIFF_NBITS. Therefore, the control will never enter this conditional statement. Also "fee stealing" is impossible, since we have notary proof tx (last tx in notary mined block).
For some reason, we were not allowed to have additional vouts in the coinbase transaction if their total was greater than 0.1 KMD. Therefore, a coinbase transaction with 2.8 KMD in vout[0] and 0.2 KMD in vout[1] was forbidden. Since this release, we are allowing such transactions. We are not using height activation here to keep the code simple; instead, we have just removed the restriction itself.
allow -ac_private for the ZOMBIE test chain
error: integer value -1 is outside the valid range of values [0, 3] for this enumeration type - https://trac.macports.org/ticket/69103 - boostorg/numeric_conversion@50a1eae
…rm64) try launch build on x86_64-apple-darwin host instead of arm-apple-darwin - actions/runner-images#9741 - https://github.com/actions/runner-images?tab=readme-ov-file#available-images
Remove libsnark, libgmp, mini-gmp
Allow on demand publishing to dockerhub
build: use native clang as darwin compiler
fix datacarrier related command-line args
Add Season 8 pubkeys and update hardfork constants
bump version [0.9.0]
The KIP0003 consensus rule was added in the `dev` branch as "logging only", i.e. as disabled. However, in the `patch-s8-prepare-hf-test` branch, which we used for testing on hfnet, it's already enabled (as seen in [this commit](783fc1f)). For the release, we should enable this rule and make the logging optional using the hfnet category.
enable KIP0003 consensus rule
v0.9.0 [Drogon]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ac_algo parameter changes the chain's mining algorithm from the default equihash to the verushash.
To enable this feature, set -ac_algo=verushash.
This activates verushash1.0. More recent versions of verushash are not yet supported.
The verushash feature serves as a proof of concept for adding support for additional mining algorithms.
The Komodo team is currently testing methods to support compatibility for ac_staked, but this feature is not yet recommended for external testing.
I have a question for the project team how soon will verushash2.2 support be implemented?