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

[uray]

which is diffcult to achieve, because burst use 4098 round of hashing

Burst uses far more than 4098 rounds. 1 shabal256 hash is 32 bytes. The generated plot is 262144 bytes, made up of 8192 hashes, plus the one which is xored, so there are 8193 shabal256 hashes done. Each round of shabal uses 64 bytes of data, and if the data processed is a multiple of 64 bytes it does an extra round. Most of the hashing is done on 4096 bytes of data, so about 65 rounds per hash, so somewhere around 8193 * 65 would be about 532545 rounds.

ok, 48413 times more secure than X11 !

[Hamuki]

I am trying to setup my miner, but my pc cant detect java.

What do I do?
Its installed, and I rebooted the PC so it should be ok, but it does not work.

Does anyone have a fix or can you help me set up my miner?

[Blago]

the blago miner support dev2 pool?

did not support

[xizmax]

I am trying to setup my miner, but my pc cant detect java.

What do I do?
Its installed, and I rebooted the PC so it should be ok, but it does not work.

Does anyone have a fix or can you help me set up my miner?

You only need java for the burst server, for mining and plotting there are other options.

Make sure you downloaded the correct java version (7 iirc).

[HunterS]

guys im a big supporter of this coin and hold a few but 99% of this thread is just mining/techsupport.We need a new thread for development and PR.this thread is just endless pages of tech support to new investors

[yellowduck2]

guys im a big supporter of this coin and hold a few but 99% of this thread is just mining/techsupport.We need a new thread for development and PR.this thread is just endless pages of tech support to new investors

Current price clearly tell us PR is missing. I am not sure what will happen to price when block reward got cut further and PR came on board later on.

Perhaps there is a PR team waiting for block reward to drop further before any actions.

Meaning now could be distribution , accumulation period

[uray]

guys im a big supporter of this coin and hold a few but 99% of this thread is just mining/techsupport.We need a new thread for development and PR.this thread is just endless pages of tech support to new investors

we have our own thread on PR here : https://bitcointalk.org/index.php?topic=825644.0
and also look at burstforum.com we got bunch of PR thread too

[Grim]

Wow, our pool is doing amazingly! Thank you all! 


Just sent the first 10k bonus to the pool address, and I think we just found 3 blocks in a row!

I put 33TB on your pool. I'll gonna see for the next few days how it goes.
So don't send me any rewards yet 

You can send me some if I decide to stay.
(came from solo and devpoolv2)

ok im staying, your reward is still there to grab ?

(just asking before I take screenshots...)

[Hamuki]

How many coins do you make pr day from those 33TB?

[FakeAccount]

How many coins do you make pr day from those 33TB?

OP has a link to calculator

[tex81]

1TB of plots are equivalent to 1 000 000 nonces per minute. So real-time plotting for mining is useless (with current software and speed).

wrong, its 4*1024*1024 , 1 nonce = 256KB (0.25MB)
if you can hash burst algo by 4.19 MH/s , its equal to 1TB of disk capacity
which is diffcult to achieve, because burst use 4098 round of hashing, compared that to X11 algo, which use 11 round, burst in term of hashing complexity is 372 times more secure than darkcoin!

4*1024*1024, but blocktime is 4 min, so /4 = about 1M/min.

[SB73]

the blago miner support dev2 pool?

did not support

waiting for this feature !!! ;-)

[crowetic]

Just so that everyone knows, right now burst.ga is running on it's backup server, so be sure to restart your miners to reconnect, and setup a restart script, or restart them every so often so that they will go back to the main server when it's back on line. Thanks!

Or, just run Blago's miner, which I will be switching to soon, because it automatically picks up the change in IP, awesome.

[go6ooo1212]

Just so that everyone knows, right now burst.ga is running on it's backup server, so be sure to restart your miners to reconnect, and setup a restart script, or restart them every so often so that they will go back to the main server when it's back on line. Thanks!

Or, just run Blago's miner, which I will be switching to soon, because it automatically picks up the change in IP, awesome.

Which sets of commands should restart cmd on windows automaticaly

[crowetic]

Just so that everyone knows, right now burst.ga is running on it's backup server, so be sure to restart your miners to reconnect, and setup a restart script, or restart them every so often so that they will go back to the main server when it's back on line. Thanks!

Or, just run Blago's miner, which I will be switching to soon, because it automatically picks up the change in IP, awesome.

Which sets of commands should restart cmd on windows automaticaly

here is an example of the script batch file I used to restart automatically every 5000 seconds... This was using Uray's miner, but you can replace the line with burst-miner.exe with the line that starts the java miner, and it will work the same for that...


@echo off
timeout 3
:mine
echo Mining for howevermany min calc, after that the miner will restart.
start burst-miner.exe
timeout 5000
taskkill /IM burst-miner.exe
goto mine

[Nevril]

Update v1.0.2

Burst Long Term Price Support project
(BLTPS)

Changelog
v1.0.2 - 03/nov/2014
Added a Frequently Asked Question section.

Remember that Phase 1 ends on 08/nov/2014!

[crowetic]

-Announcement-


Due to circumstances beyond our control... the main server AND host have to be taken down indefinitely...

What this means for the pool is...

Right now the pool will stay on the failover server, so the miners once they get connected to the failover server, shouldn't notice any interrupts in service. So, in theory there should be no difference for current miners.

If your miner is currently not connected, restart it to get the failover server's IP and get connected.

Once you're connected you're good. From this point, we will continue to use our backup server until I can get a new main server setup and running. I don't expect this to take me that long, but it will take a little time.

I will for now, make some changes to the failover pool and make the payouts start from there, so don't worry everyone, you will get all of your mined coins.


Once I have the new main server up, I will configure the failover setup to the new main IP, and everything will be back up and running, with failover, like it was before.


So, in theory the miners on the pool should only see a few seconds of downtime, enough for them to restart their miners, and connect to the failover IP, then await me getting the new server up and running.

I am sorry for the inconvenience, and I will let everyone know when the situation has been resolved. Thank you!

[xizmax]

-Announcement-


Due to circumstances beyond our control... the main server AND host have to be taken down indefinitely...

What this means for the pool is...

Right now the pool will stay on the failover server, so the miners once they get connected to the failover server, shouldn't notice any interrupts in service. So, in theory there should be no difference for current miners.

If your miner is currently not connected, restart it to get the failover server's IP and get connected.

Once you're connected you're good. From this point, we will continue to use our backup server until I can get a new main server setup and running. I don't expect this to take me that long, but it will take a little time.

I will for now, make some changes to the failover pool and make the payouts start from there, so don't worry everyone, you will get all of your mined coins.


Once I have the new main server up, I will configure the failover setup to the new main IP, and everything will be back up and running, with failover, like it was before.


So, in theory the miners on the pool should only see a few seconds of downtime, enough for them to restart their miners, and connect to the failover IP, then await me getting the new server up and running.

I am sorry for the inconvenience, and I will let everyone know when the situation has been resolved. Thank you!

Mate who is hosting all this for you. You seem to be quite out of luck with them

[crowetic]

-Announcement-


Due to circumstances beyond our control... the main server AND host have to be taken down indefinitely...

What this means for the pool is...

Right now the pool will stay on the failover server, so the miners once they get connected to the failover server, shouldn't notice any interrupts in service. So, in theory there should be no difference for current miners.

If your miner is currently not connected, restart it to get the failover server's IP and get connected.

Once you're connected you're good. From this point, we will continue to use our backup server until I can get a new main server setup and running. I don't expect this to take me that long, but it will take a little time.

I will for now, make some changes to the failover pool and make the payouts start from there, so don't worry everyone, you will get all of your mined coins.


Once I have the new main server up, I will configure the failover setup to the new main IP, and everything will be back up and running, with failover, like it was before.


So, in theory the miners on the pool should only see a few seconds of downtime, enough for them to restart their miners, and connect to the failover IP, then await me getting the new server up and running.

I am sorry for the inconvenience, and I will let everyone know when the situation has been resolved. Thank you!

Mate who is hosting all this for you. You seem to be quite out of luck with them

Yea, we've definitely been through the ringer on this server. Then we finally had everything going perfectly, and this happens. I will say it has nothing to do with the reliability of the actual hardware or the pool anything like that, it's a completely personal reason that this had to come to an end.

Wish I would have known sooner, but it is what it is. I will get a new server up in it's place as soon as I can. But for now we're still okay, the server it's running on now is dedicated hardware on a nice dedicated connection. So we're all good. Just gotta get the miners to restart their miners and reconnect.

[BitcoinGeekBoy]

-Announcement-


Due to circumstances beyond our control... the main server AND host have to be taken down indefinitely...

What this means for the pool is...

Right now the pool will stay on the failover server, so the miners once they get connected to the failover server, shouldn't notice any interrupts in service. So, in theory there should be no difference for current miners.

If your miner is currently not connected, restart it to get the failover server's IP and get connected.

Once you're connected you're good. From this point, we will continue to use our backup server until I can get a new main server setup and running. I don't expect this to take me that long, but it will take a little time.

I will for now, make some changes to the failover pool and make the payouts start from there, so don't worry everyone, you will get all of your mined coins.


Once I have the new main server up, I will configure the failover setup to the new main IP, and everything will be back up and running, with failover, like it was before.


So, in theory the miners on the pool should only see a few seconds of downtime, enough for them to restart their miners, and connect to the failover IP, then await me getting the new server up and running.

I am sorry for the inconvenience, and I will let everyone know when the situation has been resolved. Thank you!

I have not seen payouts for over 5 hours.

Are the payouts working on the failover server.

My miners have been reset several times to make sure I am mining on the failover server.  My miners show they are mining and no errors.

I see over 1000 coins qued upped for my address ==>  CJNP-KCEQ-6545-2FF4M