|
Carnth
|
 |
June 17, 2011, 03:17:28 PM |
|
I was wondering how often most people payout?
I payout when I get above 1.5 BTC. This takes about 3 days for me. There have been a number of people paying out with small amounts (less than 0.10) and this has recently "clogged up" the transactions. In fact there are so many small payments floating around that it can take hours to get one confirmed. To every Bitcoin miner in the world: Please payout once per day or only when you have over 1.0 BTC. Please be patient. Mining is a steady and continuous process. Just sit back and let your miner(s) do its job. You can take a look at all current transactions (that have not been confirmed into a block) on this web page http://bitcoincharts.com/bitcoin/. Take a look at the number of "Unconfirmed Transactions." Now scroll to the bottom (the end of the "low priority" transactions) and see how long (in UTC time) some of those transactions have been hanging around. Transactions should be cleared within 1 to 3 blocks (45 Minuties max). But they are not, because there are so many of them. I cringe every time I see a payment for 0.01 BTC; I think to myself "Really? Oh come on!" Here's how to make sure your payment is a higher priority, so it gets through faster: - Get paid a larger amount. If everything else were equal, transactions with a large amount will be given a higher priority.
- Get paid with older bitcoins. Bitcoins that have been sitting around for a while (that have hundreds of confirmations) will get you even higher priority.
This does not always happen with pools because they are in the business of making new coins and paying miners. With so many transactions flying around most are "newer" coins. - Pay a transaction fee. This is the best way to get your transaction marked as the highest priority.
Mining pools do not do this because it cuts into the profits that the miners work for.
So, the only way we can influence the priority of the payment we get from pools is by the number of Bitcoins in the transaction. |
|
|
|
|
|
|
|
|
|
|
|
"In a nutshell, the network works like a distributed
timestamp server, stamping the first transaction to spend a coin. It
takes advantage of the nature of information being easy to spread but
hard to stifle." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
eleuthria (OP)
Legendary
 Offline
Activity: 1750
Merit: 1007
|
|
June 17, 2011, 06:57:56 PM |
|
Luck statistics were added to the block statistics page, for both a 24H window and since the difficulty change.
|
RIP BTC Guild, April 2011 - June 2015
|
|
|
smackdaddy
Newbie
Offline
Activity: 45
Merit: 0
|
|
June 17, 2011, 07:00:53 PM |
|
Luck statistics were added to the block statistics page, for both a 24H window and since the difficulty change.
What do the percentages indicate? Variance from expected? |
|
|
|
|
eleuthria (OP)
Legendary
Offline
Activity: 1750
Merit: 1007
|
|
June 17, 2011, 07:03:24 PM |
|
Luck statistics were added to the block statistics page, for both a 24H window and since the difficulty change.
What do the percentages indicate? Variance from expected? The percentages are related to the average shares per block in the past 24 hours/since difficulty change. Red numbers = bad luck, we're taking longer than average. Green = good luck, we're solving faster than average. |
RIP BTC Guild, April 2011 - June 2015
|
|
|
Veldy
Member
Offline
Activity: 98
Merit: 10
|
|
June 18, 2011, 03:47:49 AM |
|
Luck statistics were added to the block statistics page, for both a 24H window and since the difficulty change.
Heheh ... apparently mine sucks!  |
If you have found my post helpful, please donate what you feel it is worth: 18vaZ4K62WiL6W2Qoj9AE1cerfCHRaUW4x
|
|
|
Veldy
Member
Offline
Activity: 98
Merit: 10
|
|
June 18, 2011, 03:56:36 AM |
|
Luck statistics were added to the block statistics page, for both a 24H window and since the difficulty change.
What do the percentages indicate? Variance from expected? The percentages are related to the average shares per block in the past 24 hours/since difficulty change. Red numbers = bad luck, we're taking longer than average. Green = good luck, we're solving faster than average. Just a little nit. The stats, at first glance, appear as if the blocks themselves are larger or smaller than difficulty would suggest [which happens]. One might read from the page that the blocks are larger than normal [when red/negative %], but it seems that you are indicating the number of shares submitted for the number of blocks earned won over a period of time? In that case, it still perplexes me, as the number of shares per solution should largely be the difficulty divided by the percentage of total network hashing power that BTC Guild wields. What am I missing? To be fair, the same question can be asked of Deepbit too [I sort of always thought it indicated that larger blocks or smaller blocks than difficulty were been doled out for mining]. The more stats the better!  Understanding them exactly is an added plus [I have been working 14 hours straight today and my mind could be a bit addled]. |
If you have found my post helpful, please donate what you feel it is worth: 18vaZ4K62WiL6W2Qoj9AE1cerfCHRaUW4x
|
|
|
eleuthria (OP)
Legendary
Offline
Activity: 1750
Merit: 1007
|
|
June 18, 2011, 04:10:46 AM |
|
Luck statistics were added to the block statistics page, for both a 24H window and since the difficulty change.
What do the percentages indicate? Variance from expected? The percentages are related to the average shares per block in the past 24 hours/since difficulty change. Red numbers = bad luck, we're taking longer than average. Green = good luck, we're solving faster than average. Just a little nit. The stats, at first glance, appear as if the blocks themselves are larger or smaller than difficulty would suggest [which happens]. One might read from the page that the blocks are larger than normal [when red/negative %], but it seems that you are indicating the number of shares submitted for the number of blocks earned won over a period of time? In that case, it still perplexes me, as the number of shares per solution should largely be the difficulty divided by the percentage of total network hashing power that BTC Guild wields. What am I missing? To be fair, the same question can be asked of Deepbit too [I sort of always thought it indicated that larger blocks or smaller blocks than difficulty were been doled out for mining]. The more stats the better! Understanding them exactly is an added plus [I have been working 14 hours straight today and my mind could be a bit addled]. The 24 hour number is calculated by taking the average shares it took for each block solve that was done in the last 24h. So if the block's solve time was within 24 hours, it's share count is included to determine the 24h luck figure. So it's not exactly 24h, since a block may have been solved 23h 59m ago, but it was started an hour before that. However, this number gives a representation that is fair in my opinion. The comparison is to the current difficulty to determine if we were ahead or behind the average. It is our luck relative to difficulty, not our luck relative to overall network block production in the last 24 hours. |
RIP BTC Guild, April 2011 - June 2015
|
|
|
|
kripz
|
|
June 18, 2011, 04:41:02 AM |
|
Hello,
Is it possible to get share/hour submitted and rejected/hour?
|
|
|
|
|
Lumpy
|
|
June 18, 2011, 05:16:02 AM |
|
As long as you don't mind waiting a while for the transaction, it shouldn't be a problem.
Ele, any chance of having luck and/or personal 24-hour generation in the API?
|
|
|
|
|
Veldy
Member
Offline
Activity: 98
Merit: 10
|
|
June 18, 2011, 05:28:12 AM
Last edit: June 18, 2011, 06:56:14 AM by Veldy |
|
I reset my stats a few minutes ago and one of my miners now shows zero submissions and that the last submission was four hours ago. Can you look into the cause of this? I want to know that my submitted shares aren't going into the ether (which I highly doubt but have to ask anyway).
EDIT: Turns out that stats weren't updating correctly prior, so I did not notice from the stats that my miner was actually NOT submitting shares. Idles had caused Phoenix 1.48 to mine at 0MH/s yet again [I blame this on phoenix more than idles]. So, stats are working fine after reset, but phoenix sucks eggs. If it wasn't for phatk, I would dump it completely.
|
If you have found my post helpful, please donate what you feel it is worth: 18vaZ4K62WiL6W2Qoj9AE1cerfCHRaUW4x
|
|
|
|
Lumpy
|
|
June 18, 2011, 03:39:26 PM |
|
EDIT: Turns out that stats weren't updating correctly prior, so I did not notice from the stats that my miner was actually NOT submitting shares. Idles had caused Phoenix 1.48 to mine at 0MH/s yet again [I blame this on phoenix more than idles]. So, stats are working fine after reset, but phoenix sucks eggs. If it wasn't for phatk, I would dump it completely.
You might try 1.50 -- it was supposed to fix/reduce this issue. |
|
|
|
|
|
BitMinerN8
|
|
June 18, 2011, 03:51:57 PM |
|
EDIT: Turns out that stats weren't updating correctly prior, so I did not notice from the stats that my miner was actually NOT submitting shares. Idles had caused Phoenix 1.48 to mine at 0MH/s yet again [I blame this on phoenix more than idles]. So, stats are working fine after reset, but phoenix sucks eggs. If it wasn't for phatk, I would dump it completely.
You might try 1.50 -- it was supposed to fix/reduce this issue. Phoenix 1.50 w/Phatk solved my "wake up in the morning to several rigs with [0 Hhash/sec]" |
|
|
|
|
|
Faraday
|
|
June 18, 2011, 04:09:26 PM |
|
I just registered and created my workers but for some reason i can't connect to any of the btcguild servers  I can ping them fine but neither of the miners will connect (phoenix or poclbm) I am running linux Other pools work fine :\ |
|
|
|
|
|
BitMinerN8
|
|
June 18, 2011, 04:48:10 PM |
|
I just registered and created my workers but for some reason i can't connect to any of the btcguild servers I can ping them fine but neither of the miners will connect (phoenix or poclbm) I am running linux Other pools work fine :\ Post the miner command you are using. (example, sans username/pass) poclbm.exe -d1 --host=[server].btcguild.com --port=8332 --user=[username]_[workername] --pass=[worker_password] |
|
|
|
|
|
Faraday
|
|
June 18, 2011, 04:58:26 PM
Last edit: June 18, 2011, 05:10:39 PM by Faraday |
|
poclbm.py --user=loginname_workername --pass=workerpass -o uswest.btcguild.com -p 8332 -d0 -v -w128 -agression=11 error is: Problems communication with bitcoin RPC I have also tried 69.42.217.226 nl.btcguild.com uk.btcguild.com uswest.btcguild.com useast.btcguild.com uscentral.btcguild.com None of these work. But either mining.bitcoin.cz or deepbit.net with correct login works..  |
|
|
|
|
|
Lumpy
|
|
June 18, 2011, 05:20:18 PM |
|
I don't know if this has much (anything) to do with it, but you do know that AGGRESSION is for Phoenix not poclbm?
|
|
|
|
|
eleuthria (OP)
Legendary
Offline
Activity: 1750
Merit: 1007
|
|
June 18, 2011, 05:24:26 PM |
|
poclbm.py --user=loginname_workername --pass=workerpass -o uswest.btcguild.com -p 8332 -d0 -v -w128 -agression=11 error is: Problems communication with bitcoin RPC I have also tried 69.42.217.226 nl.btcguild.com uk.btcguild.com uswest.btcguild.com useast.btcguild.com uscentral.btcguild.com None of these work. But either mining.bitcoin.cz or deepbit.net with correct login works.. Just to make sure, your worker name being used is (for example): Faraday_GPU1. And how long is your password? It seems to have trouble try adding some garbage to the end of it if it's short. The pool doesn't check worker passwords, but some clients have a problem connecting with short/blank passwords. |
RIP BTC Guild, April 2011 - June 2015
|
|
|
|
Faraday
|
|
June 18, 2011, 05:33:32 PM
Last edit: June 18, 2011, 06:01:55 PM by Faraday |
|
Just to make sure, your worker name being used is (for example): Faraday_GPU1. And how long is your password? It seems to have trouble try adding some garbage to the end of it if it's short. The pool doesn't check worker passwords, but some clients have a problem connecting with short/blank passwords.
Yes thats right, name_a1, name_a2 ect. my passwords were a1, a2 ect so i will try changing them. edit: made the passwords longer and now i can connect, thanks! |
|
|
|
|
|
zerokwel
|
|
June 18, 2011, 09:36:00 PM |
|
Just wanted to say loving the changes to the site with the extra stats and whatnot. Only thing I am looking forward to is when automatic payouts gets setup. I am lazy so anything to help me be more lazy is a +
|
|
|
|
|
gyzer
Jr. Member
Offline
Activity: 50
Merit: 10
|
|
June 18, 2011, 10:08:19 PM |
|
I'd really like if we could get the following stats added:
On my account page: shares submitted in the last 24 hours for each miner
In the block statistics page:
Average time to complete a block in the past 24 hours
Average number of blocks completed in the past 7 days
I really love all the new enhancements to the site! Keep up the good work!
|
|
|
|
|
|
