Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 573. (Read 2171057 times)

Nice, good job bro

I've updated the german tutorial with the latest wallet version and a how to, if you add another disks to your machine.

http://www.mku.name/post/burst-coin-mining

Oh ffs!  Maybe that's how my 50,000+ coins got stolen from my original wallet!!!  It doesn't give any instructions about removing your passphrase on the pool instructions!  OK, starting again, deleting all files and downloading from scratch... Maybe one day I will actually start mining!  I'm a computer engineer and programmer and if I'm having these types of problems then maybe things need to be made simpler and clearer for this coin to really take off.

A password consisting only of words can be bruteforced by dictionary attack. It's better to add some random characters to these words. It should be very long as well (36+ chars, maybe a few times longer as it's not ideally random).

Storing coins on exchange is bad bad bad idea. It's better to store them on a separate dedicated wallet (make sure it's secured by making at least one outgoing transaction).

Passphrase is not needed for mining on pool. Also, a special version of miner is needed. Delete the file containing passphrase from miner's folder, it's not needed. I assume you've set the pool's address in solo miner's settings and the passhprase was sent to the pool. If that's the case, the passphrase is now compromised.

I've changed it and gone with a sting of words of my choosing so hopefully all good now.  Will keep the wallet balance low by dumping to an exchange where hopefully the coins will be safer (Hmmmmm)

OK, I'm back now with a wallet that actually confirms transactions and seemingly all set to mine at burst.ga but when I submit shares I get an error 'Passphrase does not match reward recipient'  I've changed the passphrase where needed and run dump_address to obtain a new account and updated the files.  Any idea where I've gone wrong?  I've done everything needed in the wallet also and it's all confirmed.

Be careful, you can still end up with a low-entropy password that way.  A machine-generated password is safer.

Quick update

Burst Long Term Price Support project

The first goal of 250 shares (i.e. 2.5 BTC!) has been reached and surpassed. The next goal has been set to 475 shares.
More shares have already been booked and are waiting for payment to be sold and transferred.

Thanks to all who are believing in this project
And if you haven't joined us already, make sure you have a look at it!

...oh, I almost forgot... Tomorrow there will be a big update! Don't tell anybody!

As long as they don't overlap you are fine. So the next one just has to start somewhere later than where the first one finished

Everyone has to pay operating costs, that's no reason to sell an asset that will never have a chance at ROI.

my pool never dies
- some client has order my cloud mining contract 60tb+ today(wait for plots file)
- i have contract with 15+ clients for 6 Month / 1 Year
- i have money to pay ISP

Alas, some miners don't escape the passhprase properly when solo-mining. I've runned into this when my passphrase contained some garbage chars. This can be easily patched though.

Btw, until at least one outgoing transaction is made, wallet is mineable! Don't send money to newly created wallet.
What was your previous passphrase btw?

i've watched too many 5-10 min deadlines produced and beaten but not during a long block LOL

i think the owner could initialize it using their keys, like an initial "formatting" but to create a dynamic plot.  then software/driver handles re-sizing as needed.  maybe CPU utilization can be offloaded on a chip that is already on the hdd or a card attached to PCI/USB bus (if fast enough). but offloading is less important as mining could be also set to happen when system is idling.  when user starts utilizing their device, mining priority gets reduced.

-ANNOUNCEMENT-

The pool is now fully redundant, fully secure, and hosted on dedicated hardware VMWare ESXi in a really nice data center with a connection that tested at 500Mbit

http://burst.ga is going to rise again to become the top 3 pools like it used to be!


After many issues, I finally decided that I was done with having issues, and now we're setup in such a way that there should NEVER be another second of miner downtime!

We have 3 servers actively working for our project, and one that could be activated if need arises!

We are THE ONLY FAILOVER POOL!

The way we're setup, we have a balancer server that the miners connect to, the miners never have to change their IP address, which means NO MORE HAVING TO RESTART YOUR MINERS IF THERE IS A POOL ISSUE AND FAILOVER!

The balancer server routes the requests to the main pool, or if the main pool doesn't respond, it automatically routes the request to the backup pool, and no changes or restarts are required from the miner, because he's still pointing to the same IP as he was!


I am also going to re-activate a new giveaway, in order to get my previous people back, and get new miners on the pool!


Alright, the giveaway is as follows...


The next 25 people that join the pool, and provide me your burst address in a PM, and I see your address in stats on my pool, I will immediately send you 1,500 BURST!

Not only that, if you can prove that you have over 10TB (with screenshots just like my previous giveaway) I will give you another bonus of 8,000 BURST (split into two payments, one right away when I see you in stats, another a week later if you're still on the pool!)

This time should be the last time I have to do stuff like this, then after that all of our benefits, the failover, and all of the assets we will introduce, and have already introduced, will speak for themselves! So get at this giveaway while you can!

Thank you!

wow, now we reached 20 minutes with no block found... record?

My bad, I presumed you used the random passphrase generator.

If you reasonably think you didnt get bruteforced, perhaps a check for loggers is in order. I certainly hope that the attacker hasnt fount an unknown exploit

Not as of yet

Forgive my ignorance because I'm new to burst, but can you use the coin to store files yet?

I've just hammered the keyboard with random shift key presses and generated a very long string of characters that can't possibly be related to any language  That should do it LOL

Sorry to hear about the hack mate, this is a brainwallet so a good passphrase is of the essence.

What I would suggest, at least as an interim measure, is to add various other lesser known languages to the random passphrase generator.

It won't fix all the issues, but would provide a bit better protection against dictionary attacks.