Author

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

newbie
Activity: 28
Merit: 0
Ok there is tested config for 280x:

Code:
gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you. Smiley

You put 64 instead of 256?

I'll try 64 to see if i got more too

I tried 128 and 256 but it didn't work.

what driver version do you have installed? windows or linux?

Win7 64-bit. Drivers 13.xx.
hero member
Activity: 518
Merit: 500
Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

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

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).
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

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

Here is the new version. I reduced the amount of memory used from 40KB to about 1KB per unit. The only drawback is that it requires twice the global memory as before. I will search a mean to reduce this overhead later.
In CPU mode, it all goes pretty well (when no graphic card is detected).
The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow.

Here are the files :
gpuPlotGenerator-src-1.1.0.7z : https://mega.co.nz/#!iYFWAL5B!BvtmRQ5qGq4gGwjDglFNtDtNIX4LDaUvATBtClBdTlQ
gpuPlotGenerator-bin-win-x86-1.1.0.7z : https://mega.co.nz/#!aBVGBBQD!tBsRtb8VrHR12_anrFTrl41U0fPQu_OqFnxyi5nCyBY

For the linux users, the Makefile has a new target named "dist" that builds and copy/paste all the necessary files to the "bin" directory.

The executable usage is : ./gpuPlotGenerator

: the path to the plots directory
: number of parrallel threads for each work group

Found the "randomness" cause. NVIDIA is caching the kernel after the first build and rebuild it from time to time. By cleaning the cache, I can force the kernel build and speed up the debugging process.
I will notify you as soon as the crash cause is found and corrected.

I just got it to run for a bit, but crashes after a few seconds on the AMD HD7970.

Exactly the same here on the HD 7990. App crashes on "building openCL platform".

fault name: amdocl.dll


Exactly the same error in Windows. I'm on the 14.7 driver.
hero member
Activity: 599
Merit: 500
Anyone can help with pool mining ?

Maybe i do something wrong ?

1.I opened: http://127.0.0.1:8125/rewardassignment.html
2. I put my wallet password into field: Set reward recipient
3. In recipient field: 10745596296835956940
4. Submit
5. This is output

{"fullHash":"21948bc8964a1b544f86be0add9a13b1527f8ce88daeb6edca92fb6010c76645","signatureHash":"280f2cb04eac7432b917f98183ce33cc22162ac40bdf82bf9a0a5b301cccbebf","transactionBytes":"1400a0972600a005b313923ee6c0403aff2395dcd8a08114284ea5f6512bdddee2fdaef669b69b7 1cc00a93ce6062095000000000000000000e1f50500000000000000000000000000000000000000 00000000000000000000000000000000005f47807336cbefc95d3d6dacfeaa0cdbe19aab8251017 4735c8d1e958429e40cb4619c1a75b53f8fd94403a91dafec8d2e2d0e9618d2e1d402f272c53b4d 94b4","transaction":"6060519735027274785","broadcasted":true,"unsignedTransactionBytes":"1400a0972600a005b313923ee6c0403aff2395dcd8a08114284ea5f6512bdddee2fdaef669b69b7 1cc00a93ce6062095000000000000000000e1f50500000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000"}

6. I wait for 4 blocks then closed wallet and burst server
7 I download java miner add port :8124 at the end of http://burst-pool.cryptoport.io
8. Run miner

i create a video  here http://youtu.be/oYlf1xFTHvs

sr. member
Activity: 434
Merit: 250
Ok there is tested config for 280x:

Code:
gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you. Smiley

You put 64 instead of 256?

I'll try 64 to see if i got more too

I tried 128 and 256 but it didn't work.

what driver version do you have installed? windows or linux?
newbie
Activity: 28
Merit: 0
Ok there is tested config for 280x:

Code:
gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you. Smiley

You put 64 instead of 256?

I'll try 64 to see if i got more too

I tried 128 and 256 but it didn't work.
hero member
Activity: 1036
Merit: 531
The GPUplotter is not working - using EXACTLY the config you have. Did you install the OpenCL driver from AMD?

juste the base driver
hero member
Activity: 1036
Merit: 531
For those who use gpu plotter, seems to working better with Threads = 64 or 128 got nearly 40% more then 256
member
Activity: 112
Merit: 10
Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

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

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).
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

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

Here is the new version. I reduced the amount of memory used from 40KB to about 1KB per unit. The only drawback is that it requires twice the global memory as before. I will search a mean to reduce this overhead later.
In CPU mode, it all goes pretty well (when no graphic card is detected).
The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow.

Here are the files :
gpuPlotGenerator-src-1.1.0.7z : https://mega.co.nz/#!iYFWAL5B!BvtmRQ5qGq4gGwjDglFNtDtNIX4LDaUvATBtClBdTlQ
gpuPlotGenerator-bin-win-x86-1.1.0.7z : https://mega.co.nz/#!aBVGBBQD!tBsRtb8VrHR12_anrFTrl41U0fPQu_OqFnxyi5nCyBY

For the linux users, the Makefile has a new target named "dist" that builds and copy/paste all the necessary files to the "bin" directory.

The executable usage is : ./gpuPlotGenerator

: the path to the plots directory
: number of parrallel threads for each work group

Found the "randomness" cause. NVIDIA is caching the kernel after the first build and rebuild it from time to time. By cleaning the cache, I can force the kernel build and speed up the debugging process.
I will notify you as soon as the crash cause is found and corrected.

I just got it to run for a bit, but crashes after a few seconds on the AMD HD7970.

Exactly the same here on the HD 7990. App crashes on "building openCL platform".

fault name: amdocl.dll
sr. member
Activity: 355
Merit: 250
Anyone can help with pool mining ?

Maybe i do something wrong ?

1.I opened: http://127.0.0.1:8125/rewardassignment.html
2. I put my wallet password into field: Set reward recipient
3. In recipient field: 10745596296835956940
4. Submit
5. This is output

{"fullHash":"21948bc8964a1b544f86be0add9a13b1527f8ce88daeb6edca92fb6010c76645","signatureHash":"280f2cb04eac7432b917f98183ce33cc22162ac40bdf82bf9a0a5b301cccbebf","transactionBytes":"1400a0972600a005b313923ee6c0403aff2395dcd8a08114284ea5f6512bdddee2fdaef669b69b7 1cc00a93ce6062095000000000000000000e1f50500000000000000000000000000000000000000 00000000000000000000000000000000005f47807336cbefc95d3d6dacfeaa0cdbe19aab8251017 4735c8d1e958429e40cb4619c1a75b53f8fd94403a91dafec8d2e2d0e9618d2e1d402f272c53b4d 94b4","transaction":"6060519735027274785","broadcasted":true,"unsignedTransactionBytes":"1400a0972600a005b313923ee6c0403aff2395dcd8a08114284ea5f6512bdddee2fdaef669b69b7 1cc00a93ce6062095000000000000000000e1f50500000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000"}

6. I wait for 4 blocks then closed wallet and burst server
7 I download java miner add port :8124 at the end of http://burst-pool.cryptoport.io
8. Run miner
hero member
Activity: 1036
Merit: 531
Ok there is tested config for 280x:

Code:
gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you. Smiley

You put 64 instead of 256?

I'll try 64 to see if i got more too
hero member
Activity: 518
Merit: 500
Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

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

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).
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

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

Here is the new version. I reduced the amount of memory used from 40KB to about 1KB per unit. The only drawback is that it requires twice the global memory as before. I will search a mean to reduce this overhead later.
In CPU mode, it all goes pretty well (when no graphic card is detected).
The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow.

Here are the files :
gpuPlotGenerator-src-1.1.0.7z : https://mega.co.nz/#!iYFWAL5B!BvtmRQ5qGq4gGwjDglFNtDtNIX4LDaUvATBtClBdTlQ
gpuPlotGenerator-bin-win-x86-1.1.0.7z : https://mega.co.nz/#!aBVGBBQD!tBsRtb8VrHR12_anrFTrl41U0fPQu_OqFnxyi5nCyBY

For the linux users, the Makefile has a new target named "dist" that builds and copy/paste all the necessary files to the "bin" directory.

The executable usage is : ./gpuPlotGenerator

: the path to the plots directory
: number of parrallel threads for each work group

Found the "randomness" cause. NVIDIA is caching the kernel after the first build and rebuild it from time to time. By cleaning the cache, I can force the kernel build and speed up the debugging process.
I will notify you as soon as the crash cause is found and corrected.

I just got it to run for a bit, but crashes after a few seconds on the AMD HD7970.
newbie
Activity: 28
Merit: 0
Ok there is tested config for 280x:

Code:
gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you. Smiley
member
Activity: 112
Merit: 10
full member
Activity: 132
Merit: 100
The price for me is fine.300sat it is a good time to buy.I think BURST have a real innovation Wink
full member
Activity: 154
Merit: 100
Add me on Twitter! @AnonOnAMoose
http://burst.cryptoport.io/acc/2715798095717378439 - Now there is some mining power!

Looks like he's 15.5% of the hashpower on my v2 pool.

terrible thing is that it is probably the xcloudcoin multipool...
full member
Activity: 224
Merit: 100
http://burst.cryptoport.io/acc/2715798095717378439 - Now there is some mining power!

Looks like he's 15.5% of the hashpower on my v2 pool.

I started getting "Unable to get mining info from wallet" today using your pool.
member
Activity: 112
Merit: 10
The GPUplotter is not working - using EXACTLY the config you have. Did you install the OpenCL driver from AMD?
member
Activity: 60
Merit: 10
Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

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

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).
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

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

Here is the new version. I reduced the amount of memory used from 40KB to about 1KB per unit. The only drawback is that it requires twice the global memory as before. I will search a mean to reduce this overhead later.
In CPU mode, it all goes pretty well (when no graphic card is detected).
The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow.

Here are the files :
gpuPlotGenerator-src-1.1.0.7z : https://mega.co.nz/#!iYFWAL5B!BvtmRQ5qGq4gGwjDglFNtDtNIX4LDaUvATBtClBdTlQ
gpuPlotGenerator-bin-win-x86-1.1.0.7z : https://mega.co.nz/#!aBVGBBQD!tBsRtb8VrHR12_anrFTrl41U0fPQu_OqFnxyi5nCyBY

For the linux users, the Makefile has a new target named "dist" that builds and copy/paste all the necessary files to the "bin" directory.

The executable usage is : ./gpuPlotGenerator

: the path to the plots directory
: number of parrallel threads for each work group

Found the "randomness" cause. NVIDIA is caching the kernel after the first build and rebuild it from time to time. By cleaning the cache, I can force the kernel build and speed up the debugging process.
I will notify you as soon as the crash cause is found and corrected.
hero member
Activity: 952
Merit: 500
anyone tried mining BURST on cloud yet??


not on a public cloud which can be setuped to automatically clone plotting/mining instances but on my private cloud manually ;-)

on centos you only install the core system from the setup and run this:
yum groupinstall "Development Tools"
yum install java* screen git
mkdir burst
cd burst
git clone https://github.com/BurstProject/burstcoin
git clone https://github.com/BurstProject/pocminer

cd burstcoin
chmod +x *.sh
./compile.sh
screen -dmS wallet ./run.sh
cd..

cd pocminer
chmod +x *.sh
./compile.sh
screen -dmS mine ./run_mine.sh
upload or generate your passphrase.txt
screen -dmS plot ./run_generate.sh address start count stagger threads
 

Entered this: yum groupinstall "Development Tools"

My server and the provider's entire website went down lol....

https://bchain.info/BURST/tools/calculator must be using the same host I do, site is down too
hero member
Activity: 1036
Merit: 531
Quote

This is my parameter

Code:
gpuPlotGenerator.exe plots myaccount 68847637 18500000 4096 256

I run it, it started, but plot isn't generated. Win7 64bit, 280x.

If plot file is to 0bites but in the plot folders, that's normal it will grow with the time
Jump to: