[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[Yanakitu Tenatako]

I have one lesser on my burstcoin address, I did not ask anyone for lease or similar.
What should I do?
Is my account still safe?

What do you mean?

This message "1 lessor" is shown after someone unknown sent me this:

4468388687863944900   /   28/02/2015 15:55:16   Balance Leasing      0   1   BURST-FSPB-GG3T-MAH6-37DZ4

Someone leased u some Burst. Just ignore it, it will go away after ages or not ages

The leasing is from PoS, so u can forge with their NXT. U can't spen dthe burst they leased u.

Thank you.
I am not interested in spending smeone else burst, just want to keep mine safe.

Again, thank you.

[ciocgun]

HI,
i got a problem today

i've deleted a buy offer of an asset and got an error.
Some of the amount as returned into my balance, and some not..
what can i do?

[0bert]

Hey guys, is burst.ga down? 

[Mergesort]

Hey guys, is burst.ga down? 

Just use another pool, they got a few things to fix, might take a while or maybe longer who knows.

[0bert]

Hey guys, is burst.ga down? 

Just use another pool, they got a few things to fix, might take a while or maybe longer who knows.

I hope they come back quickly!
Right now i am on pool.burstcoin.io...
Should i use the EU pool or which is better with 3TB? (i am from europe;))

[bobafett]

Now at 48% funded. I still need your help!



If you want how to install the crowdfund extension, loot at burstcoin.info Guides.
thx

Update and News:
www.burstcoin.de

New Feature A Guide for Mining Basics is now available in german at www.burstcoin.de

------

Help me to keep up the page and enhance the information for the german community.

220k to go in the CF. Please do some donations!!!! This is very much work and this will bring us and the price up. So please help to make this a success!

How to donate? look into my sig, open the atcrowdfund.html and pledge for my project.
You can also support me by sending direct to my Burst Account: BURST-AJ63-3W8L-FGBT-2ALZE

Thanks!!!!

[Chesteer]

Can you stop that copy-paste man?
It's boring to see 3 same posts per page...

[seasonw]

Hey guys, is burst.ga down? 

Just use another pool, they got a few things to fix, might take a while or maybe longer who knows.

I hope they come back quickly!
Right now i am on pool.burstcoin.io...
Should i use the EU pool or which is better with 3TB? (i am from europe;))

I don't think EU is good for 3TB. You may check the distribution chart at https://bitcointalk.org/index.php?topic=769473.0. And yet EU has deadline limit.

[lite]

HI,
i got a problem today

i've deleted a buy offer of an asset and got an error.
Some of the amount as returned into my balance, and some not..
what can i do?

do you see any asset balance for which you placed a buy order? i think your buy order got partially filled?

[bobafett]

Can you stop that copy-paste man?
It's boring to see 3 same posts per page...

you have to look at the New feature section. It not copy and paste man!

feel free to fund my project complete, then i´m able to post only the news 

[bensam1231]

So I have a theory as to part of what is causing the fluctuations in the network (the saw tooth pattern). After a fast block, Blagos miner doesn't error out on the block and proceed to the next one. This means all machines currently mining on the last block will continue mining on a block that is already past. They do this till they finish scanning the disks as they normally would. Meanwhile the fresh block on the network will not be mined by the full network as everyone running Blagos miner is still working on the last block until they finish as if a new block hadn't appeared.

When multiple fast blocks happen, the next block will not receive the full mine, let alone the one after that, which can cause the network hash power to stagger downhill.

Obviously there are still people not using Blagos miner and may be using Pocminer, Urays, or Rurus where this does not seem to be a issue, so it only effects about 30% of the network. It also seems as though this does not happen if you mine on the Dev pool, but I've witnessed this behavior across multiple machines solo and on other pools.

It's not hard to see this. Look through the log of your miners, when you see a 'fast block or corrupt' or a incomplete mine (% isn't 100 before the next block), you can look at the difference in time between when that event happened and when the miner continues on to the next block and it's the difference of time that was remaining before it completed the mine of the 'fast block'.

Now, I'm not exactly sure why this hasn't been fixed yet. I brought this up multiple times including in a PM with Blago and this definitely looks like something that could easily be fixed and it's not hard to reproduce, so I assume it's to give fast machines a leg up on slow ones.

If someone wants to hack a fix, a program that monitors either Blagos miner or the log file and simply restarts the miner when either 'fast block' appears in the log or when the wallet pops a new block that would effectively fix this.

[FakeAccount]

Can you stop that copy-paste man?
It's boring to see 3 same posts per page...

it's definitely approaching annoying territory, hope you get it funded already.

[FakeAccount]

So I have a theory as to part of what is causing the fluctuations in the network (the saw tooth pattern). After a fast block, Blagos miner doesn't error out on the block and proceed to the next one. This means all machines currently mining on the last block will continue mining on a block that is already past. They do this till they finish scanning the disks as they normally would. Meanwhile the fresh block on the network will not be mined by the full network as everyone running Blagos miner is still working on the last block until they finish as if a new block hadn't appeared.

When multiple fast blocks happen, the next block will not receive the full mine, let alone the one after that, which can cause the network hash power to stagger downhill.

Obviously there are still people not using Blagos miner and may be using Pocminer, Urays, or Rurus where this does not seem to be a issue, so it only effects about 30% of the network. It also seems as though this does not happen if you mine on the Dev pool, but I've witnessed this behavior across multiple machines solo and on other pools.

It's not hard to see this. Look through the log of your miners, when you see a 'fast block or corrupt' or a incomplete mine (% isn't 100 before the next block), you can look at the difference in time between when that event happened and when the miner continues on to the next block and it's the difference of time that was remaining before it completed the mine of the 'fast block'.

Now, I'm not exactly sure why this hasn't been fixed yet. I brought this up multiple times including in a PM with Blago and this definitely looks like something that could easily be fixed and it's not hard to reproduce, so I assume it's to give fast machines a leg up on slow ones.

If someone wants to hack a fix, a program that monitors either Blagos miner or the log file and simply restarts the miner when either 'fast block' appears in the log or when the wallet pops a new block that would effectively fix this.

not so sure about this. the default setting in the config file is 2 seconds (going by memory) so at most, and if default value is present, it will take 2 seconds for Blago's miner to give up a block and start mining the next one.  I reduced my setting to 750 ms for ex.

but I have been thinking about this:

let's say I have 200TB, atm the calculator says that should be 32386 burst or /7350 = 4.4 blocks.
if I see that since 00:00:00.000 I have found 5 blocks, and let's say we have another 12 hours to go in that day, then it's very likely I shouldn't find any more blocks for the remainder of the 12 hours.  so I switch to mine against a pool and rackup another 10000-15000 burst.  then when midnight hits, I switch to solo. if next day I have fast luck, I repeat, if not, I keep mining solo until next day and check if I should repeat. and so on.
this is kind of like pool hoping to increase your reward?  this is a crude description and you can substitute any numbers with whatever you want to test this scenario...
does this make sense, is it possible to "game" burst mining like this for a bit?
pool operators should change their reward algos to prevent this?

[ciocgun]

HI,
i got a problem today

i've deleted a buy offer of an asset and got an error.
Some of the amount as returned into my balance, and some not..
what can i do?

do you see any asset balance for which you placed a buy order? i think your buy order got partially filled?

if i sum the total mined amound it's more then the total amount spent to buy asset

[bensam1231]

So I have a theory as to part of what is causing the fluctuations in the network (the saw tooth pattern). After a fast block, Blagos miner doesn't error out on the block and proceed to the next one. This means all machines currently mining on the last block will continue mining on a block that is already past. They do this till they finish scanning the disks as they normally would. Meanwhile the fresh block on the network will not be mined by the full network as everyone running Blagos miner is still working on the last block until they finish as if a new block hadn't appeared.

When multiple fast blocks happen, the next block will not receive the full mine, let alone the one after that, which can cause the network hash power to stagger downhill.

Obviously there are still people not using Blagos miner and may be using Pocminer, Urays, or Rurus where this does not seem to be a issue, so it only effects about 30% of the network. It also seems as though this does not happen if you mine on the Dev pool, but I've witnessed this behavior across multiple machines solo and on other pools.

It's not hard to see this. Look through the log of your miners, when you see a 'fast block or corrupt' or a incomplete mine (% isn't 100 before the next block), you can look at the difference in time between when that event happened and when the miner continues on to the next block and it's the difference of time that was remaining before it completed the mine of the 'fast block'.

Now, I'm not exactly sure why this hasn't been fixed yet. I brought this up multiple times including in a PM with Blago and this definitely looks like something that could easily be fixed and it's not hard to reproduce, so I assume it's to give fast machines a leg up on slow ones.

If someone wants to hack a fix, a program that monitors either Blagos miner or the log file and simply restarts the miner when either 'fast block' appears in the log or when the wallet pops a new block that would effectively fix this.

not so sure about this. the default setting in the config file is 2 seconds (going by memory) so at most, and if default value is present, it will take 2 seconds for Blago's miner to give up a block and start mining the next one.  I reduced my setting to 750 ms for ex.

but I have been thinking about this:

let's say I have 200TB, atm the calculator says that should be 32386 burst or /7350 = 4.4 blocks.
if I see that since 00:00:00.000 I have found 5 blocks, and let's say we have another 12 hours to go in that day, then it's very likely I shouldn't find any more blocks for the remainder of the 12 hours.  so I switch to mine against a pool and rackup another 10000-15000 burst.  then when midnight hits, I switch to solo. if next day I have fast luck, I repeat, if not, I keep mining solo until next day and check if I should repeat. and so on.
this is kind of like pool hoping to increase your reward?  this is a crude description and you can substitute any numbers with whatever you want to test this scenario...
does this make sense, is it possible to "game" burst mining like this for a bit?
pool operators should change their reward algos to prevent this?

There isn't a setting in the config for this, unless you have a different one then me. There is two settings ""SendInterval": 200 and "UpdateInterval": 2000. One reflects the frequency of sending updates to the wallet and receiving them, neither address this bug. The values above are mine as well.

'Luck' doesn't work that way. There is not a cap on how many blocks you can find in a day. Every block is a lottery. There is no limit on the number of blocks you can find. It would be different if Burst intelligently distributed blocks, but it doesn't, which is why we get fucked on some days and not on others. That is also why if you don't have enough 'tickets' you shouldn't be mining on your own or there wont be enough potential finds to balance things out.

[daWallet]

but I have been thinking about this:

let's say I have 200TB, atm the calculator says that should be 32386 burst or /7350 = 4.4 blocks.
if I see that since 00:00:00.000 I have found 5 blocks, and let's say we have another 12 hours to go in that day, then it's very likely I shouldn't find any more blocks for the remainder of the 12 hours.  so I switch to mine against a pool and rackup another 10000-15000 burst.  then when midnight hits, I switch to solo. if next day I have fast luck, I repeat, if not, I keep mining solo until next day and check if I should repeat. and so on.
this is kind of like pool hoping to increase your reward?  this is a crude description and you can substitute any numbers with whatever you want to test this scenario...
does this make sense, is it possible to "game" burst mining like this for a bit?
pool operators should change their reward algos to prevent this?

This doesn't make sense because if you're very lucky for some time solo, then switch to a pool... your deadlines still will be statistically worse for some time. The pool doesn't know you have 200 TB, the pool sees only your submitted deadlines and these will be quite bad in your scenario.

[mczarnek]

One year since Mt Gox but a lot of people seem to have forgotten: http://www.pcworld.com/article/2892892/one-year-later-were-no-closer-to-finding-mtgoxs-missing-millions.html

Anyone keeping millions of Burst on the exchanges.. Please move it to another account controlled by you and only you. Only keep money there when trading. An exchange hack could be a disaster at the moment for us if it's poloniex or bittrex.

Yea, the hard part about this is my day trader cash. You kinda have to keep some there.

Agreed.. just have to be careful about how much is on the exchange versus in your wallet and ideally split it between exchanges.

[dvdelkin]

Dear Sirs
Please answer my questions
1) why my nvidia gtx275 doesn't work for plotting? My driver is 314.22. When i just start plotting an error appears [ERROR][-36][CL_INVALID_COMMAND_QUEUE] Error in step2 kernel finish. What's wrong? Or i tried geforce 580 or 750mobile and i got the same error
2) i previously successfully plotted one plot with the size of 1.74Tb. But currently i tried several times to plot just about 400Gb and in several minutes i got an error "GPU plotter closed". What happens? Plotting now doesn't come to the end, it stops in several minutes after the beginning
3) Can i use simultaneously Radeon 290 and gtx275 for plotting?
4) What are correct settings, url for  V2 Burst Pool? On official page it's written "http://127.0.0.1:8125 http://thispoolsip", but that doesn't work. I use Uray miner.
5) Why during mining my Disk C is periodically loaded for 100% and internet sites are loaded very slow? It happens only during mining, My plots are on the disk K.
6) I've been mining for about 12 hours on tompool.org. On http://mining.tompool.org:82/ it was written that my round share was about 144. But in my wallet i didn't get NOTHING from tompool.org. I have one plot for 1.74Tb
7) In comparison then I've been mining about 5 hours at burst.ninja:8124 and already got 16bursts. Where are my bursts from tompool.org?

[Irontiga]

Dear Sirs
Please answer my questions
1) why my nvidia gtx275 doesn't work for plotting? My driver is 314.22. When i just start plotting an error appears [ERROR][-36][CL_INVALID_COMMAND_QUEUE] Error in step2 kernel finish. What's wrong? Or i tried geforce 580 or 750mobile and i got the same error
2) i previously successfully plotted one plot with the size of 1.74Tb. But currently i tried several times to plot just about 400Gb and in several minutes i got an error "GPU plotter closed". What happens? Plotting now doesn't come to the end, it stops in several minutes after the beginning
3) Can i use simultaneously Radeon 290 and gtx275 for plotting?
4) What are correct settings, url for  V2 Burst Pool? On official page it's written "http://127.0.0.1:8125 http://thispoolsip", but that doesn't work. I use Uray plotter.
5) Why during mining my Disk C is periodically loaded for 100% and internet sites are loaded very slow? It happens only during mining, My plots are on the disk K.
6) I've been mining for about 12 hours on tompool.org. On http://mining.tompool.org:82/ it was written that my round share was about 144. But in my wallet i didn't get NOTHING from tompool.org. I have one plot for 1.74Tb
7) In comparison then I've been mining about 5 hours at burst.ninja:8124 and already got 16bursts. Where are my bursts from tompool.org?

1)Dunno

2)^^^ Try a CPU plotter

3)^^^ But i think U can

4)Plotter and miner are different....I think u meant uray miner, and it doesn't support dev v2 pool. It does support burst.ninja tho(actually, burst.ninja supports it), so u can just mine there. For dev v2 u need blago miner or the old javaminer from the dev(don't go there).

5)Plotting is where u hardout, full time make plots. This is essentially just storing your hashrate One it is done, it is done. Mining reads a chunk of your plots(based on the scoop the current block needs, it is always 1/4096 of your plots), and then calculates deadlines, and submits them to pool or network.

6) You probably didn't hit min payout or the pool didn't find a block...i'm guessing it's the latter.

7) Burst.ninja is just awesome

[coinits]

Dear Sirs
Please answer my questions
1) why my nvidia gtx275 doesn't work for plotting? My driver is 314.22. When i just start plotting an error appears [ERROR][-36][CL_INVALID_COMMAND_QUEUE] Error in step2 kernel finish. What's wrong? Or i tried geforce 580 or 750mobile and i got the same error
2) i previously successfully plotted one plot with the size of 1.74Tb. But currently i tried several times to plot just about 400Gb and in several minutes i got an error "GPU plotter closed". What happens? Plotting now doesn't come to the end, it stops in several minutes after the beginning
3) Can i use simultaneously Radeon 290 and gtx275 for plotting?
4) What are correct settings, url for  V2 Burst Pool? On official page it's written "http://127.0.0.1:8125 http://thispoolsip", but that doesn't work. I use Uray plotter.
5) Why during mining my Disk C is periodically loaded for 100% and internet sites are loaded very slow? It happens only during mining, My plots are on the disk K.
6) I've been mining for about 12 hours on tompool.org. On http://mining.tompool.org:82/ it was written that my round share was about 144. But in my wallet i didn't get NOTHING from tompool.org. I have one plot for 1.74Tb
7) In comparison then I've been mining about 5 hours at burst.ninja:8124 and already got 16bursts. Where are my bursts from tompool.org?

1)Dunno

2)^^^ Try a CPU plotter

3)^^^ But i think U can

4)Plotter and miner are different....I think u meant uray miner, and it doesn't support dev v2 pool. It does support burst.ninja tho(actually, burst.ninja supports it), so u can just mine there. For dev v2 u need blago miner or the old javaminer from the dev(don't go there).

5)Plotting is where u hardout, full time make plots. This is essentially just storing your hashrate One it is done, it is done. Mining reads a chunk of your plots(based on the scoop the current block needs, it is always 1/4096 of your plots), and then calculates deadlines, and submits them to pool or network.

6) You probably didn't hit min payout or the pool didn't find a block...i'm guessing it's the latter.

7) Burst.ninja is just awesome

I could never get NVIDIA to plot. Always used CPU.