burstcoin-jminer-0.5.0-SNAPSHOT
Pre-release| burstcoin-jminer-0.5.0-SNAPSHOT.zip | |
|---|---|
| OS | Windows (32/64bit), Linux (64bit), MacOS (64bit) |
| Download | burstcoin-jminer-0.5.0-SNAPSHOT.zip |
| Setup | https://github.com/de-luxe/burstcoin-jminer/blob/master/README.md |
| MD5 | de4905e19dd50456a68ac87ce4213179 |
| SHA-1 | 9ee6dcbc6f935d9b434ec0d41615e70dc86d1950 |
| SHA-256 | aa82b8a98c5d14a69bcdb79274f27610bc9c1f51ce6fa3335afb212bf1d5578d |
Notice:
With this version, jminer supports both POC1 and POC2 plotfiles. This will also be the case after the fork.
However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used. The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork. I hope to make the switch from POC1 to POC2 as smooth as possible for users of jminer, like myself.
Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped.
Ensure your POC2 plotfiles do not have staggersize in filename, or they will be treated like POC1.
Read speed is calculated by plotsize, so if jminer reads twice the data on e.g. POC2 pre-fork, the numbers displayed will not be accurate.
Ensure to use Java8 (in command line java -version) Java9 will cause issues for now!
Updates:
- #64 support for POC2 plotfiles (will read twice the data pre-fork)
- some cleanup and optimize, update to latest lib versions
For a QUICKSTART check README
https://github.com/de-luxe/burstcoin-jminer/blob/master/README.md