Очень просто. Удивляюсь как ещё такого раньше не произошло.
Я не удивляюсь, а просто интересно, почему произошло именно у нас. А не в сотнях других криптовалют, в том числе и производных от нашего дерева. Так всё? Обновление уже есть? Можно качать?
Есть, но пока не выложено. Сейчас подправлю кое-что, выложу и начну собирать. Если можно IP ноды для синхронизации тоже сообщите. |
|
|
|
а как такое влзможно? достаточно ли только изменить системное время на компе который генерит время или у сети гдето хранится своё время? Очень просто. Удивляюсь как ещё такого раньше не произошло. |
|
|
|
|
По блокчейну не похоже на атаку.
ИМХО, нужно обновление но не обрезание. Вряд ли приведёт данная ситуация к чему-то плохому.
Все мы сейчас в равных условиях. У себя я что-то не вижу чтобы PoS попёр (хотя у меня копейки).
Даже если кто-то очень много закупит - так ему ещё 30 суток ждать до созревания.
|
|
|
|
|
Может не атака а кто-нибуть с большим количеством NVC свой кошель выключил или перегнал средства?
За 6-е неплохие объёмы транзакций были.
Если ветку рубануть то транзакции тоже потеряются.
Плохо что с проблемой на cryptsy совпало, там сейчас народ мечется - форками всеми подряд средства выводит.
|
|
|
|
BIP65 will take effect in the next week and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP65 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.
So, please upgrade to 15.0 now and also tell everyone else to.
I see - very few nodes been updated: http://poolnode.info/http://nodes.p2pool.co/It would be better to change the values in https://github.com/p2pool/p2pool/blob/master/p2pool/networks/bitcoin.py#L15IDENTIFIER = 'fc70035c7a81bc6f'.decode('hex')
PREFIX = '2472ef181efcd37b'.decode('hex') |
|
|
|
|
В свете последних событий на cryptsy кто в курсе, новакоинами вывод проходит?
Всё. вывел. Час прождал. Немного потерял на взлетевшем курсе.
|
|
|
|
P2pool has been updated: https://github.com/p2pool/p2poolI see forrestv has created a new v15 tag in the repo too - maybe some more updates on the way? Thanks forrestv  Edit: Hmmm....since updating my system has locked up twice in 30 minutes. I'm not sure yet what the problem is until I get a chance to check the logs....... After the update, there is no visual changes. My node works without lockings. This message appears periodically (but it was before updating): Unhandled Error
Traceback (most recent call last):
File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
self._runCallbacks()
File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 256, in gotResult
it(res2)
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 233, in it
res = gen.send(cur) # external code is run here
--- <exception caught here> ---
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 284, in _worker
self.func(*self.args, **self.kwargs)
File "/opt/p2pool-btc/p2pool/util/expiring_dict.py", line 109, in <lambda>
self._expire_loop = expire_loop = deferral.RobustLoopingCall(lambda: self_ref().expire())
exceptions.AttributeError: 'NoneType' object has no attribute 'expire' |
|
|
|
Linux wallet? Exist?
I compile it from source code |
|
|
|
It is unlikely that donat will help. I think how can we attract miners to p2pool. The best way to attract is only by increasing p2pol's hashrate. With the increase of hashrate will increase the frequency of receiving blocks. Maybe we should hold an action in support of decentralized mining at least for a few hours to support p2pool. At the certain time, arrange to use all possible power of those who agree. And bring the information about the campaign to all crypto forums. If the action is successful then p2pool by increasing capacity needs to get a few blocks in a row. According to the results of the action you can make a conclusion whether p2pool is necessary at all. |
|
|
|
I often see these messages in different nodes: Unhandled Error
Traceback (most recent call last):
File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
self._runCallbacks()
File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 256, in gotResult
it(res2)
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 233, in it
res = gen.send(cur) # external code is run here
--- <exception caught here> ---
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 284, in _worker
self.func(*self.args, **self.kwargs)
File "/opt/p2pool-btc/p2pool/util/expiring_dict.py", line 109, in <lambda>
self._expire_loop = expire_loop = deferral.RobustLoopingCall(lambda: self_ref().expire())
exceptions.AttributeError: 'NoneType' object has no attribute 'expire' What does it mean? |
|
|
|
По Auroracoin: Любители аврор http://crypto.office-on-the.net:12347/static/ я выгреб устаревшие шары - пошли блоки Пока не накопилось, можно и большой мощностью зайти. Если опять с недельку будет низкий хешрейт то снова накопится, с большими мощностями не зайдёте - будет большой DOA. |
|
|
|
https://bitcointalk.org/index.php?topic=18313.msg13060151#msg13060151Writing in c is very labour intensive (compared to python) so it's a lot of hours work. I charge less for free software than private software since I like to encourage free software use as much as possible. At current exchange rates I charge .29 btc/hr for free soft and .38 for private software. A rough estimate of the time required to rewrite p2pool in c (properly) would be 500 hours work. That's around 150 BTC. 500 часов, один - это просто овердолго. Может есть команды? Отпишитесь в теме.
|
|
|
|
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....? There is a discussion that contains all modified antminer drivers for p2pool? Except for Kano's firmware and my drivers for S1-3, all antminer S* cgminer forks from bitmain have the same driver design flaw. We mention it at regular intervals but it keeps getting forgotten or lost in the discussion by p2pool miners... Maybe does not make sense to do firmware forks for S *, so we are constantly catching up and more and more losing hashrate. Now it is so small that it can be said that p2pool is dead. And many of those who get ASICs, can never replace firmware and getting out on p2pool they switch to a another type of pools. Maybe it's time for develpers to join and modify and adapt it for the new ASICs? Perhaps it's needed to rewrite it on C, as in Python it loads only one core and often on 100% We need creative solutions, or this topic can be closed and we should stop our nodes and move to antpool, f2pool and similar. We should absolutely not, in any way, shape or form, EVER move to AntPool or f2pool. Not only are those pools way too big as it is, but they are also poorly written and take shortcuts that are bad for Bitcoin. In case you don't remember, they caused a fork in BTC earlier this year precisely because of their shoddy software and mining practices. I agree with you, but most people do not understand this. As to your other points, we've discussed numerous times rewriting p2pool in a language that can handle multiple threads. Thus far, nobody's stepped up to take on that challenge. Even so, rewriting the pool code in C or some other language will not handle the underlying problem of crappy cgminer forks not submitting shares which could be solving blocks.
I'm not sure, but why don't we raise funds for the development team that can do this (maybe it's a bad idea). I think we should act more active rather than passively wait for volunteers. |
|
|
|
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....? There is a discussion that contains all modified antminer drivers for p2pool? Except for Kano's firmware and my drivers for S1-3, all antminer S* cgminer forks from bitmain have the same driver design flaw. We mention it at regular intervals but it keeps getting forgotten or lost in the discussion by p2pool miners... Maybe does not make sense to do firmware forks for S *, so we are constantly catching up and more and more losing hashrate. Now it is so small that it can be said that p2pool is dead. And many of those who get ASICs, can never replace firmware and failing on p2pool they switch to a another type of pools. Maybe it's time for develpers to join and modify and adapt it for the new ASICs? Perhaps it's needed to rewrite it on C, as in Python it loads only one core and often on 100% We need creative solutions, or this topic can be closed and we should stop our nodes and move to antpool, f2pool and etc. |
|
|
|
|
Show Posts
