|
9 months wait?
Illegal refund conditions (check Terms and Conditions).
So much overpriced?
I don't want to be BFL'd again, thanks, I am done here.
|
|
|
|
|
1. Why fees are so high on this pool? At least for BTC mining, you should consider lowering it. This pool is great alternative to p2pool mining for small miners. Variance on original p2pool is pretty high (share difficulty), but using multipool could enable small miners to mine on p2pool again, through multipool.us. But, there is no incentive to do that, you don't pay NMC, DVC, D0C and BTC fee is ridiculous 1.5%, so hashrate is so low.
No way I am gonna switch my 2.5TH/s to your BTC pool (or profit-switching pool), because I would lose ~2% in merged mining and further 1.5% in your fee.
2. You not mentioning anywhere on the website, that BTC mining is done as p2pool node. Why? What about other alternative coins, are they all mined as p2pool node payouts and then split between multipool.us users?
|
|
|
|
|
wizkid057,Luke-Jr,
Can you share instructions how to install bfgminer on KncMiner Jupiter? Temporarily or permanently?
|
|
|
|
My stats dropped to zero today. Any known issues at eligius?
Maybe just check your cgminer? |
|
|
|
Hey all, Newbie here - been digging doges at pool.hostv.pl:9355 for almost 7 hours now, with almost 370 Accepted shares but no payout yet - is there something that's gone wrong? Who should I contact? http://imgur.com/vO58jl8Any help would be much appreciated! Thanks I know admin of that node, I just told him that you asking. |
|
|
|
Well for the last 12 hrs my 180Ghs (3xBitburner Furys & 1 Bitfury) showed 140Ghs. Checked the equipment and everything was ok. Watching it for the last 30min and I it looks like it started to show the correct hashing rate again. Since we got less coins because of false values will there be any reimbursement?
False values? There is no pool side issue at work here. The only known issue right now is that the cgminer + knc driver have some kind of issue. -wk Sorry how would you call it? From 03:00 until 18:22 today I was getting 30Ghs less shown on your pool then my rigs were hashing! If you dont care to check thats your prob. If you not happy please feel free to leave. Don't even waste developer's time without providing logs, stats, description of situation etc. Goodbye. |
|
|
|
I don't get why people still tolerate cgminer and all its many bugs.
It's on KNC firmware by default, I have to stick with it for now, I tried bfgminer from BertMod, but it didn't work very well, throwed out lots of errors and started mining with 20 GH/s or so. |
|
|
|
Not sure how that makes any sense at this point. The main server is running the exact same code now. I'll look into it further. -wk Thank you. Hope you'll find it. I switched back to dev-server and immediately got better results (live): Avg. Hash Rate 668 Gh/s
WU 9132
Difficulty Accepted 108798
Device Hardware%=1.9638
|
|
|
|
I have issues with HW ratio on Eligius on KNC Jupiter November units. I have 3 units, all of them behave exactly the same. Testing scenario one of the units: 1. Restart cgminer, choose Eligius pool via ssh, reset cgminer statistics, let it run for couple of hours, write down stats 2. Restart cgminer, choose BitMinter pool via ssh, reset cgminer statistics, let it run for couple of hours, write down stats 3. Repeat nr 1 4. Repeat nr 2 Stats: 1. Eligius 9.4% HW, WU 8437 https://drive.google.com/file/d/0B2z0CgjT8HdwYnhkTFk1TGd1VUE/edit?usp=sharing2. BitMinter 1.5% HW, WU 9199 https://drive.google.com/file/d/0B2z0CgjT8HdwZFB6Nkx1czBNdEE/edit?usp=sharing3. Eligius 8.9% HW, WU 8478 https://drive.google.com/file/d/0B2z0CgjT8HdwazZsRnlPbDdYQkk/edit?usp=sharing4. BitMinter 1.6% HW, WU 9188 https://drive.google.com/file/d/0B2z0CgjT8HdwMTJMaW1kdkNaQlE/edit?usp=sharingI have default settings of: [Q]ueue: 1
[S]cantime: 60
[E]xpiry: 120
wizkid057, what should I set there? I will be happy to help with dev pool, sent you PM. Regards, Lenny |
|
|
|
I switched back one worker, I have now 500GH/s less hashrate, but adjusting share difficulty works fine, it's still targeting for 30 minutes: Before: 2013-12-12 01:25:39.378616 Got new merged mining work!
2013-12-12 01:25:39.467493 New work for worker! Difficulty: 524.676247 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:39.536678 New work for worker! Difficulty: 200.000000 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:39.943825 New work for worker! Difficulty: 524.676247 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:40.014058 New work for worker! Difficulty: 200.000000 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:40.431869 P2Pool: 17329 shares in chain (17333 verified/17333 total) Peers: 30 (20 incoming)
2013-12-12 01:25:40.431971 Local: 2312GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.8 minutes
2013-12-12 01:25:40.432022 Shares: 2 (2 orphan, 0 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-80%) Current payout: 0.0000 BTC
2013-12-12 01:25:40.432066 Pool: 113TH/s Stale rate: 17.2% Expected time to block: 9.6 hours
After switching back one Jupiter: 2013-12-12 01:38:35.039265 Got new merged mining work!
2013-12-12 01:38:35.081103 New work for worker! Difficulty: 460.471053 Share difficulty: 827194.125247 Total block value: 25.045982 BTC including 227 transac
tions
2013-12-12 01:38:35.110148 New work for worker! Difficulty: 200.000000 Share difficulty: 827194.125247 Total block value: 25.045982 BTC including 227 transac
tions
2013-12-12 01:38:35.294612 P2Pool: 17341 shares in chain (17345 verified/17345 total) Peers: 30 (20 incoming)
2013-12-12 01:38:35.294721 Local: 1922GH/s in last 10.0 minutes Local dead on arrival: ~2.4% (1-4%) Expected time to share: 29.4 minutes
2013-12-12 01:38:35.294754 Shares: 3 (2 orphan, 0 dead) Stale rate: ~66.7% (20-94%) Efficiency: ~40.0% (7-96%) Current payout: 0.0080 BTC
2013-12-12 01:38:35.294790 Pool: 113TH/s Stale rate: 16.7% Expected time to block: 9.5 hours
After switching another one: 2013-12-12 01:49:11.751705 Got new merged mining work!
2013-12-12 01:49:11.779507 New work for worker! Difficulty: 315.541941 Share difficulty: 566841.961741 Total block value: 25.063109 BTC including 155 transactions
2013-12-12 01:49:11.802853 New work for worker! Difficulty: 200.000000 Share difficulty: 566841.961741 Total block value: 25.063109 BTC including 155 transactions
2013-12-12 01:49:13.899286 Peer sent entire transaction 25702c285a2b64d0abb7c0421a01dc68159428b594491a318870a652016fa6d5 that was already received
2013-12-12 01:49:14.122667 P2Pool: 17328 shares in chain (17332 verified/17332 total) Peers: 30 (20 incoming)
2013-12-12 01:49:14.122844 Local: 1435GH/s in last 10.0 minutes Local dead on arrival: ~2.1% (1-4%) Expected time to share: 30.6 minutes
2013-12-12 01:49:14.122970 Shares: 4 (2 orphan, 0 dead) Stale rate: ~50.0% (15-85%) Efficiency: ~60.0% (18-102%) Current payout: 0.0124 BTC
2013-12-12 01:49:14.123066 Pool: 109TH/s Stale rate: 16.7% Expected time to block: 9.9 hours
At this point, I think, that adjusting code should be simpified to one rule: if your expected time to share is less than 60 minutes, adjust share diff so expected time to share is again 60 minutes.This will work with all miners, big and biggest ones, gives more room for smaller miners like less than 50, 100 GH/s again. |
|
|
|
I got error when I found a share today: 2013-12-12 01:01:36.423805 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:36.423930 Local: 2356GH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:36.423978 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:36.424015 Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:39.436918 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:39.437093 Local: 2357GH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:39.437174 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:39.437264 Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:41.593547 GOT SHARE! Jupiter 23877a5a prev a9d32777 age 80.86s
2013-12-12 01:01:41.622728 > Error while processing Event callbacks:
2013-12-12 01:01:41.622811 > Traceback (most recent call last):
2013-12-12 01:01:41.622846 > File "/home/user/p2pool/p2pool/bitcoin/worker_interface.py", line 136, in <lambda>
2013-12-12 01:01:41.622882 > lambda header, user, coinbase_nonce: handler(header, user, pack.IntType(self._my_bits).pack(nonce) + coinbase_nonce),
2013-12-12 01:01:41.622915 > File "/home/user/p2pool/p2pool/work.py", line 403, in got_response
2013-12-12 01:01:41.622981 > self.node.set_best_share()
2013-12-12 01:01:41.623012 > File "/home/user/p2pool/p2pool/node.py", line 297, in set_best_share
2013-12-12 01:01:41.623043 > self.best_share_var.set(best)
2013-12-12 01:01:41.623073 > File "/home/user/p2pool/p2pool/util/variable.py", line 74, in set
2013-12-12 01:01:41.623103 > self.changed.happened(value)
2013-12-12 01:01:41.623133 > --- <exception caught here> ---
2013-12-12 01:01:41.623162 > File "/home/user/p2pool/p2pool/util/variable.py", line 42, in happened
2013-12-12 01:01:41.623192 > func(*event)
2013-12-12 01:01:41.623232 > File "/home/user/p2pool/p2pool/node.py", line 96, in broadcast_share
2013-12-12 01:01:41.623271 > peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.valu
e, include_txs_with=[share_hash])
2013-12-12 01:01:41.623322 > File "/home/user/p2pool/p2pool/p2p.py", line 291, in sendShares
2013-12-12 01:01:41.623355 > assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2013-12-12 01:01:41.623394 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions
2013-12-12 01:01:41.660075 New work for worker! Difficulty: 599.266435 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:41.691285 New work for worker! Difficulty: 200.000000 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:42.448631 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:42.448763 Local: 2360GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:42.448800 Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC
2013-12-12 01:01:42.448837 Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:45.462377 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:45.462555 Local: 2369GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:45.462638 Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC Then found another share and it was fine: 2013-12-12 01:04:22.130684 Local: 2329GH/s in last 10.0 minutes Local dead on arrival: ~1.6% (1-3%) Expected time to share: 30.1 minutes
2013-12-12 01:04:22.130717 Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:22.130754 Pool: 115TH/s Stale rate: 20.5% Expected time to block: 9.4 hours
2013-12-12 01:04:22.335429 New work for worker! Difficulty: 691.171186 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:22.377099 New work for worker! Difficulty: 200.000000 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:25.143566 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:04:25.143681 Local: 2325GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:25.143714 Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:25.143750 Pool: 120TH/s Stale rate: 20.5% Expected time to block: 9.0 hours
2013-12-12 01:04:27.234256 GOT SHARE! Jupiter3 89d9ea47 prev faed7137 age 4.87s
2013-12-12 01:04:27.349609 New work for worker! Difficulty: 614.131984 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:27.391143 New work for worker! Difficulty: 200.000000 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:28.156049 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
2013-12-12 01:04:28.156144 Local: 2327GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:28.156176 Shares: 2 (1 orphan, 0 dead) Stale rate: ~50.0% (9-91%) Efficiency: ~63.3% (11-115%) Current payout: 0.0114 BTC
2013-12-12 01:04:28.156213 Pool: 121TH/s Stale rate: 21.1% Expected time to block: 8.9 hours
2013-12-12 01:04:30.834454 Peer sent entire transaction 90e0bb504ac630d2e08ddf489731341236812c22179e74fedde6a6b5d96282ad that was already received
2013-12-12 01:04:31.166570 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
Also, adjusting share diff works for my node, just fine. p2pool gives work to my workers and reporting share time: 2013-12-12 01:06:00.703104 Got new merged mining work!
2013-12-12 01:06:00.740053 New work for worker! Difficulty: 570.368318 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:00.767854 New work for worker! Difficulty: 200.000000 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:01.621688 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:06:01.621786 Local: 2352GH/s in last 10.0 minutes Local dead on arrival: ~1.8% (1-3%) Expected time to share: 30.4 minutes But on webpage it says: Pool rate: 121TH/s (21% DOA+orphan) Share difficulty: 487000
Node uptime: 4.0 days Peers: 10 out, 21 in
Local rate: 2.41TH/s (1.5% DOA) Expected time to share: 14.5 minutes So we have different share diff and ETA for workers in p2pool log, and different share diff nad ETA on p2pool front page. But adjusting itself works very good, I have Expected time to share in p2pool log always auto-adjusted to ~30 minutes. EDIT: Both shares I found has been orphaned couple of minutes later!!! :O With series of errors. Whole log here: http://lenny.dnsd.me/p2pool.logShares: 2 (2 orphan, 0 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-80%) Current payout: 0.0000 BTC  Can someone explain how it happened? |
|
|
|
I would go with "over time" = at least 100 times whatever your expected time to find a share is.
In lenny's example that would be 17 years. Yes, and in that example case making any statement of "what I earned over the past couple months" is not statistically meaningful. That example was for 322 MH/s which is insanely small given current bitcoin difficulties. The only reason to be mining with 300 MH/s at all is if you are betting on another 100-fold increase in the BTC/USD exchange rate making your handful of satoshis valuable someday. Or alternatively if you don't care about profits and are just mining for the fun of it. Whatever the reason, definitely don't bother mining on p2pool with that amount of hashrate. Perfect pool should be profitable for any miner. p2pool is very unfriendly for anything smaller than 10-30 GH/s. I am working to change that - for future of p2pool, which can do good for any miner on the planet, using distributed p2p network of miners. Right now you make profit only if you have lots of expensive ASIC miners. And yes, I am mining for fun, not for profits - all my Jupiters are sitting on Eligius pool. |
|
|
|
Quick glance at stats: Pool rate: 95.5TH/s (16% DOA+orphan) Share difficulty: 411000
Node uptime: 1.5 days Peers: 10 out, 11 in
Local rate: 322MH/s (0.0% DOA) Expected time to share: 63.5 days As you see, p2pool is not good for small miners anymore. Even with 30 GH/s, you getting share once in 17 hours, variance can make this value 5x smaller or bigger, and you may miss the blocks. Right now, we have modification in p2pool share diff calculating algorithm: If address (miner) have more than 1.67% of p2pool hashrate, increase his node's share diff, so he will find shares less likely 1.67% corresponding to ~1.4 TH/s. I check p2pool.info stats and we have about 11 miners with hashrate above that. Biggest one have almost 15TH/s, which is ~18% of p2pool hashrate. Couple of weeks ago, when commit has been made by forrestv to modify that limit to 1.67%, it was fine - 1.67% was equivalent of about 400-500 GH/s, right now it's 3x higher. I am suggesting to change this behaviour to formula: * If address (miner) is finding shares in less than 60 minutes, increase his node share diff so he will find share in exactly 60 minutes This will be independent from current pool hashrate, last implementation (percentage of pool hashrate) doesn't work anymore with such big miners we have there now. Avg. of 24 beefy shares per day will be enough even for largest miners, they shouldn't complain about variance, as their sacrifice will enable small miners to mine again on p2pool, total pool hashrate will increase, so total variance for pool will decrease (profit for all miners). What you guys think? |
|
|
|
|
Bitcoin is not only a store of value. Please google it more next time.
|
|
|
|
|
scam. Easy was to get your e-mail and other credentials.
|
|
|
|
Username WeExchange ID Amount Time Stamplennytrt34g3 czdbgZ148KpRyIdTvNhm83KRi2K3Ssdk 0.24526709 BTC 2013-11-05 10:15:49
lennytrt34g3 nC1oU3xlAAAv1KsrrNuiLU5TYm6S8Bj6 0.17036000 BTC 2013-11-18 07:00:19 Still processing.
|
|
|
|
|
Show Posts
