There's now a Windows wallet available:
https://github.com/dawallet/burstwindowswallet
or
https://sourceforge.net/projects/burstwindowswallet/
Goal is to include 1-click plotter and miner in the next 2 months...
Topic: [ANN] [BURST] Burst Mining System - A new miner for BurstCoin (Read 32163 times)
Any news on this for been updated to work on windows 8 preferable a built exe to install
November 03, 2014, 08:36:30 PM
Is their a windows version of this yet compiled and ready to configure and mine with?
miner mines a few times then it stops untill new block found
then a few line of mining again and then stops again
very low share or sometimes no share submiting
what is wrong
java ver 8 installed
I hoped for an easy to use GUI.
iam starring at folders with no clue what to do.not remotely.
Now after skipping through all the threads,i still cant get a cmd line together.
Would somebody please give me a cmd line with x y variables ?
Page 29 in the ANN thread was a frustrating read through.i barely got that you use ur HDD to mine
(shame on me)
Help much appreciated already
iam starring at folders with no clue what to do.not remotely.
Now after skipping through all the threads,i still cant get a cmd line together.
Would somebody please give me a cmd line with x y variables ?
Page 29 in the ANN thread was a frustrating read through.i barely got that you use ur HDD to mine
(shame on me)Help much appreciated already
Hello
having problem with submitted shares , miner shows shares being submited, offical v2 pool shows nothing.
Mining with 8,6 TB got 0 on over 3 days altho miner shows a lot of shares. What can cause this?
having problem with submitted shares , miner shows shares being submited, offical v2 pool shows nothing.
Mining with 8,6 TB got 0 on over 3 days altho miner shows a lot of shares. What can cause this?
I am still getting quite a few interrupts on some of my miners using BMS, even though the plots are optimized and are locally attached. Also, it is not uncommon for my miners 'Time Since Last Share' to be for hours. This can't be good, correct?
Sorry for the poor formatting but below is an example. Sadly, this is probably one of my better situations...
Miner
Uptime - local 0 Days : 8 Hours : 14 Minutes : 31 Seconds
Time Since Last Share - 0 Days : 5 Hours : 3 Minutes : 39 Seconds
Mining Stats
Plot | File Size (Gb) | Expected Size (Gb) | Shares | Times Mined | Times Interrupted
f5e9e2a9-0de2-3800-b105-124ea1fb321d | 256.25 | 256.25 | 50 | 127 | 16
3c13b980-8ed9-3675-82d0-253184d2f025 256.25 256.25 29 127 16
c0bdf19d-f17b-3543-89ff-79e114bba76b 256.25 256.25 17 125 18
56c08d68-007c-3d87-bafc-79f59a39c3b0 256.25 256.25 10 124 19
27a76dbd-3947-34b4-914f-3b9a5b536edb 256.25 256.25 7 123 20
82bde6b9-7970-3be1-bf69-5059fb209285 256.25 256.25 5 116 27
7abc71a8-98be-3ac5-9053-ff581ee491bf 256.25 256.25 6 112 31
Totals 1793.75 1793.75 124 854 147
Sorry for the poor formatting but below is an example. Sadly, this is probably one of my better situations...
Miner
Uptime - local 0 Days : 8 Hours : 14 Minutes : 31 Seconds
Time Since Last Share - 0 Days : 5 Hours : 3 Minutes : 39 Seconds
Mining Stats
Plot | File Size (Gb) | Expected Size (Gb) | Shares | Times Mined | Times Interrupted
f5e9e2a9-0de2-3800-b105-124ea1fb321d | 256.25 | 256.25 | 50 | 127 | 16
3c13b980-8ed9-3675-82d0-253184d2f025 256.25 256.25 29 127 16
c0bdf19d-f17b-3543-89ff-79e114bba76b 256.25 256.25 17 125 18
56c08d68-007c-3d87-bafc-79f59a39c3b0 256.25 256.25 10 124 19
27a76dbd-3947-34b4-914f-3b9a5b536edb 256.25 256.25 7 123 20
82bde6b9-7970-3be1-bf69-5059fb209285 256.25 256.25 5 116 27
7abc71a8-98be-3ac5-9053-ff581ee491bf 256.25 256.25 6 112 31
Totals 1793.75 1793.75 124 854 147
September 22, 2014, 11:27:58 PM
how to use plots with 2 hdds???
gui only shows 1 hdd
i can link them and use them but still shows 1 hdd on dashbord
gui only shows 1 hdd
i can link them and use them but still shows 1 hdd on dashbord
Currently you will need to use 2 miners... just start them on different ports
September 20, 2014, 02:13:12 PM
how to use plots with 2 hdds???
gui only shows 1 hdd
i can link them and use them but still shows 1 hdd on dashbord
gui only shows 1 hdd
i can link them and use them but still shows 1 hdd on dashbord
September 19, 2014, 04:12:56 PM
Can someone write step by step instructions for how to run on Ubuntu.
Thanks
Thanks
September 17, 2014, 10:02:27 AM
So how many coins per day can one get with 1TB currently?
About 1000
There is a little tool out there that calculates this... somehow
https://bchain.info/BURST/tools/calculator
1000? on which pool?
September 14, 2014, 07:17:04 PM
My BMS dashboard shows a negative number for the address on my plot. Is that normal?
Edit: I guess it's not normal since it got me banned on http://burst-pool.cryptoport.io/ which worked just fine for me with the v2 miner.
Edit: I guess it's not normal since it got me banned on http://burst-pool.cryptoport.io/ which worked just fine for me with the v2 miner.
Interesting... could you PM me a screen shot of the BMS dashboard an possible a screen shot of a directory listing with the plot... I am wondering if there is something wrong with the way I am loading the address from the filename as an unsigned long.
Or you can add and issue to the GitHub page with screenshots etc.
Also what OS are you using?
September 14, 2014, 09:57:12 AM
My BMS dashboard shows a negative number for the address on my plot. Is that normal?
Edit: I guess it's not normal since it got me banned on http://burst-pool.cryptoport.io/ which worked just fine for me with the v2 miner.
Edit: I guess it's not normal since it got me banned on http://burst-pool.cryptoport.io/ which worked just fine for me with the v2 miner.
September 12, 2014, 06:37:11 AM
what arguments do i use to start this up?
Take a look at the readme on github, https://github.com/mrpsion/burst-mining-system. but basically its just
java -jar mining-system-1.20.jar --pool.url=http://{pool.hostname}:{pool.port} --plot.generation.threads=2
or something similar
September 12, 2014, 02:56:27 AM
I am new to this. I am really confused. I downloaded the gui miner on windows how do I run it now? I do have the jvm installed.
September 11, 2014, 09:23:39 PM
what arguments do i use to start this up?
September 11, 2014, 01:06:46 PM
Is there a way to set something on the remote miners running this to report back to the master miner that oversees them all?
Finding exactly what IP each one actually finds to can be troublesome, but I'm being picky/lazy.
Finding exactly what IP each one actually finds to can be troublesome, but I'm being picky/lazy.
I could, and I was thinking about something like this, but I too was lazy when trying to roll out the miner
. The question I have for the group is what style of auto discovery would we want? i.e. do most people run their miners on networks that have multicast enabled across all the switches and hubs etc? or would we just want to instead of listing all the nodes on the masters start-up command, just list the master node on every other nodes start-up command?Perhaps a config file or command line argument on each remote node that would cause it to connect to a certain master node.
Same way it currently works where the master lists each remote node, but reversed
each remote node lists the master it connects to. September 11, 2014, 08:55:21 AM
Is there a way to set something on the remote miners running this to report back to the master miner that oversees them all?
Finding exactly what IP each one actually finds to can be troublesome, but I'm being picky/lazy.
Finding exactly what IP each one actually finds to can be troublesome, but I'm being picky/lazy.
I could, and I was thinking about something like this, but I too was lazy when trying to roll out the miner
. The question I have for the group is what style of auto discovery would we want? i.e. do most people run their miners on networks that have multicast enabled across all the switches and hubs etc? or would we just want to instead of listing all the nodes on the masters start-up command, just list the master node on every other nodes start-up command? September 11, 2014, 08:49:14 AM
BTW how is the uray deadline limiting handled cause from my brief look over at the github it looks like you cant submit things that are lower than your lowest deadline submitted, which while fair from a pool manager perspective the vast majority of other miners are submitting lots of low deadlines that aren't necessarily all lower than their current lowest but regardless of this it positively affects their score. Point being that you should either just slowly scale the threshold or simply use the algo provided by the site to calculate if the share should be uploaded
Quote
deadline value from miner is converted into share value using this equation
share = 1000 / ( NetDiff * Deadline + 1 ) 0.75
where NetDiff (network difficulty) is calculated by Block0-BaseTarget / Block#N-BaseTarget
note : to prevent user spamming low share, we implement share penalty of -0.001 on each submission for miners who submit nonce that has higher deadline than their (current round) own best deadline, as spamming low share is no use since pool will always pick one best deadline for every submitted nonce per round.
IE if your value isn't greater than 0.001 it definetly shouldnt be uploaded but something more reasonable would be to simply assume the -0.001 is in effect and not allow shares that would be worth less than 0.01 safely preventing scores from being lowered and slowly increasing the necessary deadline as needed share = 1000 / ( NetDiff * Deadline + 1 ) 0.75
where NetDiff (network difficulty) is calculated by Block0-BaseTarget / Block#N-BaseTarget
note : to prevent user spamming low share, we implement share penalty of -0.001 on each submission for miners who submit nonce that has higher deadline than their (current round) own best deadline, as spamming low share is no use since pool will always pick one best deadline for every submitted nonce per round.
on urays pool according to Uray, who i pm'd on something similar, only your best share is actually used. the penalty is to stop people trying exactly what you suggest, just to try and preserve system resources on the pool.
So if you first submit a deadline of 1000000, that's what you will get credit for initially, however if you then submit 10000 you will instead get credit for that one and so on... its not cumulative. If then after the 10000 you submitted 10001 you would get a penalty for this. So if you have multiple miners you will get some penalties as the miners don't know about the other shares the other miners have submitted, but it would be minimal, and you would just get credit for the best share submitted across all of your miners that use the same address.
September 11, 2014, 12:14:36 AM
BTW how is the uray deadline limiting handled cause from my brief look over at the github it looks like you cant submit things that are lower than your lowest deadline submitted, which while fair from a pool manager perspective the vast majority of other miners are submitting lots of low deadlines that aren't necessarily all lower than their current lowest but regardless of this it positively affects their score. Point being that you should either just slowly scale the threshold or simply use the algo provided by the site to calculate if the share should be uploaded
Quote
deadline value from miner is converted into share value using this equation
share = 1000 / ( NetDiff * Deadline + 1 ) 0.75
where NetDiff (network difficulty) is calculated by Block0-BaseTarget / Block#N-BaseTarget
note : to prevent user spamming low share, we implement share penalty of -0.001 on each submission for miners who submit nonce that has higher deadline than their (current round) own best deadline, as spamming low share is no use since pool will always pick one best deadline for every submitted nonce per round.
IE if your value isn't greater than 0.001 it definetly shouldnt be uploaded but something more reasonable would be to simply assume the -0.001 is in effect and not allow shares that would be worth less than 0.01 safely preventing scores from being lowered and slowly increasing the necessary deadline as needed share = 1000 / ( NetDiff * Deadline + 1 ) 0.75
where NetDiff (network difficulty) is calculated by Block0-BaseTarget / Block#N-BaseTarget
note : to prevent user spamming low share, we implement share penalty of -0.001 on each submission for miners who submit nonce that has higher deadline than their (current round) own best deadline, as spamming low share is no use since pool will always pick one best deadline for every submitted nonce per round.
Jump to: