question
is it necessary to run wallet when mining on pool v2 ?
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1022. (Read 2170889 times)
September 04, 2014, 02:55:48 AM
September 04, 2014, 02:42:59 AM
September 04, 2014, 02:40:55 AM
Hi, I hope this was not answered before as it's hard for me to follow the complete thread at the current pace...
Regarding mining on the pool (v2):
The miner submits the found share(s) only AFTER it has finished checking all his plots, right?
If a new block arrives after he found a share, but before he could submit it (=reading was not finished), he will submit this/these share(s) after completing the run for the new block.
Are they credited as valid shares by the pool or are they discared as "stale"?
Does the result "share/s received" really only mean "received" or also "accepted and counted"?
Would be good to know as this happens quite often with larger amounts of plot data and not too performant miners.
I tried to figure it out by watching the sharecount in the pool stats, but it's quite hard because of PPLNS.
Thanks!
Regarding mining on the pool (v2):
The miner submits the found share(s) only AFTER it has finished checking all his plots, right?
If a new block arrives after he found a share, but before he could submit it (=reading was not finished), he will submit this/these share(s) after completing the run for the new block.
Are they credited as valid shares by the pool or are they discared as "stale"?
Does the result "share/s received" really only mean "received" or also "accepted and counted"?
Would be good to know as this happens quite often with larger amounts of plot data and not too performant miners.
I tried to figure it out by watching the sharecount in the pool stats, but it's quite hard because of PPLNS.
Thanks!
These actually haven't been asked before.
The block height is sent with each share, and stales are discarded.
share/s received only confirms that data was sucessfully received and dumped into the processing queue
If you often have difficulty reading through everything, you should try using larger stagger sizes or using dcct's optimize tool. You will get higher read speeds when using higher stagger sizes.
September 04, 2014, 02:36:51 AM
Hi Dev!
Have you seen on #Bittrex (irc.freenode.net)?
(08:28) bittrex-rami: bittrex-richie has the burstcoin dev contacted you? How's the integration going on?
(08:29) problems with the code?
(08:41) <@bittrex-richie> Burst_: its not a problemw ith the code
(08:41) <@bittrex-richie> Burst_: we were just hoping they suportd the new NXT model which they dont
(08:42) ah
(08:42) so i guess it would be still a while then
(08:44) bittrex-richie: so i guess it would still take some time to get things worked out?
(08:51) <@bittrex-richie> shrug.. not sure yet..
Please go on irc and speak with them! It's the only way to contact them quickly! If they'll ask you BTC for adding Burst no problem, but first you have to know what they want! Community is here waiting for you! There are lot of big wallet dumping their coin on c-cex and no buy support.. Don't let your coin die!
Have you seen on #Bittrex (irc.freenode.net)?
(08:28)
(08:29)
(08:41) <@bittrex-richie> Burst_: its not a problemw ith the code
(08:41) <@bittrex-richie> Burst_: we were just hoping they suportd the new NXT model which they dont
(08:42)
(08:42)
(08:44)
(08:51) <@bittrex-richie> shrug.. not sure yet..
Please go on irc and speak with them! It's the only way to contact them quickly! If they'll ask you BTC for adding Burst no problem, but first you have to know what they want! Community is here waiting for you! There are lot of big wallet dumping their coin on c-cex and no buy support.. Don't let your coin die!
September 04, 2014, 02:18:19 AM
[WARN] [09/04/2014 15:16:37.428] [default-akka.actor.default-dispatcher-8] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:16:47.431] [default-akka.actor.default-dispatcher-4] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:16:57.424] [default-akka.actor.default-dispatcher-6] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:17:07.441] [default-akka.actor.default-dispatcher-4] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:17:17.429] [default-akka.actor.default-dispatcher-7] [akka
://default/user/$a/$b] null
i got this when trying to mine. I am using pool v2 , plotting and mining at the same time.
://default/user/$a/$b] null
[WARN] [09/04/2014 15:16:47.431] [default-akka.actor.default-dispatcher-4] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:16:57.424] [default-akka.actor.default-dispatcher-6] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:17:07.441] [default-akka.actor.default-dispatcher-4] [akka
://default/user/$a/$b] null
[WARN] [09/04/2014 15:17:17.429] [default-akka.actor.default-dispatcher-7] [akka
://default/user/$a/$b] null
i got this when trying to mine. I am using pool v2 , plotting and mining at the same time.
September 04, 2014, 02:10:31 AM
Hi, I hope this was not answered before as it's hard for me to follow the complete thread at the current pace...
Regarding mining on the pool (v2):
The miner submits the found share(s) only AFTER it has finished checking all his plots, right?
If a new block arrives after he found a share, but before he could submit it (=reading was not finished), he will submit this/these share(s) after completing the run for the new block.
Are they credited as valid shares by the pool or are they discared as "stale"?
Does the result "share/s received" really only mean "received" or also "accepted and counted"?
Would be good to know as this happens quite often with larger amounts of plot data and not too performant miners.
I tried to figure it out by watching the sharecount in the pool stats, but it's quite hard because of PPLNS.
Thanks!
Regarding mining on the pool (v2):
The miner submits the found share(s) only AFTER it has finished checking all his plots, right?
If a new block arrives after he found a share, but before he could submit it (=reading was not finished), he will submit this/these share(s) after completing the run for the new block.
Are they credited as valid shares by the pool or are they discared as "stale"?
Does the result "share/s received" really only mean "received" or also "accepted and counted"?
Would be good to know as this happens quite often with larger amounts of plot data and not too performant miners.
I tried to figure it out by watching the sharecount in the pool stats, but it's quite hard because of PPLNS.
Thanks!
September 04, 2014, 02:05:35 AM
Got 3.4 TB I'm was able to get 3.5K BURST per day so at current rate of 0.00000650 BTC will be able to get 0.02275 BTC per day. Most profitable coin I'm ever mined. 
the diff may be rise again, but even at 0.01 you would makes a good profit
actually i don't care much i come late to this, i'm waiting for the next poc coin
September 04, 2014, 01:40:56 AM
September 04, 2014, 01:40:07 AM
You only need one client running. It is listening on 127.0.0.1:8125 and every miner can connect to that client.
What you may need is one miner per drive.
If I want to connect from another computer what should I change in config file?
# Hosts from which to allow http/json API requests, if enabled.
nxt.allowedBotHosts=
i did'nt manage to add whole subnets and did'nt wanted to loose time for reasearch so i simply added my miner ips seperated by a semicolon.
September 04, 2014, 01:35:34 AM
Question for data storage specialist
I have network array EMC VNX3100 with about 14TB of storage. Is it good idea to share it to VMware esxi storage adapter via NFS and mount it to for example ubuntu virtual machine and use it for burst ? How many RAM i have to allocate do 3TB plot under linux ?
vms stored in esxi on nfs wont run quite well. but if you really want to store the machine on network you can export the storage as iscsi target and add this to the esxi storage pool.I have network array EMC VNX3100 with about 14TB of storage. Is it good idea to share it to VMware esxi storage adapter via NFS and mount it to for example ubuntu virtual machine and use it for burst ? How many RAM i have to allocate do 3TB plot under linux ?
it would be much more efficient to run your ubuntu from local storage and only mount your mining or plot folder from the emc using nfs.
September 04, 2014, 01:31:35 AM
Alright, have a v2 pool running at http://178.62.39.204:8121/
The v1 pool will be converted to v2 in a day or 2, but setting up the migration would have delayed this release, and only running that one on v2 could result in a dangerously high portion of network hashrate on one pool, so it's better to split it for now anyway.
Usage:
You will need the pocminer_pool posted previously when the v1 pool was launched: https://mega.co.nz/#!7hwHQJLZ!-waC7CwWeMStkdAwjEVbew1fN_YqeZDRWMWfCylaNPo
Reward reassignment has not been integrated into the wallet gui yet, however an extra html page was included in the 1.0.3 release that you can use. http://localhost:8125/rewardassignment.html
Below where it says set reward recipient, fill in your passphrase, and put the pool's burst- address where it says recipient, and submit. This will have a fee of 1 Burst. It should come up with a page of a bunch of details you won't care about if everything is good.
Once the transaction is in a valid block + 3 confirms, you should be able to use the pool. You can check the users list on the pool to make sure that your numerical account id is there(your generate address)
Edit the pool's ip/port into the run_mine file for pocminer_pool.
Rename or move your passphrases.txt file, since pocminer_pool will try to solo instead if it sees a correct passphrase for those plots.
Starting target deadline is 75k
PPLNS
When your balance hits 500 burst you get paid.
All users who have not upgraded to 1.0.3 are now on a bad fork
V2 Pool allows you to mine with your solo plots. You do NOT have to regenerate plots if you have solo plots. v1 pool users can keep mining without doing anything. the v1 -> v2 migration for v1 pool users will be transparent to them, and not require them to do anything.
The v1 pool will be converted to v2 in a day or 2, but setting up the migration would have delayed this release, and only running that one on v2 could result in a dangerously high portion of network hashrate on one pool, so it's better to split it for now anyway.
Usage:
You will need the pocminer_pool posted previously when the v1 pool was launched: https://mega.co.nz/#!7hwHQJLZ!-waC7CwWeMStkdAwjEVbew1fN_YqeZDRWMWfCylaNPo
Reward reassignment has not been integrated into the wallet gui yet, however an extra html page was included in the 1.0.3 release that you can use. http://localhost:8125/rewardassignment.html
Below where it says set reward recipient, fill in your passphrase, and put the pool's burst- address where it says recipient, and submit. This will have a fee of 1 Burst. It should come up with a page of a bunch of details you won't care about if everything is good.
Once the transaction is in a valid block + 3 confirms, you should be able to use the pool. You can check the users list on the pool to make sure that your numerical account id is there(your generate address)
Edit the pool's ip/port into the run_mine file for pocminer_pool.
Rename or move your passphrases.txt file, since pocminer_pool will try to solo instead if it sees a correct passphrase for those plots.
Starting target deadline is 75k
PPLNS
When your balance hits 500 burst you get paid.
All users who have not upgraded to 1.0.3 are now on a bad fork
V2 Pool allows you to mine with your solo plots. You do NOT have to regenerate plots if you have solo plots. v1 pool users can keep mining without doing anything. the v1 -> v2 migration for v1 pool users will be transparent to them, and not require them to do anything.
but the pool v1's target deadline is still 50K
September 04, 2014, 01:23:55 AM
Oh GOD! i have seen my nodes for 300sat...I'm gonna buy them back,this time i will be a holder
September 04, 2014, 01:15:34 AM
Some scumbag hacked into my account and withdrew my funds, apparently my passphrase is too weak. Is there any way for me to change passphrase without having to replot my entire Hard Drive? 
can someone please help me
I don't think you got hacked. Its hard to crack a 12 work passphrase. What does it say under the transactions tab?
It says that I withdrew some funds out of my account, but I'm 100% I never did, at least not the address specified. And it shows the address where they were transferred to and I don't recognize it.
you using any programs that work with burst that you downloaded?
September 04, 2014, 01:13:54 AM
Some scumbag hacked into my account and withdrew my funds, apparently my passphrase is too weak. Is there any way for me to change passphrase without having to replot my entire Hard Drive?
can someone please help me
I don't think you got hacked. Its hard to crack a 12 work passphrase. What does it say under the transactions tab?
It says that I withdrew some funds out of my account, but I'm 100% I never did, at least not the address specified. And it shows the address where they were transferred to and I don't recognize it.
September 04, 2014, 01:12:46 AM
Some scumbag hacked into my account and withdrew my funds, apparently my passphrase is too weak. Is there any way for me to change passphrase without having to replot my entire Hard Drive?
can someone please help me
The answer is no.
September 04, 2014, 01:11:41 AM
Some scumbag hacked into my account and withdrew my funds, apparently my passphrase is too weak. Is there any way for me to change passphrase without having to replot my entire Hard Drive?
can someone please help me
I don't think you got hacked. Its hard to crack a 12 work passphrase. What does it say under the transactions tab?
September 04, 2014, 01:09:56 AM
Some scumbag hacked into my account and withdrew my funds, apparently my passphrase is too weak. Is there any way for me to change passphrase without having to replot my entire Hard Drive?
can someone please help me
September 04, 2014, 01:08:16 AM
You only need one client running. It is listening on 127.0.0.1:8125 and every miner can connect to that client.
What you may need is one miner per drive.
If I want to connect from another computer what should I change in config file?
September 04, 2014, 01:08:02 AM
Got 3.4 TB I'm was able to get 3.5K BURST per day so at current rate of 0.00000650 BTC will be able to get 0.02275 BTC per day. Most profitable coin I'm ever mined.
Yup. And the price should get better
September 04, 2014, 12:53:58 AM
Got 3.4 TB I'm was able to get 3.5K BURST per day so at current rate of 0.00000650 BTC will be able to get 0.02275 BTC per day. Most profitable coin I'm ever mined.
Jump to: