Bitcoin Forum
July 01, 2024, 11:56:51 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 [137] 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 ... 202 »
2721  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 09:33:14 PM
Pretty sure I mentioned something about having patience somewhere in this thread... Tongue

I think I was in too big of a hurry to read that! 😜
Well played, sir... well played Smiley
2722  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 09:29:46 PM
Pretty sure I mentioned something about having patience somewhere in this thread... Tongue
2723  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 08:41:57 PM
ok ! i thought CoiniumServ was like p2pool.
No... CoiniumServ is a centralized pool.  You get miners to connect to your pool and it is only the combined hashing power of the miners on that pool that count towards the solving of the block.  This is how your typical pool works (BTCGuild, Eligius, Slush, Discus Fish, AntPool, etc).  They are all centralized pools.

P2Pool is a distributed network of nodes all working together to solve the block of BTC.

Here's the difference between a pool like CoiniumServ and p2pool.  I can move my miners right now from my node to yours, over to OgNasty's, on to windpath's and back to mine and my work goes with me.  All of my shares are still there.  If I happen to be mining on your node when the next block is found, I still get paid for the shares I have on the chain no matter on which node that share was found.  I don't lose any work.  I most certainly cannot do that if I point my miners to BTCGuild, then to BAN, then to kano.is and back to BTCGuild.  On each of those pools any work I've done on any other pool is completely irrelevant.
2724  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 07:45:34 PM
i see wow. well then i must say i was close to changing the pool to CoiniumServ but i will hold off and see this through.

Thanks Jonny !
CoiniumServ is its own pool and not hooked into p2pool.  Your pool by itself is trying to solve blocks of BTC.  Unless you've gotten a few petahash worth of miners to commit to you, don't bother.
2725  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 07:25:57 PM
got it.. but how come only one miner shows shares? that has me worried i don't like feeling like everyone is getting cheated or something..

at the moment that's how it feels with only one miner showing shares
Because that miner is the only one who's got a share that was accepted onto the share chain.  Remember, p2pool is not like your typical pool where every little share you submit counts.  The only shares that p2pool cares about are ones that are of a high enough difficulty to be added to the share chain and/or solve a block of BTC.

I've got a S3 that has been mining for a few days now without finding a share... so when the last block was found, it didn't get a payout.  It happens.  It's the variance inherent in the system.
2726  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 07:10:26 PM
i just learned something the more Miners we have the faster the time to share is.. when we had them all on it said 1h now that a few disconnected it says 5h cool.. nice to know
The node takes into account all miners to calculate the time to share.  The more miners you have, the more hash rate you have and the quicker a share is expected to be found.  It's kind of a misleading stat for an individual miner, since it is based on the entire node's hash rate.  Just like you can calculate your expected earnings of BTC per day for a given hash rate and difficulty, you can do the same thing to determine how long it should take you as a miner to find a share in p2pool.  The formula can be simplified to this:
Code:
Share Difficulty * 2^32 / hash rate = time to find a share in seconds

Let's look at an example for a 1TH/s miner using the current share difficulty of 6500000:
Code:
6500000 * 2^32 / 1000000000000 = 27917.29
So, a 1TH/s miner would expect to find a share every 7.75 hours at a share difficulty of 6.5 million.
2727  Bitcoin / Pools / Re: NastyPoP vs Standard P2Pool on: January 29, 2015, 05:39:26 PM
Just a quick update... it looks like Nonnakip double-spent the coins and as a result I received the payout from last week's mining on NastyPoP.  Thanks!  I wasn't expecting the payout until tomorrow, so it was a nice surprise Smiley.

Anyway, now that the payout has been received, here are the results for the week of 1/16 - 1/23:

NastyPoP - 0.02833329BTC
NastyP2P - 0.03989456BTC
Expected - 0.0352BTC

I didn't capture the 7 day luck last Friday, so I don't have it to report unfortunately.  There have definitely been some growing pains with the adoption of ckpool as the front end for NastyPoP, and the payout reflects it.  Downtime, restarts, etc contributed, and the lower payout is the result.  Things have gotten a tad more stable this week, so we'll see how it stacks up tomorrow.

OP updated with the results.

Edit: you'll notice that I am not including numbers for a miner on my own node any longer.  Last week when I was traveling for work I noticed that the miner had gone down.  When I returned home, I found the miner had hashed its last hash.  Oh well... it was an early batch S3 that's long since paid for itself.  Moving forward, I'll be running the test only showing the results of standard p2pool payouts vs NastyPoP with both S3s pointing to nastyfans.org.
2728  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 29, 2015, 04:09:23 PM
i seen that! also let me know if they are sending out pay! i got one this morning

I just moved both S5's back a little while ago. As far as pay I have not seen anything?
You will only see a payment if you had a share on the chain when the block was found.  Looking at the stats page, I can see only 1 of the 4 miners on the node that has a share.
2729  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 28, 2015, 08:06:32 PM
Just took a quick look at your site... I like the color scheme you chose.  Too bad the two shares you found were both orphaned.  Also, you're very generous to offer 1% donation to the p2pool author (forrestv).  Most people don't bother to provide anything at all.
2730  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 28, 2015, 05:33:25 PM
Good info! how do you compare the earnings vs other pools will our guys mining see a better return mining the p2pool?
Ahh... the penultimate question that everyone asks, "How does p2pool stack up against others?"

Too bad there really is no way to answer it definitively.  I can share my experience with it.  I can show you threads that compare p2pool to other pools - but each is subjective.

My personal experience with p2pool has been extremely positive.  I have made far more mining on p2pool than expectations show I should have.  I think the biggest thing you and your miners need to understand when they decide to make the jump to p2pool is that you absolutely MUST have patience.  P2Pool miners go through cold spells and hot spells.  You might get lucky and find more than the expected number of shares on the chain, and then p2pool might find more than the expected number of blocks, leading you to make far more in a day than you reasonably should.  The converse is also true.  You might find fewer than expected shares and p2pool finds fewer than expected blocks, leaving you with far less than you should have made.  Variance is far more prevalent with p2pool for your average miner.  If you've got ADHD or freak out because you were supposed to make 0.00234147BTC a day, but only made 0.00234146BTC then p2pool is not for you.

One of the biggest draws for me was the fact that I do not have to rely upon some pool operator and whether or not that operator is out to scam me and the rest of the miners.  I don't have to worry about fancy payout systems, setting payout thresholds, any of it.  When a block is found, if I have shares on the chain, I get paid.  Period.  There are no late payments, missed payouts, complaints to tech support and opening a ticket.  Nothing.  Got a share?  Get paid for it.
2731  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 28, 2015, 05:03:16 PM
Glad to help.  Another question that comes up a lot is, "How long is my share valid on the payout list?" The answer is 3 times the average shares to find a block OR 8160 shares, whichever is smaller.  Since shares are supposed to be found every 30 seconds, this turns into a maximum of 3 days that your share will be valid for payout.  Obviously it fluctuates but, generally if expected time to block is a day, your share on the chain will last for 3 days.

Also in relation to shares is, "how much is my share worth?" Each share is given a weight, and when the payouts are calculated your share weights are compared to all the other shares on the chain.  This also constantly fluctuates because it is primarily based upon share difficulty.  In other words, the higher the difficulty of finding a share to add on the chain, the more that share is typically worth.
2732  Bitcoin / Pools / Re: Stop by our pool give us feed back on: January 28, 2015, 03:45:56 PM
looking good so far! just sent out some thank you cause i still dont know if this thing is working.. but what ever comes in on my end i make sure i split = )

Just seen it thanks! This my first time trying a miner on a p2pool and have to admit I am really not sure how the payout works. I will try and find the time to read up on it.
There's a rather long thread about p2pool right here in these forums Smiley

I'll give you a brief summary: p2pool works on a PPLNS payout where you get paid for however many shares you currently have on the payout list when a block is found.  To find a share, you are essentially solo-mining a low difficulty coin.  The current difficulty of that share fluctuates between 8 and 12 million.  When you find a share, it is broadcast to the p2pool network in much the same way finding a block of BTC is broadcast.  If your version of the share chain is accepted, congratulations you now have a share on the chain.  The more shares you have on the chain, the higher your payout is when a block of BTC is found.  You receive newly generated coins, and as such must wait for 101 confirmations before you can spend them.
2733  Bitcoin / Pools / Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: January 28, 2015, 12:14:38 AM
Oh look... Another one!
2734  Bitcoin / Pools / Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: January 27, 2015, 10:06:16 PM
Difficulty goes down... p2pool finds a block.  Let's find a few more today Smiley

diff down, hits a block, hashrate goes up = ? ? ?
That's easy... we find another block!  Oh look... we just did Smiley
2735  Bitcoin / Pools / Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: January 27, 2015, 04:08:31 PM
Difficulty goes down... p2pool finds a block.  Let's find a few more today Smiley
2736  Bitcoin / Pools / Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: January 26, 2015, 10:02:04 PM
Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?
The actual payout depends on the weight of the share when it was found.  It's easy to calculate how many shares you should expect to find, but remember, the share difficulty is constantly changing.  That means the share weights are constantly changing and the expected time to find a share is also constantly changing.

Let's assume a share difficulty of 10000000.  With your 5.5TH/s, you would expect to find a share every 2.17 hours or so, or about 11 shares a day.
2737  Bitcoin / Pools / Re: NastyPoP vs Standard P2Pool on: January 26, 2015, 07:43:55 PM
It's quite apparent that something went pretty wrong last week, both with the conversion to the new front end and with the payouts themselves.  The issues still persist today.  I hope Nonnakip is able to get this sorted.

The payouts went out, but aren't being confirmed by the network for some reason.  This isn't related to the frontend, but some other mystery.  Here's the transaction that is waiting to confirm: https://www.blocktrail.com/BTC/tx/c46bd16596240f6b41a10ceb968389c3921214cbff27d6cbe6d987f51bab9c99

The conversion to the new frontend went fine as well.  The issue is that ckpool is currently extremely buggy.  NastyPool is now using an older version of ckpool that seems a little more stable, as well as restarting when an issue is detected.  I'm beginning to question if ckpool is ready for primetime yet though.  Using the 9332 port will eliminate any issues relating to ckpool until a stable version can be released, and if last week's distribution isn't confirmed by this week, the coins will be double spent to ensure they are added to this week's distribution.
I linked the payout transaction in my post.  You're absolutely right that it's a mystery.  I also read your post in the pool thread stating that Nonnakip would be sending out the payments again this coming Friday if they hadn't confirmed by then, so no worries about that.

My primary concern is the discrepancy between what the charts on the site state vs what the payout transaction has.  The charts show miner addresses more than once, each with a value of expected BTC payout.  The payout transaction, however, only has one of those values.  Could you explain that, please?  The reason I'm asking is that during the past week p2pool was over 100% luck, finding more blocks that it should have.  My standard p2pool payouts reflect that; however, my payments in the NastyPoP payout transaction are far below expectations.  As I mentioned, I made nearly double with standard p2pool payouts as I did with NastyPoP.

When you wrote, "using the 9332 port will eliminate..." are you suggesting that people should go back to using stratum+tcp://nastyfans.org:9332 -u WALLETADDRESS-PoP -p x for the NastyPoP payouts?

Thanks for any clarifications.
2738  Bitcoin / Pools / Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: January 26, 2015, 04:10:56 PM
the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M
You're correct, and I should have pointed out that caveat.  Also, for some reason with Bitmain's web UI, if you use a power of 2 for your pseudo difficulty, best share value will always be 0.  However, if you use any other value it works just fine.  Bitmain definitely has some peculiar issues with their hardware, firmware and software.
2739  Bitcoin / Pools / Re: NastyPoP vs Standard P2Pool on: January 26, 2015, 04:03:02 PM
As you can see, I have not provided results for the week 1/16 - 1/23.  There were some pretty significant connection issues with Nonnakip's new implementation of ckpool on top of the p2pool framework.  Unfortunately, those issues are still persisting as you can see from this screenshot:



Combine this with the fact that no payouts were received for last week and I am unable to provide any kind of meaningful test results.  Please note, you can see that a payout was attempted by looking here: https://www.blocktrail.com/BTC/tx/c46bd16596240f6b41a10ceb968389c3921214cbff27d6cbe6d987f51bab9c99

Unfortunately, with the changeover to the new NastyPoP system, payouts seem to have gotten confused.  Looking at the payout distribution charts at https://nastyfans.org/nastypool/nastypop_ticker I can see my miner's address listed twice.  The attempted payout matches one of those values (0.02006569 BTC) but there is no mention of the other value.  If we go solely on the attempted value, we'll find that it is significantly lower than what I made on the standard nasty p2pool payout (0.03989456BTC).  The expected payouts for this past week were 0.0352BTC.  P2Pool itself was pretty lucky during these 7 days, so I'm shocked to see such a huge disparity (nearly twice as much) between what I made on the standard payout vs what is reported for the NastyPoP method.

It's quite apparent that something went pretty wrong last week, both with the conversion to the new front end and with the payouts themselves.  The issues still persist today.  I hope Nonnakip is able to get this sorted.
2740  Bitcoin / Pools / Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: January 26, 2015, 03:16:57 PM
the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.
Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

Setting "/" does affect your payout IF you set it to a value higher than the current p2pool share difficulty.  Setting it to 1000 makes no difference.  Setting it to 1000000000 would certainly make a difference.  This parameter tells p2pool, "I don't care what you think the share difficulty to get on the chain should be.  You will use the difficulty I provide and weight any shares I submit accordingly."  Unless you have a miner that could potentially be submitting shares faster than every 30 seconds, there is really no reason to use this parameter.
Pages: « 1 ... 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 [137] 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 ... 202 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!