Recent content by ozziecoin

  1. O

    v0.10.12.x RC4 Testing

    Enjoy a nice beer or three mate. You deserve it.
  2. O

    v0.10.12.x RC4 Testing

    My wallet denominated, but too well - went 5 rounds instead of 4.
  3. O

    v0.10.12.x RC4 Testing

    Try this. Change darksend rounds in options to 4. Wait for rounds to continue. I think the wallet is able to perform up to 5 darksend rounds.
  4. O

    v0.10.12.x RC4 Testing

    However, no deal breakers appeared, AFAICT.
  5. O

    v0.10.12.x RC4 Testing

    While you are on "send" screen go to console and type "darksend auto" - do inputs get sent to MNs?
  6. O

    v0.10.12.x RC4 Testing

    Working good over here. No complaints at all.
  7. O

    v0.10.12.x RC4 Testing

    Just update to latest version - v.19. Sent 3000 tdrks to address in wallet using "no preference". System started denominating automatically and immediately. However, the system got stuck at end. After 33 confirmations, there remains about 600 tdrks not denominated: Edit: debug log -...
  8. O

    v0.10.12.x RC4 Testing

    It cleared. Not sure when.
  9. O

    v0.10.12.x RC4 Testing

    Three inputs appear to be locked for a few hours:
  10. O

    v0.10.12.x RC4 Testing

    Flare has not updated Win v.17 to fix locking issue.
  11. O

    v0.10.12.x RC4 Testing

    If fees can be lowered by one decimal, this might be good for community.
  12. O

    v0.10.12.x RC4 Testing

    Suggest that total balance should reflect sum of anon plus unconfirmed:
  13. O

    v0.10.12.x RC4 Testing

    Now properly selecting darksend inputs! http://test.explorer.darkcoin.fr/tx/e1d41e062bcde724d6a69ae3984ad3d7a5486e04143e9fe8736814089b09aa88
  14. O

    v0.10.12.x RC4 Testing

    Loads of MNs now: { "184.73.179.148:19999" : 1, "54.191.236.39:19999" : 1, "184.73.179.187:19999" : 1, "184.73.179.196:19999" : 1, "184.73.179.235:19999" : 1, "149.255.109.167:19999" : 1, "108.61.198.220:19999" : 1, "50.191.199.127:19999" : 1, "66.172.33.248:19999" : 1 }
  15. O

    v0.10.12.x RC4 Testing

    From here: http://stackoverflow.com/questions/22389442/bitcoin-wallet-dat-corrupt-salvage-failed "You need to run the client with the -salvagewallet command-line option which moves any existing wallet.dat to wallet.[timestamp].dat and then attempts to salvage public/private keys and master...