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

No.

U need

CPU

RAM

Disk Space

Good Internet Connection

All of the above combine. Lack of any u are better of buying coin

How do you calculate your nonces before creating a plot? Is mining on your average i7 powered CPU worth it?

1GB is 1024*1024 kB. Your formula is wrong. Just check any one plotfile.

Thanks, I will look at your kernels to see if I can find a better solution.

So is HDD space the ONLY factor in mining here? Buying hard drive space = more coins mined?

Is ~1TB going to generate any income at all?

Simplest explanation I can give is this is similar to proof-of-stake, but the amount of space you have occupied by plot files on your hdd is your stake instead of amount of coins.
Unlike POS, it technically is possible to POW mine this, but the hashrate/W is absolutely horrible compared to mining it as intended.

OK, I got the idea. Used faucet, waited till confirmation and now it seems working.
Would be good idea to update howto.

You just create your Burst account and never had any outgoing-incoming transactions yet?

Pls help ! Trying to use V2 pool miner.
Cannot set reward address at http://127.0.0.1:8125/rewardassignment.html

Get :
{"errorCode":5,"errorDescription":"Unknown account"}

Why ?

Just try with amd R9 290X : insufisant private ressource

It's nice to see someone else working on this, since I seem to have failed in it.

Private memory is actually part of global on AMD cards, so storing it in private isn't any better than just using global for everything; it's local that needs to aimed for for the massive speedup. No AMD cards have more than 64KB local per workgroup, which makes storing it all in local impossible however.

I haven't tried your implementation yet, but on my own first attempt, I also used global on everything also, and the result was faster than the java plotter, but slower than dcct's c plotter. My 2nd attempt used a 32KB local buffer I rotated through for storing the currently being hashed stuff, however I couldn't figure out how to get it copied also to global fast enough, and the local -> global copy killed the performance.

You might be interested in those kernels here: https://bitcointalksearch.org/topic/m.8695829

wow this currency has me stumped. Anyone have a good layman-ish explanation of what plots are for and how the mining correlates to your HDD space? Haven't trouble getting this up and running and not seeing any results from the mining. Can't tell if I'm doing this right.

Where is that?

Yes there is one.
https://bchain.info/BURST/tools/calculator

I see it in the c++ windows plotter

How are you guys getting the n/m? Calculating it manually or does it show up in the linux version of the plotter?

6 cores at 3.2 GHz doing 5400 n/m. It`s 213.3M cycles per nonce (on 1 core)
Boost clock is 3.8GHz - so get 253.3M cycles per nonce

My I5-2500K (no OC too):
base clock (3.3G): 204.1M cycles per nonce
boost clock (3.7G): 228.9M cycles per nonce

Just love math, LOL  

Are there any profitability calculators out there yet?

Anyone have rough numbers for the current mining rate:yield?

your formula gives a rough estimation, the one posted by me it`s more... exact (file on disk size).

1**********************9_60000000_40960_40960 - 10Gb (your version) - 10.485Gb (mine)

Hi everyone,

As promised I have been working on a GPU plot generator on the last few days. I made a little program built on top of OpenCL, and it seems to work pretty well in CPU mode. Unfortunately, I can't test the GPU mode as it requires a very powerfull graphic card (with at least 46kB private memory per compute unit, because the algorithm needs at least 4096*64 static bytes to store an entire plot).

Here is a preview you can test for now :
gpuPlotGenerator-src-1.0.0.7z : https://mega.co.nz/#!bcF2yKKL!3Ud86GaibgvwBehoxkbO4UNdiBgsaixRx7ksHrgNbDI
gpuPlotGenerator-bin-win-x86-1.0.0.7z : https://mega.co.nz/#!HJsziTCK!UmAMoEHQ3z34R4RsXoIkYo9rYd4LnFtO_pw-R4KObJs

I will build another release in the end of the day with some minor improvements (threads per compute unit selection, output of OpenCL error codes, improvement of the Makefile to generate the distribution directly).
I will also try to figure out another mean to dispatch the work between the GPU threads to reduce the amount of private memory needed by the program.

For the windows people, you can use the binary version directly.
For the linux people, just download the source archive, make sure to modify the OpenCL library and lib path in the makefile (and maybe the executable name), and build the project via "make". To run the program, you need the "kernel" and the "plots" directories beside the executable.

The executable usage is : ./gpuPlotGenerator

The parameters are the same as the original plot generator, without the threads number.

If you find bugs or if you want some new features, let me now.

If you want to support me, here are my Bitcoin and Burst addresses :
Bitcoin: 138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst: BURST-YA29-QCEW-QXC3-BKXDL

Regards