cpuminer-gw64-corei7.exe -a cryptonight -o stratum+tcp://minercoin3.duckdns.org:7450 -u btc@1B5GzsvfinUinUE1suxbCw9zhSGc4abzuz -p 7a3dd24b88u4t@rig1 -t 2Windows #76
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
This reverts commit 44a5b3a.
Backport from cpuminer 2.4, commit 30fae0c
to be able to cherry pick remaining v2.4 changes
disabled by default or if syslog option is set Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
Added to compare results with ccminer tool (cuda variant) Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
should be set to 14 for NEOS-blake and pentablake
also ensure blake context was initialised...
Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
unlike timetravel, a fast algo can be used 16 times in theory Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
keccakc is the same as the original keccak, but the previous was using a different (early) stratum protocol and factor. This new implementation use a stratum factor of 256 and a sha256d merkle tree
The expected coinbase for BIP34 blocks is constructed by serialising a script with the block height as integer. In the end, this leads to the code in CScriptNum::serialize in the Bitcoin Core codebase. Specifically, for positive numbers (as in the case of a block height), the rule [1] is that another zero byte has to be pushed in case the last byte had the highest bit set (since that bit is used to indicate the sign). [1] https://github.com/bitcoin/bitcoin/blob/e117cfe45eee9169409e74a44ef4a866be25bc35/src/script/script.h#L351
cleaned up...
phi2 is a new test algo for LUX, may change again if required... cpu hashrate remains almost identical, 230 vs 250 kH/s but gpu speed is slower by a bigger factor. It should be harder to implement on fpgas, and fixes the original algo power issue due to over-optimised heavy gpu code Adding lyra and some other memory ops allow the gpu to breath between heavy algos (gost/echo)
Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
A quick benchmark shows 1795 kH/s on a core i7/4790K at 4000 MHz and 795 kH/s on a Odroid-C2 ARM board at 1752 MHz lacking crypto extensions. Pretty nice for such a small device. (MikeMurdo) It is very impressive on a Raspberry-Pi 3B+, it gives 668 kH/s, or roughly 1/3 of my skylake 4 GHz for 1/30 of the power usage and 1/18 of the price! Test report here : https://www.linkedin.com/pulse/more-efficient-mining-raspberry-pi-julien-delorme . The skylake also outperforms the GPU! (jdelorme3) FWIW I just tested on NanoPI-Fire3 at 8*1.6 GHz and it's way faster (1825 kH/s). Apparently the algo makes use of crypto extensions which are enabled on this board but are not on raspi. It's fun to see a $35 device beat a $500 PC (wtarreau) From https://github.com/bschn2/rainforest
made an error when using intel compiler. compiles fine now.
X20r algo - this is x16r extended with the addition of haval, gost, radioatun and panama + space/tabs cleanup, algo order and missing vstudio files...
Signed-off-by: Tanguy Pruvot <tanguy.pruvot@gmail.com>
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.
No description provided.