Search results

  1. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    darkcoind sendtoaddress mghAuBWNMdeqm5TzvevY5i91nqd6Kyj17A 3333 8d93ea34ef4f4b3cdea66231a2d736a1fc9ad9fe119ebdd03b5d0b628af31b9c
  2. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    give me an address to send some drk to for testnet
  3. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    finally got home to check... all my blocks where good and I am at block 24771. I just let it run and it worked itself out.
  4. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    I am stuck on 24628 now... estimated at 24639 4 immature solo blocks. will see what happens..... gona drive home now.. 1.5 hours.
  5. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    downloaded: v0.9.11.2-ga950f31-beta from the bamboo server running. had to reindex... still it is stuck on 24616.. gona let it run, i have seen them clean themselves just running. solo mining against qt: OK. edit: wonder how this works since it is not up to date ! [15:53:25] Found block...
  6. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    Thanks.. everything looks good now.
  7. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    I'm in: I thought I was in.. can anyone see my node? I only have one in my list.. been running for about 10 to 20 minutes. ubuntu@ip-10-252-56-205:~$ darkcoind masternode list { "54.189.217.227:19999" : 1 } now I have two: darkcoind masternode list { "54.189.217.227:19999" : 1...
  8. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    lol.. duh.. what was i thinking. Thank you
  9. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    DarkCoin version v0.10.11.2-1-gb779377-beta
  10. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    wont start. just downloaded. DarkCoin server starting ubuntu@ip-10-252-56-205:~$ ubuntu@ip-10-252-56-205:~$ darkcoind: main.cpp:2294: bool SetBestChain(CValidationState&, CBlockIndex*): Assertion `pfork != __null' failed. ubuntu@ip-10-252-56-205:~$ ubuntu@ip-10-252-56-205:~$ darkcoind getinfo...
  11. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    I still get this: ubuntu@ip-10-252-56-205:~$ DarkCoin server starting ubuntu@ip-10-252-56-205:~$ ubuntu@ip-10-252-56-205:~$ darkcoind: main.cpp:2294: bool SetBestChain(CValidationState&, CBlockIndex*): Assertion `pfork != __null' failed.
  12. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    after updating to recent: darkcoind ubuntu@ip-10-252-56-205:~$ DarkCoin server starting ubuntu@ip-10-252-56-205:~$ darkcoind: main.cpp:2294: bool SetBestChain(CValidationState&, CBlockIndex*): Assertion `pfork != __null' failed. ubuntu@ip-10-252-56-205:~$
  13. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    darkcoind sendtoaddress mjZ4dgpGMw3kGQJNT87e4wWujg5a3Aynic 3333 6bc4a0485804c0d17c082a6d0cc58d7ceb894587ca277e7af09c1ee4126a5077
  14. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    are the window versions compiled?
  15. jimbit

    v0.10.11.x RC3 Prelaunch Testing

    my MN has b953b04943c1af8c4df601b428050fd41c28cab0ef5e6884e0ca8d2e470b76a9 but my mining rig, solo on qt is on a fork me thinks. this rig was definetly on the proper fork last night and nothing has changed except the MN was updated. getblockhash 24574...
  16. jimbit

    RC3 Relaunch Strategy and Testing

    So when do we need to be ready/running our nodes? This is a good idea!
  17. jimbit

    v0.10.9.x Help test RC2 forking issues

    I am getting about 3 to 4 blocks per hour with one gpu against a solo qt win client..
  18. jimbit

    RC3 Relaunch Strategy and Testing

    We call it a spork :)
  19. jimbit

    v0.10.9.x Help test RC2 forking issues

    this guy is getting lucky on voting: cce48bd2c49675e73d49d45c0f633de72367430d darkcoind masternode votes { "24321" : "OP_DUP OP_HASH160 6480e797bbf4ef1838d8ac4a9aa1d7f2e6b2f538 OP_EQUALVERIFY OP_CHECKSIG", "24322" : "OP_DUP OP_HASH160 8ca15c286e4b02067579cbe24eec6a5cb22007dc...
  20. jimbit

    v0.10.9.x Help test RC2 forking issues

    I was unsuccessful.... all of my hours worth of blocks have been orphaned.... proper chain wins. after a -reindex soloing on the proper chain now... found block 24061 with hash 00000001183fc6478c1ace79a4e9b1d65072b1685f748717b6320a93b5174c11 if anyone is interested in seeing if we can get...
Back
Top