Yes please! How a high-latency miner with 33% total hashrate can decrease other's efficiency?
Easy. He just need found 2 shares in row faster than rest of nodes. share chain: S1 S2<S1 ... Sa<S9 Sb<Sa - yours Sc<Sa - thiers Sd<Sc - thiers n2 -> your Sb is orphaned Se<Sd - someone else Sf<Sd - thier n3 Sg<Sf - thier n4 -> Se is orphaned too He got 4 shares, 2 other orpahned in proecess. Because of high latency he is not aware of other shares. But his probability to find a share faster than others is only 33%, and about 11% for finding two shares before the rest. If he fails, his shares will be orphaned. As a result, he harms himself more, just as planned! |
|
|
|
i just turned my stuff back to p2pool for a final hurrah i suppose you could say, before i shut everything down
but doesn't anyone find it concerning that someone has 33% of the hashrate? i also was unable to locate the IP address of this person, so they're probably behind a firewall, without many outgoing connections, judging from the other nodes I checked (IP address reported as relaying their share is quite a spread)
just found it curious since i've gotten 2 orphans out of 6 already, both because of the double share from 1Nasty
although i guess it could be partally attributed to using a US server
Why would it be disconcerting? p2pool is really small. there are filthy rich miners who have more than the entire hash rate of p2pool. M because it decreases efficiency of other people using p2pool when someone is using inefficient connection and is able to put out 33% of hashrate? does it need further explaining? Yes please! How a high-latency miner with 33% total hashrate can decrease other's efficiency? |
|
|
|
I am mining at 220 MH/s, are there any reasons why I shouldn’t raise my difficulty? If I were to put it at 512 would this have any negative impact on my side? It's just less traffic right? I already know this doesn’t change my chances of finding a share of the required difficulty. I'm just wondering what happens on my end.
At that hashrate, you probably don't want to increase difficulty. It will not significantly change network load but will increase income variance. This gets to the crux of my question. How or why would it increase income variance at a pool like p2pool where we are looking for high difficulty shares. I'm not disagreeing with you, I'm asking why? Do we need to submit these lower diff shares for some reason? At 220MH/s estimated time to share is 8 hours. For instance, that means that there's 5% probability of not finding any shares for 24 hours. For two week period, your estimated number of shares is 42, and there's 5% probability to find 31 or less shares, which means only 75% of estimated income. Of course, this also works in positive direction, and your income may be higher than estimated as well. Now if you increase your share difficulty, this variation will be even higher. If you are not a gambler, you want stable income. When mining in p2pool, your income variance depends on both pool's blockrate variance and your own sharerate variance. For details see my post here https://bitcointalk.org/index.php?topic=18313.msg2060914#msg2060914 |
|
|
|
vata2013 не поддавайся на провокации, тебя купить пытаются )))
его уже купили, поставили на четвереньки и поимели  Чудовище ты поясни, что за нелепость выше написал? Это я на новый кошелек только созданный выводил с пула лайт? А почему нет в историях транзакций этого? или мосга не хватило продумать, что все транзакции в логах оседают? Кстати 1 лайта мало для того, чтобы я славил Бальта! Докиньте хотя бы еще пол лайта. Дебил, тебе 2 человека кинули денег, чтобы ты не позорился и не ныл из-за 1 лайта, который проебал по своей же глупости. |
|
|
|
I am mining at 220 MH/s, are there any reasons why I shouldn’t raise my difficulty? If I were to put it at 512 would this have any negative impact on my side? It's just less traffic right? I already know this doesn’t change my chances of finding a share of the required difficulty. I'm just wondering what happens on my end.
At that hashrate, you probably don't want to increase difficulty. It will not significantly change network load but will increase income variance. |
|
|
|
Чего Вы разнылись как бабы, Вы же предприниматели мать вашу, значит ведете свою деятельность на свой страх и риск. Бальтазар получил имиджевый урон гораздо больше чем стоимость тех лайтов уплывших к вполне конкретным людям. Хотите бойкотировать - флаг в руки и никто не пожалеет, если человек оставляет хранится свои средства в чужих руках и при этом не отдает себе отчет о рисках и даже не удосуживается заниматься риск-менеджментом, то он конкретный, скажем так - "недальновидный предприниматель".
П.С. 1) Самая надежная валюта это водка и тушенка
2) Выводить свои бабки нужно каждый день
3) Доверять нельзя никому - иногда даже себе
4) Хранить любые монеты надежней всего в своем кошельке
У меня 0,95 лайта змезло на пуле. Если такой умный скажи как я их бы вывел? Клёво болтаешь, прям с элементами НЛП, типа кто отпишется против твоих слов тот дурачок и не модный сейчас предпренематель, а баба. Пфффф... Да ты бы мог уже их заработать, уйти на другой пул и забыть. Но пиздеть на форуме конечно интереснее, не спорю. Добавил 0.45 лайта, 0.5 тебе уже кинули. 74cbf49d7e97bafd72e28047c9bbbaf41262ab780933f7e4293868b463fbef8d P.S. Только не майни больше на пулах Бальтазара, а то третий раз уже не смешно будет. |
|
|
|
If you want to mine on a public node, go to http://p2pool.hostv.pl/ (once page loads, reload it again with F5), choose node with least ping (and suitable fee), and point your workers to it specifying your payout address as login and any password. yeah, that exact synax woultd be nice, for BFGminer. What do you mean with "exact syntax"? Try bfgminer -o stratum+tcp://78.27.191.182:8349 -u 1YourBTCaddress -p x
|
|
|
|
my pool has over 200 connections to my miner why?
It is also growing
I pull the lasted version from git.
I don't know the reason.
I use Debian testing as distribution. Is there a problem in the twisted library?
which distrib do you use?
Seems like this issue was introduced in the latest version. It is being discussed now on last page of the official thread. I am running Ubuntu 12.04. $ lsof -np 4993 | grep -c -e TCP -e UDP
27
$ lsof -np 4993 | grep -e TCP -e UDP | grep -c 127.0.0.1
3
so
..what's the command line for p2pool in, say bfgminer, for a couple of Erupters?
..for a Little SC?
..for 60GH SC?
can i mergemine NMC with it?
It depends whether you want to run your local node or mine on a public one. In first case, you will need enough computational power to run bitcoin and p2pool (that's about 2 CPU cores + 2GB RAM + 10 GB disk space minimum in total), so you obviously can't do it with Raspberry Pi. If you want to run your own node, launch it with python run_p2pool.py --net bitcoin --merged http://<NMC RPC user>:<NMC RPC password>@127.0.0.1:<NMC RPC port>/ -w <port for workers> <BTC RPC user> <BTC RPC password>
then point your miners to <port for workers> (both getwork and stratum are supported!) If you want to mine on a public node, go to http://p2pool.hostv.pl/ (once page loads, reload it again with F5), choose node with least ping (and suitable fee), and point your workers to it specifying your payout address as login and any password. Unfortunately, Erupter blades are currently not supported because of their shitty on-board software which results in about 50% stales on p2pool (details based on my research: https://bitcointalk.org/index.php?topic=18313.msg2622669#msg2622669). Erupter USBs, however, work perfectly. P.S. NMC merged mining is supported if you run your own node. However, it is not pooled! This means you will mine BTC in pool but NMC are mined solo. |
|
|
|
У меня 2 вопроса к тем, кто потерял монеты в результате инцидента. Ответьте, пожалуйста, очень уж интересно!
1. Вы когда уйдете майнить на другой пул, вы тоже все намайненое будете там на балансе держать?
2. Когда тот пул хакнут/сломают/владелец исчезнет, вы снова придете на форум светить своими порванными жопами, так?
наша пісня гарна нова опять хомяки сами виноваты (где тут смайлик-фейспалм) Мне в самом деле интересно, какие выводы сделали люди. Потеря денег сама по себе еще не делает человека лохом. А делает вот это: В прошлом году именно вот на этом месте кинули меня на сотню! А сегодня – на двести...
Более того, такое поведение поощряет и поддерживает мошенников. |
|
|
|
|
У меня 2 вопроса к тем, кто потерял монеты в результате инцидента. Ответьте, пожалуйста, очень уж интересно!
1. Вы когда уйдете майнить на другой пул, вы тоже все намайненое будете там на балансе держать?
2. Когда тот пул хакнут/сломают/владелец исчезнет, вы снова придете на форум светить своими порванными жопами, так?
|
|
|
|
p2pool crashes too often.
I need a stable pool.
I think without these python *** it could be more stable.
There are plenty of nodes with uptime >1month. From my own experience, power losses occur more often than p2pool crashes. If your node crashes often, you might be doing something wrong. Also, no pool has 100% uptime guarantee, that's why mining software has backup pools option. |
|
|
|
|
Another possible solution to AMblade-p2pool issue here!
Blade owners could just fork their own p2pool. The only 4 lines of code which need to be changed are share period, p2pool network identifier (prefix), bootstrap nodes, and optionally chain length. As blade's "effective latency" is about 6 seconds, reasonable values for share period are 5 or 10 minutes.
The hardest part is involving miners. You need about 100 blades in total to reach mean rate of 1 block per day. At this hashrate, 1 blade's expected time to share will be 8 and 17 hours for 5 and 10 minute share period correspondingly (or even less if multiple-blade miners adjust their difficulty properly). Maybe someone should make announcements here and in AM blade discussion threads to get feedback and estimate how many blades will support this.
|
|
|
|
Bitcoin network
* Increase SHARE_PERIOD (average time between shares) from 10 seconds to 30 seconds, in order to make it more fair for high-latency miners (read: ASICs)
also...this hasn't been done yet, right? I think it has been done but switch to new share version will occur when most hashrate upgrades. P2pool graphs show only 1% new version now. |
|
|
|
Why would they fix this only in the usb version?
Usb version is controlled by third-party mining software like cgminer and others. Blades are controlled by closed-source software written (poorly!) by some AM's partner company. I guess the only thing can be done here is waiting until AM fixes its dumb software for its smart chips. |
|
|
|
Brief report of p2pool + AM block eruptor blade investigation
1) Blade always works on difficulty 1, regardless of what server tells, so p2pool must always provide diff 1 pseudoshares to account solved work properly. This does not affect real shares difficulty, which can be tuned as usually.
2) Blade does not use long polling. Instead, it makes about 4 getwork requests per second. Looks like it makes as much requests as it can, each providing work to one chip. With 32 chips, it means about 8 seconds per full round. Maybe it doesn't send solutions before doing this full round; this must rersult in about 50% DOA. Or maybe results are put into queue and wait while software is busy requesting new work. In both cases, running it locally may help. Also, I'm not sure that real share DOA will be as high as pseudoshare DOA.
3) "p2pool + stratum proxy + AM blade" setup has some authorization-related issue. This is all I can tell by now, will try to get more details.
P.S. With the difficulty tweak, it works giving about 50% pseudoshare DOA. Real share efficiency is unknown because of little statistics. Those who have AM blades may give it a try at 78.27.191.182:8353 (with your payout address as username).
P.P.S. A question to any developers here. May I officially state that AM blade software is a piece of crap? No stratum, no long polling and constant difficulty in the year 2013. It might be OK for their internal mining but not for a sold product!
Update! At last, the blade's mining mechanism is clear to me. Like in AM USB, found solutions are reported immediately. However, unlike AM USB and like BFL devices, work is not restarted. This means that a chip keeps mining the same work for about 12 seconds (I guess it corresponds to full nonce range of 32 bit, and is equal to average chip's time per one diff1 share). Since solutions are reported immediately, this must give slightly less than 50% DOA shares. There's a solution that can considerably increase mining efficiency on p2pool for ASIC devices, and this solution is... share difficulty. By setting it high you not only help small miners, but also protect yourself from orphan shares! If you are mining with x10 share difficulty, your "DOA" shares will most probably get into the chain, since your share's work is bigger than even 9 min diff shares. With current mindiff of 1500 and expected time to block of 30 hours, ASIC miners (except AM USB which works fine) can set their diff to 15000 without any serious increase of variance. Shares which are first reported DOA in p2pool node log may still get into the chain! |
|
|
|
|
Brief report of p2pool + AM block eruptor blade investigation
1) Blade always works on difficulty 1, regardless of what server tells, so p2pool must always provide diff 1 pseudoshares to account solved work properly. This does not affect real shares difficulty, which can be tuned as usually.
2) Blade does not use long polling. Instead, it makes about 4 getwork requests per second. Looks like it makes as much requests as it can, each providing work to one chip. With 32 chips, it means about 8 seconds per full round. Maybe it doesn't send solutions before doing this full round; this must rersult in about 50% DOA. Or maybe results are put into queue and wait while software is busy requesting new work. In both cases, running it locally may help. Also, I'm not sure that real share DOA will be as high as pseudoshare DOA.
3) "p2pool + stratum proxy + AM blade" setup has some authorization-related issue. This is all I can tell by now, will try to get more details.
P.S. With the difficulty tweak, it works giving about 50% pseudoshare DOA. Real share efficiency is unknown because of little statistics. Those who have AM blades may give it a try at 78.27.191.182:8353 (with your payout address as username).
P.P.S. A question to any developers here. May I officially state that AM blade software is a piece of crap? No stratum, no long polling and constant difficulty in the year 2013. It might be OK for their internal mining but not for a sold product!
|
|
|
|
I can understand that shares decrease in value as the total number of shares in the block increases (hence the overall downward sloping of the flat regions). But what explains the jumps up and down? I only have one orphan, and 9 valid shares in this block... (two found during the time plotted there).
Payout system in the pool is PPLNS, which stands for pay per last N shares. Jumps down occur when one of your shares becomes so old that it is excluded from those "last N shares". Thus, not every share is actually paid. However, this works both ways! When a block is found, your payout will not drop to zero but remain the same, so you may eventually get paid several times (from several blocks) for the same share! |
|
|
|
|
Could someone who has AM blades grab one and mine on 78.27.191.182, ports 8353 and 8354, for about 5 minutes on each please.
First one is p2pool node worker port, second is getwork port of stratum mining proxy, which itself is directed to the same node.
I am trying to debug with some tweaks.
Thanks!
|
|
|
|
When was the last time that P2Pool found a block?  - all blocks + luck charts |
|
|
|
Why does this happen?  After two days I have 10 shares and 1 orphan and 2.4% DOA? Am I doing something wrong? I think it's just variance. If you don't find shares for a long time, your current payout starts decreasing (as your older shares become outdated). |
|
|
|
|
Show Posts
