|
Es funktioniert bestens! Und ich bin stark verwundert, dass diese Neuigkeiten hier im Forum nicht viel größere Wellen geschlagen haben. Immerhin scheint ul.to nach Rapidshare im europäischen Raum der zweitgrößte Sharehoster zu sein. Es ist somit kein kleines Unternehmen, das sich da entschieden hat, Bitcoins als Zahlungsmittel zu akzeptieren - und das ist klasse.
|
|
|
|
|
Die XTREME-Karten gehen für 110-120 weg bei eBay, soweit ich das sehen kann. Exklusive Versand. Dann mine ich lieber noch weiter bis zum bitteren Ende, bevor ich das Zeug verscherble, sorry Jungs.
|
|
|
|
|
Niemand interessiert? Wie gesagt, der Preis für das Gesamtsystem ist verhandelbar!
|
|
|
|
|
Ich würde die Komponenten evtl. auch einzeln verkaufen, macht mir einfach ein Angebot! Die Radeons gibt's einzeln für 120€/Stück.
|
|
|
|
|
EDIT: steht nicht mehr zum Verkauf.
|
|
|
|
I actually also get >5% stales using the latest poclbm by luke-jr, catalyst 11.6, sdk 2.4, ubuntu 11.04. pool.bitp.it:8334 24/07/2011 17:00:42, 67d07587, _rejected_ 48 (Eff:6.73)]
pool.bitp.it:8334 24/07/2011 17:00:50, 79461648, _rejected_ 48 (Eff:6.73)]
pool.bitp.it:8334 24/07/2011 17:06:20, e6223209, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:06:22, baf86b5c, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:06:30, 9b851437, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:06:43, e89b8378, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:06:48, abcbd49d, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:06:55, c97f1d85, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:06:55, 7a1160f0, _rejected_
pool.bitp.it:8334 24/07/2011 17:07:08, 331832ab, _rejected_ 53 (Eff:6.57)]
pool.bitp.it:8334 24/07/2011 17:08:10, b15d15dd, _rejected_ 54 (Eff:6.52)]
pool.bitp.it:8334 24/07/2011 17:08:14, f6cf105d, _rejected_ 54 (Eff:6.52)]
pool.bitp.it:8334 24/07/2011 17:08:19, 586a7649, _rejected_ 54 (Eff:6.52)]
pool.bitp.it:8334 24/07/2011 17:08:20, 96eb1868, _rejected_ 54 (Eff:6.52)]
pool.bitp.it:8334 24/07/2011 17:24:13, long poll: IO error 67 (Eff:6.52)]
pool.bitp.it:8334 24/07/2011 17:24:14, LP connected to pool.bitp.it:8334 67 (Eff:6.52)]
pool.bitp.it:8334 24/07/2011 17:29:32, long poll: new block 0000082b53a84405 71 (Eff:6.49)]
pool.bitp.it:8334 24/07/2011 17:31:36, long poll: new block 00000133afb8a04d 73 (Eff:6.42)]
pool.bitp.it:8334 24/07/2011 17:47:50, 13c9b852, _rejected_ 86 (Eff:6.40)]
pool.bitp.it:8334 24/07/2011 17:52:53, 7b4be65c, _rejected_ 90 (Eff:6.32)]
pool.bitp.it:8334 24/07/2011 17:52:54, d97349df, _rejected_ 90 (Eff:6.32)]
pool.bitp.it:8334 24/07/2011 17:53:01, 26d6fe5c, _rejected_ 90 (Eff:6.32)]
pool.bitp.it:8334 24/07/2011 18:01:41, bdad71cf, _rejected_ 97 (Eff:6.28)]
pool.bitp.it:8334 24/07/2011 18:02:56, a9e1406a, _rejected_ 98 (Eff:6.24)]
pool.bitp.it:8334 24/07/2011 18:03:02, bb5ed498, _rejected_ 98 (Eff:6.24)]
pool.bitp.it:8334 24/07/2011 18:03:05, bb716a04, _rejected_ 98 (Eff:6.24)]
pool.bitp.it:8334 24/07/2011 18:06:31, dd738ad8, _rejected_ 101 (Eff:6.17)]
pool.bitp.it:8334 24/07/2011 18:06:33, 48a73be3, _rejected_ 101 (Eff:6.17)]
pool.bitp.it:8334 24/07/2011 18:06:51, ae570e72, _rejected_ 101 (Eff:6.17)]
pool.bitp.it:8334 24/07/2011 18:11:48, af734db8, _rejected_ 105 (Eff:6.21)]
pool.bitp.it:8334 24/07/2011 18:11:50, bc0b4856, _rejected_ 105 (Eff:6.21)]
pool.bitp.it:8334 24/07/2011 18:14:21, d1c9c700, ERROR (will resend) 107 (Eff:6.13)]
pool.bitp.it:8334 24/07/2011 18:21:59, 1586401f, _rejected_ 113 (Eff:6.13)]
pool.bitp.it:8334 24/07/2011 18:22:01, c3ea8f62, _rejected_ 113 (Eff:6.13)]
pool.bitp.it:8334 24/07/2011 18:22:08, 6c63d1bb, _rejected_ 113 (Eff:6.13)]
pool.bitp.it:8334 24/07/2011 18:31:37, long poll: IO error 121 (Eff:6.15)]
pool.bitp.it:8334 24/07/2011 18:31:38, LP connected to pool.bitp.it:8334 121 (Eff:6.15)]
pool.bitp.it:8334 24/07/2011 18:35:08, long poll: new block 000004a6b287b636 124 (Eff:6.14)]
pool.bitp.it:8334 [373.537 MH/s (~396 MH/s Eff:6.92)] [Rej: 42/812 (5.17%)] [GW: 125 (Eff:6.16)]
|
|
|
|
http://eligius.st/~artefact2/blocks/This should make it clear. Works good and is absolutely fair. Plus it's quite easy to understand actually, compared to your suggestions, TheSeven. If there are withholders, this would mean that they will get full payouts one day, but payouts get delayed by possibly weeks, which is very unattractive to new users.
No - in case of unsufficient funds on the server, payouts are adjusted, not "left out" entirely. So the effect is not that "hard".
|
|
|
|
The difference between a miner's actual (SMaxPPS) earnings and PPS earnings is retained as credit, and considered in future blocks.
Unpaid shares remain as a credit and will be paid out before "new" shares are paid out. It's like a queue, no credit gets lost. |
|
|
|
The only problem I see with this is that if the first rounds after implementing this are very lucky the funds will be used to payout the future long rounds where miners that werent there before can profit. And there is no point on keeping it secret since it can be easily calculated from the pool stats. Anyway, given the options its not a bad solution.
That's not true - it's still PPS, which means it eliminates "luck" entirely for the miners. You always get paid what you'd expect in the given time from your hashing rate and current difficulty. So the only variable for you as a miner is time and hashrate. "Long rounds" don't change your rewards, an neither are "new miners" rewarded more at any time. It's always fair. |
|
|
|
What is with the big swings in the pool total hash rate today? In the lat hour or so I have seen it in the from 100Mh/s to 70Mh/s.
pool hopping? the point in time (about 0.4*difficulty) fits. just want to clarify - abuse by pool hoppers (especially with prop/realtimestats) is not a question of faith. it's mathematically provable. for a good explanation, read this: http://forum.bitcoin.org/index.php?topic=24966.0 |
|
|
|
e.g. (blocksperday * 50) / (sharesperday) = your payout for that day
i don't know how you want to make that work. prop means: you get paid when a block is found. while the pool is still small, this can mean days, weeks. |
|
|
|
|
You don't "like" other systems... that's ok. But with prop and realtime stats, you actually get ripped off by pool hoppers, so you'd be better off with PPS.
|
|
|
|
but PLEASE don't use score / maxpps or anything else - just stick with pps.
i don't mine 24/7 so for me it's just an additional variance.
MaxPPS and PPS is actually more or less the same - and the best choice for someone who's not mining 24/7. But right now the pool is using Prop (that's not PPS!) |
|
|
|
|
What I'd really like to see is that you put focus on protection from pool hoppers. Either by delaying the stats (tough this can only marginally reduce the effect), or by introducing score/pps-based rewards. The MaxPPS system used by Eligius seems to work well. In the last round we were able to see 10-20 GH leaving in the middle of the round, and this will probably become even worse in the future.
|
|
|
|
I switched back from the most recent version of poclbm to the old version (doesn't have version numbers I guess  ), now I'm back to 0% stales. New one must have either a glitch by itself, or problems with your pushpool-implementation. |
|
|
|
Ok, some information: I'm in CEST (because of the timestamps). I run Ubuntu 11.04, poclbm (latest version) with phatk (2011-07-11 version by Diapolo), Catalyst 11.6 and APP SDK 2.4 --- pool.bitp.it ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 189.161/190.889/192.886/1.448 ms What I noticed also. pool.bitp.it:8334 12/07/2011 15:20:42, long poll: IO error
pool.bitp.it:8334 12/07/2011 15:20:43, LP connected to pool.bitp.it:8334
pool.bitp.it:8334 12/07/2011 15:20:48, 4a94f793, accepted
Current rates: [Rej: 156/5988 (2%)]
[Rej: 165/6319 (2%)]
[Rej: 145/6176 (2%)]
[Rej: 159/6279 (2%)]
Oh, and still would like to know who got the Bonus  |
|
|
|
My stale rate is up to about 1% the last hours... just now, I noticed a strange behaviour:  Any idea? But still very satisified so far, still the most stable pool experience I had. |
|
|
|
Block ist gefunden, Runde 7 hat begonnen, es kann losgehen  |
|
|
|
|
Show Posts
