can use this ?
--plot.folder=D:\plots --plot.folder=E:\plots
Topic: [ANN] [BURST] Burst Mining System - A new miner for BurstCoin - page 3. (Read 32163 times)
September 07, 2014, 11:23:20 PM
September 07, 2014, 10:29:42 PM
Ok. I recompiled with the revised version and now it works. The compiled version you pointed to does not want to work.
Did you try with the 1.11 release jar. It should be the same code as the master branch now.
Let me know if you see any issues with the official pool, I haven't had much time to test with that one yet.
Was the first thing to do but it does not work. I put the flag for the official pool but it was asking for mining info using the URL structure from Urays pool.
Then I compiled from master, and it works without problems.
Was the first jar you linked to 1.1 or 1.11?
I think it was 1.1 i first linked to. My release management wasn't very good at the beginning.. sorry
Make sure you are at least using 1.12 now to make sure you get the credit for your shares, and minimize the penalties.
September 07, 2014, 10:11:17 PM
Sorry everyone... new release to use if you want a working System Dashboard. In my rush to get the shares fix out, I forgot about some in-progress code that broke the System Dashboard. 1.12 will still mine just fine, but you probably wont have a working system dashboard. Release 1.13 fixes this
https://github.com/mrpsion/burst-mining-system/releases/tag/1.13
https://github.com/mrpsion/burst-mining-system/releases/tag/1.13
September 07, 2014, 09:54:01 PM
Ok. I recompiled with the revised version and now it works. The compiled version you pointed to does not want to work.
Did you try with the 1.11 release jar. It should be the same code as the master branch now.
Let me know if you see any issues with the official pool, I haven't had much time to test with that one yet.
Was the first thing to do but it does not work. I put the flag for the official pool but it was asking for mining info using the URL structure from Urays pool.
Then I compiled from master, and it works without problems.
Was the first jar you linked to 1.1 or 1.11?
September 07, 2014, 09:48:33 PM
Quote
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.
^from http://burst-pool.cryptoport.io/howitwork.htmlUm just to let you know when using http://burst-pool.cryptoport.io/ you will be penalized for using this client as it spams lots of high deadline submits which I have noticed from looking at my score decrease on the site pretty quickly
Miner looks great and stats and feedback is really cool but this needs to be fixed, also if you could make a window in the gui that contains the logs that runs through the command line that would be stellar
Also if you put a donation address in your sig and make mentioned fixes and changes I am sure plenty of happy miners would be willing to contribute
Okay all fixed. I added a new release 1.12 that fixes this issue. Everyone should use this version.
September 07, 2014, 08:18:18 PM
Quote
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.
^from http://burst-pool.cryptoport.io/howitwork.htmlUm just to let you know when using http://burst-pool.cryptoport.io/ you will be penalized for using this client as it spams lots of high deadline submits which I have noticed from looking at my score decrease on the site pretty quickly
Miner looks great and stats and feedback is really cool but this needs to be fixed, also if you could make a window in the gui that contains the logs that runs through the command line that would be stellar
Also if you put a donation address in your sig and make mentioned fixes and changes I am sure plenty of happy miners would be willing to contribute
I just PM'd Uray about this, as I think his client will do this as well, unless i am reading it all wrong. Ill put some time into this tonight, but I am thinking that I should just submit 1 share per miner per block to minimize the penalty.
The donation addresses are at the bottom of the web UI and the readme i think... i didn't want to make it too obvious
September 07, 2014, 06:18:25 PM
Quote
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.
^from http://burst-pool.cryptoport.io/howitwork.htmlUm just to let you know when using http://burst-pool.cryptoport.io/ you will be penalized for using this client as it spams lots of high deadline submits which I have noticed from looking at my score decrease on the site pretty quickly
Miner looks great and stats and feedback is really cool but this needs to be fixed, also if you could make a window in the gui that contains the logs that runs through the command line that would be stellar
Also if you put a donation address in your sig and make mentioned fixes and changes I am sure plenty of happy miners would be willing to contribute
September 07, 2014, 04:53:17 PM
Thanks for putting some development effort into a new miner for BURST.. I'm sure there are tons of optimizations possible at this stage still.
September 07, 2014, 04:23:10 PM
do you plan also a miner for solo ?
Yeah I started adding in the code for solo... its basically the same as Uray, with some passphrase work. Not sure when Ill get it out, but It is in the plan.
September 07, 2014, 02:40:52 PM
do you plan also a miner for solo ?
September 07, 2014, 02:28:36 PM
looks like im still a noob on this can i get a "how to" on ubuntu 14.04 ?
Thanks
EDIT : on v2 pool i want to mine http://burst-pool.cryptoport.io/
Thanks
EDIT : on v2 pool i want to mine http://burst-pool.cryptoport.io/
September 07, 2014, 01:31:40 PM
Ok. I recompiled with the revised version and now it works. The compiled version you pointed to does not want to work.
Did you try with the 1.11 release jar. It should be the same code as the master branch now.
Let me know if you see any issues with the official pool, I haven't had much time to test with that one yet.
September 07, 2014, 01:09:26 PM
will this work mining on http://burst-pool.cryptoport.io/ ?
Yes. You just need to tell it to do so. In the readme you will find everything you need
ok thankyou ill take a look now
September 07, 2014, 01:02:19 PM
will this work mining on http://burst-pool.cryptoport.io/ ?
Yes. You just need to tell it to do so. In the readme you will find everything you need
September 07, 2014, 12:44:28 PM
will this work mining on http://burst-pool.cryptoport.io/ ?
September 07, 2014, 05:09:25 AM
Ok. I recompiled with the revised version and now it works. The compiled version you pointed to does not want to work.
September 07, 2014, 04:52:50 AM
Hi all,
If you are using this, please immediately download release 1.11
It fixes a major bug in deadline calculation. i.e. your will actually get some credit for your shares now.
https://github.com/mrpsion/burst-mining-system/releases/tag/1.11
I had to bang my head on a wall a couple of times when i spotted it. (It was an offset issue, which I hadn't spotted as all my testing has been against a test network that I reset, so my first share is always in the first MiningPlot... doh)
If you are using this, please immediately download release 1.11
It fixes a major bug in deadline calculation. i.e. your will actually get some credit for your shares now.
https://github.com/mrpsion/burst-mining-system/releases/tag/1.11
I had to bang my head on a wall a couple of times when i spotted it. (It was an offset issue, which I hadn't spotted as all my testing has been against a test network that I reset, so my first share is always in the first MiningPlot... doh)
I've set the flag to mine with the official pool and it keep telling me that it can't find mining info and giving the link structure from Urays pool.
September 07, 2014, 12:11:43 AM
Hi all,
If you are using this, please immediately download release 1.11
It fixes a major bug in deadline calculation. i.e. your will actually get some credit for your shares now.
https://github.com/mrpsion/burst-mining-system/releases/tag/1.11
I had to bang my head on a wall a couple of times when i spotted it. (It was an offset issue, which I hadn't spotted as all my testing has been against a test network that I reset, so my first share is always in the first MiningPlot... doh)
If you are using this, please immediately download release 1.11
It fixes a major bug in deadline calculation. i.e. your will actually get some credit for your shares now.
https://github.com/mrpsion/burst-mining-system/releases/tag/1.11
I had to bang my head on a wall a couple of times when i spotted it. (It was an offset issue, which I hadn't spotted as all my testing has been against a test network that I reset, so my first share is always in the first MiningPlot... doh)
thanks for the good work
September 06, 2014, 09:51:34 PM
Hi all,
If you are using this, please immediately download release 1.11
It fixes a major bug in deadline calculation. i.e. your will actually get some credit for your shares now.
https://github.com/mrpsion/burst-mining-system/releases/tag/1.11
I had to bang my head on a wall a couple of times when i spotted it. (It was an offset issue, which I hadn't spotted as all my testing has been against a test network that I reset, so my first share is always in the first MiningPlot... doh)
If you are using this, please immediately download release 1.11
It fixes a major bug in deadline calculation. i.e. your will actually get some credit for your shares now.
https://github.com/mrpsion/burst-mining-system/releases/tag/1.11
I had to bang my head on a wall a couple of times when i spotted it. (It was an offset issue, which I hadn't spotted as all my testing has been against a test network that I reset, so my first share is always in the first MiningPlot... doh)
September 06, 2014, 09:07:35 PM
Ok. I started 3 miners. 1 master and 2 slaves.
The slaves are working ok. The master is reporting that mining for block has finished. But its the same block over and over again
On the dashboard it displays the correct block and the generating hash. Also reporting how many time a plot was searched.
Is it something bad or does it run even with these problems?
edit: the plot file used by the master isn't finished yet if it matters
Also, mining official v2 pool. Not Urays pool
The slaves are working ok. The master is reporting that mining for block has finished. But its the same block over and over again
Code:
2014-09-07 04:08:52.499 INFO 3953 --- [taskScheduler-2] ish.burst.ms.services.MiningService : Stopped mining {f4eb42d8-d1e4-3676-8a3f-5f9879758ca6} due to block change.
2014-09-07 04:08:52.500 INFO 3953 --- [taskScheduler-2] ish.burst.ms.services.NetStateService : Could not fetch block data from pool
On the dashboard it displays the correct block and the generating hash. Also reporting how many time a plot was searched.
Is it something bad or does it run even with these problems?
edit: the plot file used by the master isn't finished yet if it matters
Also, mining official v2 pool. Not Urays pool
So the {f4eb42d8-d1e4-3676-8a3f-5f9879758ca6} is the plot file id that lines up with the UUID you see in the UI... in hindsight i probably should have just left its representation as the usual address_noncestart_number_stagger id.
If a new block is announced before it has finished scanning the plot it will tell you it stopping mining the plot.
The pool situation is a bit of a mess. Urays pool actually uses a completely different api and mining methodology, so currently the v1.1 jar only will mine urays. I am putting in some code to try and detect between the two types of pool, and switch mining modes accordingly. If you had built from source earlier today its probably running the official pool version code I had in there, but after some testing i found that it might not actually be getting any shares accepted by the pool, even if the pool is returning the success message, so I pulled that code, and left in Urays, which actually tells you if you are being rejected.
The burst pool scene is a little chaotic at the moment, so I hope everyone bears with the community as we all try and adjust.
Jump to: