Native Burst miner [OSX] [Win] [Linux]

[uray]

download binary here https://github.com/uraymeiviar/burst-miner/releases
source code is here https://github.com/uraymeiviar/burst-miner/
website is here http://uraymeiviar.github.io/burst-miner/

to configure, just edit mining.conf file in packaged bin, app will automatically look for this file when run, unless you specify costom .conf file

this is for burst pool v2 mining only
miner will use 2x staggerSize x 64 byte per plot file

• it use C++ and native compiled, should be faster and less memory consumption compared to java miner
• binary available for osx, win64 and linux64 (on linux most of the case you still need to recompile it, to do this clone source from github and issue "make" command
• multithreaded miner, it will keep reading without pause when submiting share
• added random delay when submitting nonce, to ensure you dont submitting nonce during peak submission on pool
• it will auto retry if nonce submission is failed
• multi account, multi-plots, just configure path to plot or directory inside mining.conf, it will autmatically search for valid plot file, dont worry if have another file inside plot directory, it wont read it

[uray]

New Native C++ Miner Update 1.1 R4

binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64

• capable to read large stagger plot, with manual limit option on memory usage
• Fix thread race condition, which reported to less nonce read
• add option of buffer size (MB) in mining.conf to limit memory usage

[tex81]

Would be great to change to single PlotReading thread per path (hdd). Now it reads all files at the same time, exploding HDD

[tex81]

... and single user`s acc status page with his shares, payouts, etc, eg http://burst-pool.cryptoport.io/acc/12471376074470458574

[chey]

Getting very high deadlines using the miner.

{"result": "success","deadline": 591396439290,"targetDeadline": 591396439290}

I'm submitting shares and getting payouts though. The deadline carries through to the pool as it shows up in "years".

I'm using http://pool.burstcoin.io/ and it's showing 9000+ years

This doesn't seem right. How can I fix it?

[brizio71]

New Native C++ Miner Update 1.1 R4

binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64

• capable to read large stagger plot, with manual limit option on memory usage
• Fix thread race condition, which reported to less nonce read
• add option of buffer size (MB) in mining.conf to limit memory usage

I'm using the latest version of your Burst Miner 1.1 R4 on Linux,
there is a particular configuration or option to put on mining.conf file in order to know
how many seconds it took to read a folder of plots ?

Thanks

Fabrizio

[jaggard]

Is it possible for you to get this stable on windows? Or, for that matter, to quit looping on share submissions that are ridiculously high deadlines (as in millennia) so that it keeps eating share values since I'm mining on a pool that uses your source when it does it? On this machine, an Intel I5-2500k, it's more stable than the other one, but when it crashes here, the cmd window just disappears. On my AMD FX8320, it crashes sometimes 10 times a day with the wonderful check online for a solution bs window. As it is right now, I think I'd be doing better to be running the java miner on each plot dir/drive rather than dealing with this mess...

Code:

confirmed dl. for 7VA8-N2KU-CJEL-23WPY : 64 days 16:27:30
7VA8-N2KU-CJEL-23WPY dl:0 days 13:49:19 n:16324922
plot read done. 1105494758335376646_15555474_2515968_2515968 = 2672640 nonces
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
plot read done. 1105494758335376646_388800000_7547904_24192 = 7572096 nonces
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
plot read done. 1105494758335376646_10644491_967680_967680 = 1148928 nonces
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY
{"result":"success","deadline":1256214657110}
plot read done. 1105494758335376646_12870157_1257984_1257984 = 1467392 nonces
plot read done. 1105494758335376646_11612172_1257984_1257984 = 1467392 nonces
submitting nonce 16324922 for 7VA8-N2KU-CJEL-23WPY

[LVB]

I am using this miner (R4) with great results on the burst.ga pool.

However, when I tried to solo mine without a pool, I get the same high deadlines reported back from my wallet as reported above by chey.  More precisely, the miner finds good deadlines but when it submits them to the wallet, the wallet reports back a very high value.

[jaggard]

yes, this is what can be seen looking in the codebox i submitted also, although it's doing it on a pool. I haven't tried solo with this miner.

I am using this miner (R4) with great results on the burst.ga pool.

However, when I tried to solo mine without a pool, I get the same high deadlines reported back from my wallet as reported above by chey.  More precisely, the miner finds good deadlines but when it submits them to the wallet, the wallet reports back a very high value.

[BazzaBoiii]

Just got my miner and wallet set up but now I'm getting this. I'm mining on burst.ga pool.

Code:

submitting nonce 85788 for Z8D3-PNRY-JYZL-CS6MP
{"requestProcessingTime":0,"result":"Passphrase does not match reward recipient"

[LVB]

"Passphrase does not match reward recipient"

This is the kind of error you get when you did not assign the pool's burst address as the reward recipient, through the rewardassignment.html page of your wallet. Once you have done this, after 4 blockchain confirmations this error will disappear.  For more details, visit the "how to mine" page of your pool.

[BazzaBoiii]

Ahhh I see! I just tried to set it again and it's said the current one is processing I'm just being impatient lol.

 

[Longsnowsm]

I am new to all of this and I am trying to figure out the "for dummies version" of how to install the wallet for Burst on the Mac.  Can anyone point me to a resource to help me get started with Burst on the Mac?  I just downloaded the miner on my Mac also... And again I think I am having an ID10T issue here... Can someone tell me what the process is to get the miner up and running on the MAC?  Thanks.