Hello, and attention all miners of burstpool.ddns.net
Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.
NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.
--Irotniga
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 720. (Read 2171056 times)
September 27, 2014, 12:25:59 AM
September 27, 2014, 12:21:06 AM
Am I correct in saying that a passphrases.txt is not needed in a folder when pool mining? In particular, pool mining on http://burstpool.ddns.net/ with 'Burst Mining System'?
That being said, what is the best way to track that my shares are properly getting submitted to the pool and such?
I like BURST and I have several different miners hitting it. But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out. There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!
Thanks all!
That being said, what is the best way to track that my shares are properly getting submitted to the pool and such?
I like BURST and I have several different miners hitting it. But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out. There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!
Thanks all!
No, remove passphrase for pool mining.
September 27, 2014, 12:13:01 AM
Am I correct in saying that a passphrases.txt is not needed in a folder when pool mining? In particular, pool mining on http://burstpool.ddns.net/ with 'Burst Mining System'?
That being said, what is the best way to track that my shares are properly getting submitted to the pool and such?
I like BURST and I have several different miners hitting it. But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out. There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!
Thanks all!
That being said, what is the best way to track that my shares are properly getting submitted to the pool and such?
I like BURST and I have several different miners hitting it. But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out. There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!
Thanks all!
September 26, 2014, 11:47:30 PM
New client Burst 1.1.3
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
Do we need to re-download the blockchain? or the one I have from the old wallet will work fine?
Old blockchain is fine, just move the folder over.
September 26, 2014, 11:45:30 PM
New client Burst 1.1.3
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
Do we need to re-download the blockchain? or the one I have from the old wallet will work fine?
September 26, 2014, 11:28:55 PM
New client Burst 1.1.3
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
September 26, 2014, 11:03:25 PM
I just noticed that http://coinmarketcap.com is now properly showing the market cap for burst. Burst is ranked exactly 100 right now.
September 26, 2014, 10:58:04 PM
ok, i will make optimization, but after we dont have any critical issue first, i want to make this miner can read any weird and funky plot first
Can you also implement log file generation so that we can check when the miner is crashed & find out the possible reason behind that crash ?
September 26, 2014, 09:22:39 PM
Native C++ Miner Update 1.1 R4
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
and also, github automatically give the project website : http://uraymeiviar.github.io/burst-miner/
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
- capable to read large stagger plot, with manual limit option on memory usage
- Fix thread race condition, which reported to less nonce read
- add option of buffer size (MB) in mining.conf to limit memory usage
and also, github automatically give the project website : http://uraymeiviar.github.io/burst-miner/
So, is this only for pool mining at your pool? Or can this solo mine also?
September 26, 2014, 09:19:42 PM
I had this issue but changing the drive letter to lowercase fixed it. I guess tolower(); wasn't used?
It doesn't take any change to me
I can not find the problem, because the miner is working fine for me with a pool:
Code:
miner.exe pool burstpool.ddns.net 8124 C:\pocminer_v1-burst\plots\ D:\pocminer_v1-burst\plots\ E:\pocminer_v1-burst\plots\ G:\pocminer_v1-burst\plots\ H:\pocminer_v1-burst\plots\ F:\plots\
Note:
drive letter upper case.
No deadlines because i did not set reward assignment, but miner sent shares and get mining info from pool (trying port 80 and 8124)
September 26, 2014, 08:41:01 PM
Does anyone know how much BTR you need to get 2 votes per hour on bter.com?
September 26, 2014, 08:16:02 PM
https://bter.com/voting#BURST
Pleace voite!
Already - 2,317 votes and 17 place.
Pleace voite!
Already - 2,317 votes and 17 place.
September 26, 2014, 07:03:49 PM
I had this issue but changing the drive letter to lowercase fixed it. I guess tolower(); wasn't used?
It doesn't take any change to me
September 26, 2014, 06:15:18 PM
I also have the same problem.
Windows 8.1 64Bits
Windows 8.1 64Bits
@Uray and @Blago:
Guys obviously I have some regional issue with connecting the remote IP using R3/R4 Uray's miners such an issue I have with the Blago's miner:
My settings at R4 miner in the conf file are:
{
"poolUrl" : "burstpool.ddns.net",
"submissionMaxDelay" : 30,
"submissionMaxRetry" : 3,
"socketTimeout" : 60,
"maxBufferSizeMB" : 2048,
"plots" :
[
"D:\\BURST\\gpuPlotGenerator-bin-win-x86-2.1.1\\plots"
]
}
It doesn't matter if I set buffersize 64 / 2048 / 4096.. Also doesn't matter if I set port (8124 for DDNS pool) or not (80 port). I tried with firewall absolutely OFF- same situation.
I have different account on other PCs with different IPs and location , the accounts are for both Uray's pools - same issue.
Let me show you some screenshots:
https://i.imgur.com/3AEn7w2.jpg
https://i.imgur.com/yWGaBDF.jpg
I'm still using JAVA miner without any issue , but I have to start different miner for every single HDD ploted...
Guys obviously I have some regional issue with connecting the remote IP using R3/R4 Uray's miners such an issue I have with the Blago's miner:
My settings at R4 miner in the conf file are:
{
"poolUrl" : "burstpool.ddns.net",
"submissionMaxDelay" : 30,
"submissionMaxRetry" : 3,
"socketTimeout" : 60,
"maxBufferSizeMB" : 2048,
"plots" :
[
"D:\\BURST\\gpuPlotGenerator-bin-win-x86-2.1.1\\plots"
]
}
It doesn't matter if I set buffersize 64 / 2048 / 4096.. Also doesn't matter if I set port (8124 for DDNS pool) or not (80 port). I tried with firewall absolutely OFF- same situation.
I have different account on other PCs with different IPs and location , the accounts are for both Uray's pools - same issue.
Let me show you some screenshots:
https://i.imgur.com/3AEn7w2.jpg
https://i.imgur.com/yWGaBDF.jpg
I'm still using JAVA miner without any issue , but I have to start different miner for every single HDD ploted...
well, for one, the burstpool.ddns.net is port 8124, so you have to use burstpool.ddns.net:8124
The other pool I can't help you, but that should get you working on burstpool.ddns.net.
I had this issue but changing the drive letter to lowercase fixed it. I guess tolower(); wasn't used?
September 26, 2014, 05:48:21 PM
I use POC_Pool miner and keep getting this error spuraticly and not sure why. Any help?
[INFO] [09/25/2014 15:16:55.970] [default-akka.actor.default-dispatcher-2] [akka://default/user/$a/$c] Message [pocminer_pool.Miner$msgSendResults] from Actor[akka://default/deadLetters] to Actor[akka://default/user/$a/$c#-1365268779] was not delivered. [1] 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'.
my bat file:
C:\Windows\SysWOW64\java -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121
[INFO] [09/25/2014 15:16:55.970] [default-akka.actor.default-dispatcher-2] [akka://default/user/$a/$c] Message [pocminer_pool.Miner$msgSendResults] from Actor[akka://default/deadLetters] to Actor[akka://default/user/$a/$c#-1365268779] was not delivered. [1] 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'.
my bat file:
C:\Windows\SysWOW64\java -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121
September 26, 2014, 05:07:44 PM
is it possible see the deadline that found the block in the block expoler?
You can infer it with reasonable accuracy from the delay since the reporting of the previous block.
see that small text below tx amount
Round Time ...
its the deadline for that block
September 26, 2014, 05:05:02 PM
If my hdd is 1tb but it show up as 931gb, does that mean i shouldn't go over 931gb creating plots?
add: must be, it's that macintosh is different, it's 1tb in bytes.
add: must be, it's that macintosh is different, it's 1tb in bytes.
September 26, 2014, 04:34:48 PM
well, for one, the burstpool.ddns.net is port 8124, so you have to use burstpool.ddns.net:8124
The other pool I can't help you, but that should get you working on burstpool.ddns.net.
Trust me I already tried 8124 port , I wrote it above where I specify the issue
EDIT: I can run JAVA miner on port 80 at DDNS pool
You must use dcct or uray miner on this pool
September 26, 2014, 04:33:40 PM
This is an idiot-proof guide (hopefully) for pool mining at http://burst-pool.cryptoport.io/ using windows 64-bit, with pictures! I got stuck a few times with setting it up, so I have included a few details and pictures that I hope will help others.
First install or update Java. This may involve removing older versions. http://www.java.com/en/download/help/index_installing.xml . This should put java in C:\Windows\SysWOW64.
http://i59.tinypic.com/wcib6e.jpg
Install or update flash player. You will need this to copy your account ID or numeric account ID in the BURST wallet. http://get.adobe.com/flashplayer/
Download the most recent version of the BURST wallet from the first page of https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923.
Download the pool miner at http://uraymeiviar.github.io/burst-miner/.
Extract these two files (the wallet and the miner) onto the drive you’re going to be using.
Go the the BURST wallet folder, run the batch file run.bat. A command prompt window should open and run for a minute until you get a line that says “INFO: Burst server 1.1.2 started successfully” (or whichever Burst server is the most recent version). If the window closes, it’s most likely a problem with Java, go back and make sure it’s installed correctly. You can edit the batch file run.bat and put the word ‘pause’ in a second line to keep the window open and see what the error is.
http://i62.tinypic.com/f9nio3.jpg
In the wallet folder, click on the BURST wallet internet shortcut. Create a new account. Wait for the blockchain to download completely. It may take a while, maybe an hour?
Go to the burstcoin faucet at http://burstfaucet.com/ and put in your wallet address, which should look something like BURST-NSRE-4KG9-6LZ4-ETTG3. Fill out the captcha and you should receive 2 BURST. Alternatively, if you know someone who has BURST have them send you two BURST coins. Wait for the coins to post to your balance, then send 1 BURST to someone. ( You can use my address, BURST-NSRE-4KG9-6LZ4-ETTG3, or the pool’s wallet address, BURST-L28E-WSYC-F4N3-B82AC, if you don’t know of anyone else with an address.)
http://i57.tinypic.com/20f7ts8.jpg
Go to the Burst pool miner folder. There should be 4 windows batch files.
http://i59.tinypic.com/2h4j3fd.jpg
First, edit the four batch files so that they show the location of java in SYSWOW64. The first part of each of them should read C:\Windows\SysWOW64\java at the very beginning.
Go the the BURST wallet, click on your burst address and click ‘Copy Numeric Account ID’. If you don’t get the drop-down it is most likely because your flash player isn’t working right.
http://i60.tinypic.com/2r4snzm.jpg
You can also get the account ID number by going to the pool miner folder, creating a text file called ‘passphrases.txt’ and entering the passphrase for your wallet, then double-clicking on the run_dump_address.bat. It will create a file called address.txt with your numeric account ID in it.
Now go back to the run_generate.bat batch file. This is the file that generates your plots. Edit it to:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate [numeric account ID] 0 xxxxxx 1000 y
where ‘xxxxx’ is the number of nonces to generate. What this refers to is how much disk space you’re going to mine with. It is about 4000 per Gb, so if you’re using 1000 Gb, it will be 4000000. ‘y’ is the number of threads to use. There are a few other changes that CAN be made to this, but it only going to run once, so as long as it works you shouldn’t worry about it too much.
In the pool miner folder, double-click on run.bat. A window will open and close. Now double-click on run_generate.bat and a command window will open and start generating plots. It should start to spit out lines like so:
Generating from nonce: 0
Writing from nonce:0
Generating from nonce: 1000
Writing from nonce:1000
This means you are generating plots. Let it run all the way through, it will stop at the number of nonces you told it to generate and close. It will take a very long time, hours and hours. One of my computers took 36 hours to finish.
If you are running another miner on your graphics cards (scrypt, x-11, blake, etc.), that miner might slow down until you are finished generating plots. Don't worry, it will speed up again after the plots are finished generating.
Now to set up the pool.
Go to http://127.0.0.1:8125/rewardassignment.html. . Under ‘Set reward recipient:’ in the ‘passphrase’ box enter your passphrase. In the ‘recipient’ box enter 10745596296835956940. (The instructions for this are at http://burst-pool.cryptoport.io/howto.html ) If you did not wait for the blockchain to finish downloading in the wallet, then it won’t work. Wait for it to finish and try again.
Now go back to the pool miner folder. Edit the run_mine.bat batch file to:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner mine "http://burst-pool.cryptoport.io:80"
Now double-click on the run_mine.bat batch file and it should open a command window and start to run. It should start displaying lines that look like:
[“baseTarget”:”4045283”,”height”:”16561”,”generation signature”:4e8g8gfg2fe6f204g82c9e7gh7aa87c7650g7588d9b3gh4f782219va3546c67a”]
and occasionally give you a result about submitting shares. It may give you an error about submitting shares at first, just give it a while and it should start successfully submitting them.
When it starts successful submitting shares, you can confirm that you are mining by going to http://burst-pool.cryptoport.io/ and searching for your BURST account ID (BURST-xxxx-xxxx-xxxxx) using ctrl-f. Again, it might take a few rounds, so give it a little time if you don’t find it.
Note: You can start mining without waiting for the plots to finish generating, you'll just have a lower chance of getting anything for it.
What my four batch files look like:
run.bat
C:\Windows\SysWOW64\java -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner %*
run_dump_address.bat
C:\Windows\SysWOW64\java -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner dumpaddr >address.txt
Run_generate:
C:\Windows\SysWOW64\java -Xmx1024m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate 13867756655654712537 0 3200000 1000 3
run_min.bat:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner mine "http://burst-pool.cryptoport.io:80"
Many thanks to KSpinner, who wrote the first guide I went off of at https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923.msg8298999#msg8298999 and to billyboy402 at youtube who made a video at https://www.youtube.com/watch?v=oYlf1xFTHvs
Feel free to tip them or to tip me. 1 BURST is currently only $.0006, so it’s not that much. Have fun mining!
my BURST address: NSRE-4KG9-6LZ4-ETTG3
****EDIT:***
I wasn't getting anything off of two of my computers with the stagger only at 10. I made a change to the stagger and it seems to be working better. The changed was made to the run_generate.bat file, I changed '10' to '1000' so that my run_generate.bat was read as: C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate [numeric account ID] 0 xxxxxx 1000 y. It seems to work better.
First install or update Java. This may involve removing older versions. http://www.java.com/en/download/help/index_installing.xml . This should put java in C:\Windows\SysWOW64.
http://i59.tinypic.com/wcib6e.jpg
Install or update flash player. You will need this to copy your account ID or numeric account ID in the BURST wallet. http://get.adobe.com/flashplayer/
Download the most recent version of the BURST wallet from the first page of https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923.
Download the pool miner at http://uraymeiviar.github.io/burst-miner/.
Extract these two files (the wallet and the miner) onto the drive you’re going to be using.
Go the the BURST wallet folder, run the batch file run.bat. A command prompt window should open and run for a minute until you get a line that says “INFO: Burst server 1.1.2 started successfully” (or whichever Burst server is the most recent version). If the window closes, it’s most likely a problem with Java, go back and make sure it’s installed correctly. You can edit the batch file run.bat and put the word ‘pause’ in a second line to keep the window open and see what the error is.
http://i62.tinypic.com/f9nio3.jpg
In the wallet folder, click on the BURST wallet internet shortcut. Create a new account. Wait for the blockchain to download completely. It may take a while, maybe an hour?
Go to the burstcoin faucet at http://burstfaucet.com/ and put in your wallet address, which should look something like BURST-NSRE-4KG9-6LZ4-ETTG3. Fill out the captcha and you should receive 2 BURST. Alternatively, if you know someone who has BURST have them send you two BURST coins. Wait for the coins to post to your balance, then send 1 BURST to someone. ( You can use my address, BURST-NSRE-4KG9-6LZ4-ETTG3, or the pool’s wallet address, BURST-L28E-WSYC-F4N3-B82AC, if you don’t know of anyone else with an address.)
http://i57.tinypic.com/20f7ts8.jpg
Go to the Burst pool miner folder. There should be 4 windows batch files.
http://i59.tinypic.com/2h4j3fd.jpg
First, edit the four batch files so that they show the location of java in SYSWOW64. The first part of each of them should read C:\Windows\SysWOW64\java at the very beginning.
Go the the BURST wallet, click on your burst address and click ‘Copy Numeric Account ID’. If you don’t get the drop-down it is most likely because your flash player isn’t working right.
http://i60.tinypic.com/2r4snzm.jpg
You can also get the account ID number by going to the pool miner folder, creating a text file called ‘passphrases.txt’ and entering the passphrase for your wallet, then double-clicking on the run_dump_address.bat. It will create a file called address.txt with your numeric account ID in it.
Now go back to the run_generate.bat batch file. This is the file that generates your plots. Edit it to:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate [numeric account ID] 0 xxxxxx 1000 y
where ‘xxxxx’ is the number of nonces to generate. What this refers to is how much disk space you’re going to mine with. It is about 4000 per Gb, so if you’re using 1000 Gb, it will be 4000000. ‘y’ is the number of threads to use. There are a few other changes that CAN be made to this, but it only going to run once, so as long as it works you shouldn’t worry about it too much.
In the pool miner folder, double-click on run.bat. A window will open and close. Now double-click on run_generate.bat and a command window will open and start generating plots. It should start to spit out lines like so:
Generating from nonce: 0
Writing from nonce:0
Generating from nonce: 1000
Writing from nonce:1000
This means you are generating plots. Let it run all the way through, it will stop at the number of nonces you told it to generate and close. It will take a very long time, hours and hours. One of my computers took 36 hours to finish.
If you are running another miner on your graphics cards (scrypt, x-11, blake, etc.), that miner might slow down until you are finished generating plots. Don't worry, it will speed up again after the plots are finished generating.
Now to set up the pool.
Go to http://127.0.0.1:8125/rewardassignment.html. . Under ‘Set reward recipient:’ in the ‘passphrase’ box enter your passphrase. In the ‘recipient’ box enter 10745596296835956940. (The instructions for this are at http://burst-pool.cryptoport.io/howto.html ) If you did not wait for the blockchain to finish downloading in the wallet, then it won’t work. Wait for it to finish and try again.
Now go back to the pool miner folder. Edit the run_mine.bat batch file to:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner mine "http://burst-pool.cryptoport.io:80"
Now double-click on the run_mine.bat batch file and it should open a command window and start to run. It should start displaying lines that look like:
[“baseTarget”:”4045283”,”height”:”16561”,”generation signature”:4e8g8gfg2fe6f204g82c9e7gh7aa87c7650g7588d9b3gh4f782219va3546c67a”]
and occasionally give you a result about submitting shares. It may give you an error about submitting shares at first, just give it a while and it should start successfully submitting them.
When it starts successful submitting shares, you can confirm that you are mining by going to http://burst-pool.cryptoport.io/ and searching for your BURST account ID (BURST-xxxx-xxxx-xxxxx) using ctrl-f. Again, it might take a few rounds, so give it a little time if you don’t find it.
Note: You can start mining without waiting for the plots to finish generating, you'll just have a lower chance of getting anything for it.
What my four batch files look like:
run.bat
C:\Windows\SysWOW64\java -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner %*
run_dump_address.bat
C:\Windows\SysWOW64\java -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner dumpaddr >address.txt
Run_generate:
C:\Windows\SysWOW64\java -Xmx1024m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate 13867756655654712537 0 3200000 1000 3
run_min.bat:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner mine "http://burst-pool.cryptoport.io:80"
Many thanks to KSpinner, who wrote the first guide I went off of at https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923.msg8298999#msg8298999 and to billyboy402 at youtube who made a video at https://www.youtube.com/watch?v=oYlf1xFTHvs
Feel free to tip them or to tip me. 1 BURST is currently only $.0006, so it’s not that much. Have fun mining!
my BURST address: NSRE-4KG9-6LZ4-ETTG3
****EDIT:***
I wasn't getting anything off of two of my computers with the stagger only at 10. I made a change to the stagger and it seems to be working better. The changed was made to the run_generate.bat file, I changed '10' to '1000' so that my run_generate.bat was read as: C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate [numeric account ID] 0 xxxxxx 1000 y. It seems to work better.
September 26, 2014, 04:28:21 PM
1.) What is the purpose of optimizing plot files?
2.) How large plot files should be? Is it same to have 100 x 10Gb files or 10x100Gb files?
3.) Is there any limitation in size of plots miner could handle?
4.) Is there any need to specify RAM size while making plot files, and if so, what is optimal RAM size per machine for mining?
5.) Will it be "hard to hanlde" for miner if I put 4Gb ram in machine and 32Tb in same computer (8 x 4Tb hdds)?
Thank You.
2.) How large plot files should be? Is it same to have 100 x 10Gb files or 10x100Gb files?
3.) Is there any limitation in size of plots miner could handle?
4.) Is there any need to specify RAM size while making plot files, and if so, what is optimal RAM size per machine for mining?
5.) Will it be "hard to hanlde" for miner if I put 4Gb ram in machine and 32Tb in same computer (8 x 4Tb hdds)?
Thank You.
1. reducing disk seeks
2. It doesn't matter at all
3. Nope
4. the bigger the better
5. Yeah, probably
Will 8Gb than make it better? Should I re-optimize plot files again after memory upgrade?
Jump to: