Author

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

full member
Activity: 153
Merit: 100
do you think  burst will  go to above 3000?

Just one man's opinion:  Yes but it will go down afterwards.
sr. member
Activity: 448
Merit: 255
do you think  burst will  go to above 3000?
yuk
full member
Activity: 224
Merit: 100
hello, this started happening for one of my plots using the C+ generator..

can anyone tell what happened?

Have you finished plotting the files? What size are they? Looks like the miner cant read them, at least not completely.


I got this error sometime me too. they are some way to know if plots are corrupted?
btw mine are generated whit java poltter
sr. member
Activity: 280
Merit: 250
Is it more profitable to run 10TB on a single wallet, or run 5TB each on two different wallets?

Exactly the same.

Quote
would it increase my chances of finding shares in a pool.. or blocks going solo?

When going solo you get the same amount of coins - on average. With just a few TB its more like gambling, but with 10TB you can give it a try.

https://bchain.info/BURST/tools/calculator

10TB is about 2.5 blocks per day - with current diff.
legendary
Activity: 1036
Merit: 1000
https://bmy.guide
Is it more profitable to run 10TB on a single wallet, or run 5TB each on two different wallets? would it increase my chances of finding shares in a pool.. or blocks going solo?
legendary
Activity: 1036
Merit: 1000
https://bmy.guide
Could we use an usb external drive/ drives?

Of cause you can. USB 3.0 drives are best, but USB 2.0 is also fine.

With enough ram you might want to run a separate miner for each drive.

Friend as I am to mine that currency with the open wallet as I do now?

Ill release the final version soon, be patient  Wink
 Ok Smiley thx

CAN SOMEONE HELP ME HuhHuh??

you need to have the wallet server running to mine. you can generate without the wallet running.

edit: but have a miner going on each drive that is connected to the same computer (localhost) the wallet is running on
sr. member
Activity: 280
Merit: 250
81kk noonces?! it's more than 19tb

i didnt know what i was doing... look at the sizes they are barely full but they will still work. right?

Yes they work. They don't even overlap. If you get some deadlines you can ignore the warnings - they just tell you the file is not complete.
sr. member
Activity: 311
Merit: 250
Hix
legendary
Activity: 1971
Merit: 1036
Ill release the final version soon, be patient  Wink
 Ok Smiley thx
legendary
Activity: 1036
Merit: 1000
https://bmy.guide
81kk noonces?! it's more than 19tb

i didnt know what i was doing... look at the sizes they are barely full but they will still work. right?
newbie
Activity: 16
Merit: 0
81kk noonces?! it's more than 19tb
sr. member
Activity: 358
Merit: 251
hello, this started happening for one of my plots using the C+ generator..

can anyone tell what happened?

Have you finished plotting the files? What size are they? Looks like the miner cant read them, at least not completely.

i still creating that plots but i get valid share with that c++ generator
legendary
Activity: 1036
Merit: 1000
https://bmy.guide
hello, this started happening for one of my plots using the C+ generator..

can anyone tell what happened?

Have you finished plotting the files? What size are they? Looks like the miner cant read them, at least not completely.





the one selected is still being generated, it just went through two blocks without that error, i got scared i wastes hours of plotting. is that normal for it to error like that ?
sr. member
Activity: 280
Merit: 250
hello, this started happening for one of my plots using the C+ generator..

can anyone tell what happened?

Have you finished plotting the files? What size are they? Looks like the miner cant read them, at least not completely.
legendary
Activity: 1036
Merit: 1000
https://bmy.guide
hello, this started happening for one of my plots using the C+ generator..





can anyone tell what happened?
sr. member
Activity: 311
Merit: 250
Could we use an usb external drive/ drives?

Of cause you can. USB 3.0 drives are best, but USB 2.0 is also fine.

With enough ram you might want to run a separate miner for each drive.

Friend as I am to mine that currency with the open wallet as I do now?
sr. member
Activity: 280
Merit: 250
Could we use an usb external drive/ drives?

Of cause you can. USB 3.0 drives are best, but USB 2.0 is also fine.

With enough ram you might want to run a separate miner for each drive.
legendary
Activity: 1512
Merit: 1000
quarkchain.io
Could we use an usb external drive/ drives?
hero member
Activity: 644
Merit: 500
How do I mine will open the wallet, as I do now?
can someone help me

Invest.
In the long run you will get rewarded.
I remember when some user here was mining millions of litecoin and then sent after 3 months for some Penny.  Grin Grin
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
ok guys im confused.it doesnt take much for me.lol.i have not done any pool mining yet.all my plots are solo.what do i need to do to mine v2 pool.
1. Download pocminer_pool DONE
2. move your plots folder from pocminer_v1 to pocminer_pool DONE
3. In the mine.bat file, edit the poolip to http://178.62.39.204:8121 DONE
4. Go to http://localhost:8125/rewardassignment.html DONE
5. At the bottom fill in your passphrase, and put BURST-8NZ9-X6AX-72BK-2KFM2 as recipient and submit. This will have a fee of 1 DONE
6. After 4 confirms, your generate address will show up in http://178.62.39.204:8121/users DONE
7. run mine.bat DONE

And I get this....

Quote
N:\pocminer_v1>C:\Windows\SysWOW64\java -cp pocminer_pool.jar;lib/*;lib/akka/*;l
ib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://198.199.103.
145:8121
[default-akka.actor.default-dispatcher-3] INFO org.eclipse.jetty.util.log - Logg
ing initialized @682ms
{
  "height": "8318",
  "generationSignature": "9e40ec57d14c413c6b90ebc5aa5722b257a09859336cc7fd5247af
0c1a2ddfb0",
  "baseTarget": "11965749",
  "targetDeadline": "50000"
}
Error reading file: 4651495086655359966_25000000_3160000_1000
No valid shares to submit to pool

How do I fix this?

So I had the IP wrong. I changed it to the correct one but still no luck. Seems to have made a bigger problem. Pool Admin or users please help. Getting frustrated.

Quote
N:\pocminer_v1>C:\Windows\SysWOW64\java -cp pocminer_pool.jar;lib/*;lib/akka/*;l
ib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.20
4:8121
[default-akka.actor.default-dispatcher-3] INFO org.eclipse.jetty.util.log - Logg
ing initialized @1132ms
{
  "height": "8323",
  "generationSignature": "973af18c4371a38f1e9d2f1f35f07f92fc5381d57ecbcaab3c4fbc
5d7cf59731",
  "baseTarget": "11872832",
  "targetDeadline": "75000"
}
{
  "height": "8324",
  "generationSignature": "26dfbfe37a60223013bef42144eb18d6a0def986a871af7af23fc8
a5a6c53da9",
  "baseTarget": "11607410",
  "targetDeadline": "75000"
}
Error reading file: 4651495086655359966_25000000_3160000_1000
No valid shares to submit to pool
Error reading file: 4651495086655359966_25000000_3160000_1000
[INFO] [09/03/2014 16:30:06.133] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c/$a] Message [pocminer_pool.Miner$msgReadFlush] from Actor[
akka://default/user/$a/$c#-1346312748] to Actor[akka://default/user/$a/$c/$a#850
786242] was not delivered. [1] dead letters encountered. This logging can be tur
ned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akk
a.log-dead-letters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.133] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.Miner$msgSendResults] from Actor[a
kka://default/deadLetters] to Actor[akka://default/user/$a/$c#-1346312748] was n
ot delivered. [2] dead letters encountered. This logging can be turned off or ad
justed with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-le
tters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.Miner$msgSendResults] from Actor[a
kka://default/deadLetters] to Actor[akka://default/user/$a/$c#-1346312748] was n
ot delivered. [3] dead letters encountered. This logging can be turned off or ad
justed with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-le
tters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.Miner$msgSendResults] from Actor[a
kka://default/deadLetters] to Actor[akka://default/user/$a/$c#-1346312748] was n
ot delivered. [4] dead letters encountered. This logging can be turned off or ad
justed with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-le
tters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.ScoopReader$msgScoopChunk] from Ac
tor[akka://default/user/$a/$c/$a#850786242] to Actor[akka://default/user/$a/$c#-
1346312748] was not delivered. [5] dead letters encountered. This logging can be
 turned off or adjusted with configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.ScoopReader$msgScoopChunk] from Ac
tor[akka://default/user/$a/$c/$a#850786242] to Actor[akka://default/user/$a/$c#-
1346312748] was not delivered. [6] dead letters encountered. This logging can be
 turned off or adjusted with configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.ScoopReader$msgScoopChunk] from Ac
tor[akka://default/user/$a/$c/$a#850786242] to Actor[akka://default/user/$a/$c#-
1346312748] was not delivered. [7] dead letters encountered. This logging can be
 turned off or adjusted with configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.ScoopReader$msgScoopChunk] from Ac
tor[akka://default/user/$a/$c/$a#850786242] to Actor[akka://default/user/$a/$c#-
1346312748] was not delivered. [8] dead letters encountered. This logging can be
 turned off or adjusted with configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.ScoopReader$msgScoopChunk] from Ac
tor[akka://default/user/$a/$c/$a#850786242] to Actor[akka://default/user/$a/$c#-
1346312748] was not delivered. [9] dead letters encountered. This logging can be
 turned off or adjusted with configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
[INFO] [09/03/2014 16:30:06.134] [default-akka.actor.default-dispatcher-3] [akka
://default/user/$a/$c] Message [pocminer_pool.ScoopReader$msgScoopChunk] from Ac
tor[akka://default/user/$a/$c/$a#850786242] to Actor[akka://default/user/$a/$c#-
1346312748] was not delivered. [10] dead letters encountered, no more dead lette
rs will be logged. This logging can be turned off or adjusted with configuration
 settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
Jump to: