• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Search results

  1. F

    Network Issues

    Unfortunately debug.log has been deleted :(
  2. F

    Network Issues

    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...
  3. F

    51% HASHRATE COINMINE.PL !!!

    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...
  4. F

    51% HASHRATE COINMINE.PL !!!

    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...
  5. F

    V12 Release

    coinmine.pl is already updated
  6. F

    11.2 - Dash Release

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

    v0.11.1 - InstantX Release

    and unfortunately chain from cheating pool won :|
  8. F

    v0.11.1 - InstantX Release

    coinmine is updated...
  9. F

    v0.11.1 - InstantX Release

    @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...
  10. F

    v0.11.1 - InstantX Release

    coinmine.pl pool updated
  11. F

    v0.11.0 - Darkcoin Core Release

    and this is my chain as well
  12. F

    v0.11.0 - Darkcoin Core Release

    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
  13. F

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    Tutaj sie witamy [ Niech Moc Bedzie z Wami]

    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...
  16. F

    Tutaj sie witamy [ Niech Moc Bedzie z Wami]

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

    Tutaj sie witamy [ Niech Moc Bedzie z Wami]

    no to ja tez sie przywitam ;)
  18. F

    Mandatory : All users must update to v0.11.1.x

    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
  19. F

    Mandatory : All users must update to v0.11.1.x

    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?
  20. F

    v0.11.0 - Darkcoin Core Release

    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...
Back
Top