Search results

Unfortunately debug.log has been deleted :(

Hi, Did anything happened with network last night? I noticed strange behaviour: block 531712 - reward 4.12613683 - diff 23585.14327135 block 531715 - reward 3.89230205 - diff 23789.59304741 block 531719 - reward 3.88373917 - diff 20374.78004697 Then my daemon crashed several times, diff went...

Hi, hanlab is nicehash as far as I know... EDIT: Anyway - I can do few things but I cannot force miners to move somewhere else. This is actually miner choice what he is doing with his hashrate. Problem exist in hashrate centralisation, because as I said peviously hanlab (nicehash?) itself...

Hi, I think you put too much attention to botnet miner because hanlab user is responsible for 41% of total hashrate in last 24 hrs. All remaining users (approx 176) on my pool generated 15% of blocks in last day. The real problem is that there is not so many miners in total to even the hashrate...

coinmine.pl is already updated

this blocks comes from older version of network but it is being rejected by current version

and unfortunately chain from cheating pool won :|

coinmine is updated...

@evan or devs - something happened with spork functionality - my pool wallet suddenly rolled back approx 100 blocks and then started from the beginning. I had to manually adjust DB on my pool. Apart of this I had 3 orphaned blocks in last 3 hrs which is very unusual. Here is debug.log...

coinmine.pl pool updated

and this is my chain as well

at least onyx daemon has higher diff and more blocks on it so i suppose this is a orrect chain :| anyway - after Core reindex it is on chain now, but I am a bit afraid to switch to it until Evan will release the fix or something

only Onyx keeps correct chain at this moment - all my new daemons forked

Network forked again - my pool was on wrong chain for few hours and I switched back to previous daemon version

a tak przy okazji... ostatni update zajal mi pewnie w sumie ze dwa dni (najpierw serwery stratum nie mogly znalez bloku, potem po poprawkach byl zly getblocktemplate, i w koncu dzis sie udalo zmigrowac na nowa wersje...) Poza tym po update moje masternody sie wylaczyly po godzinie, choc je...

haha - mam dosc czytania wszystkich wiadomosci po angielsku, zeby jeszcze na wszystkie podfora zagladac :) bede wpadal od czasu do czasu

no to ja tez sie przywitam ;)

yes - I did update yesterday and I had few messages in stratum server that blocks were rejected by daemon... In wallet debug.log I saw messages that masternode payee cannot be found (or similar) and blocks were not accepted at all. EDIT: I had to revert to previous version then

anything changed in the code since yesterday? I posted that upgrading wallet on my pool caused blocks not being accepted. How can I be sure now it will not happen anymore?

something is wrong with this version: I updated wallet on my pool and found blocks were rejected by deamon. I had to revert to previous version. Unfortunately I dont have debug.log file but there were messages that masternode payee cannot be found...