Search results

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

    v0.10.12.x RC4 Testing

    Yes. To prevent DDOS but I was thinking even with 10,000 wallets - the system is capable of handling that.
  17. O

    v0.10.12.x RC4 Testing

    Found the issue. The wallet.dat appears to have been corrupted. So I ran -salvagewallet and it seems to have fixed up the problem.
  18. O

    v0.10.12.x RC4 Testing

    It is a bit bizarro. My best guess is that somehow I have received someone else's 900 Drks during mixing process somehow. Edit: I have sent the funds to you Tante but it doesn't show up: http://test.explorer.darkcoin.qa/tx/77981d35b89f4d2955b69f5a5fa759e84f905663b94ca48f27378bf1ea6b0987 Edit2...
  19. O

    v0.10.12.x RC4 Testing

    Check dropbox link for entire list. :)
  20. O

    v0.10.12.x RC4 Testing

    Anything for you Tante: true 2014-08-07T09:42:16 Payment to yourself -0.003 07d91a5434d5a9d2aefffe71c270b0cd520b9e9a34187f967e2357378cd74ebd-000 true 2014-08-07T09:38:47 Payment to yourself 0 d6fc90f176df397234957cd61f5f7a72d9bee3b0dbc46663eddcd9904f7c38a5-000 true 2014-08-07T09:37:01 Payment to...
  21. O

    v0.10.12.x RC4 Testing

    Sure tante: see this: http://test.explorer.darkcoin.qa/tx/53b1f215204ddf9bb54dcd05ea1f978e370d3437790700cb624cce0bc006e890 That was pretty much all the coin that was there. I transferred out 1000 test Drks, the wallet used all the inputs automatically. Edit: I want more Drks but not like this ;)
  22. O

    v0.10.12.x RC4 Testing

    Linux Daemons will run with darksend off by default. Encryption also prevents denomination, AFAIK.
  23. O

    v0.10.12.x RC4 Testing

    Can someone help me figure out what is going on? I had approx. 5121 Drks at 08:50. I did the upgrade to v.16 I transferred 1000 Drks at 08:59 (I think using "no preference" option) Transaction id...
  24. O

    v0.10.12.x RC4 Testing

    I think only coinz3 would be concerned about this :)
  25. O

    v0.10.12.x RC4 Testing

    My linux wallet started denominating after 4.5 hours. One collateral bug to report.
  26. O

    v0.10.12.x RC4 Testing

    Try this: Create a new address. Send yourself most of your Drks to that new address within your wallet. Choose "no preference". Then wait for it to denominate. I think the client gets stuck.
  27. O

    v0.10.12.x RC4 Testing

    Anyone else's Linux QT wallet having issues denominating?
  28. O

    v0.10.12.x RC4 Testing

    I just got latest version and it still says: v0.10.12.12-6-ge798b71-beta Edit: But has synced to block 9413
  29. O

    v0.10.12.x RC4 Testing

    Possibly, you need to wait for your daemon to catch up to correct block height.
  30. O

    v0.10.12.x RC4 Testing

    Me too. Anyone else out of sync? I'm going in sync, out of sync, in sync, out of sync. No internet issues at my end AFAIK.
  31. O

    v0.10.12.x RC4 Testing

    I think the fact that multiple wallets will be used for attack is obvious. IP banning is useless, that is also obvious. No one knows how the signing process occurs (other than Evan) but collateral is required, which is deterrent in itself. Also, presumably the amount to be denominated must be...
  32. O

    v0.10.12.x RC4 Testing

    Let's assume a DDOS attack is being launched. The person would need to run many, many wallets and to manually force darksend denom. If wallets are being auto denominated, perhaps fee should be waived. Edit: To run lots and lots of wallets with auto denom, will take so many Drks that the cost is...
  33. O

    v0.10.12.x RC4 Testing

    And the auto denomination is going into all sorts of random addresses now. No collateral bug here also. Wonder, how this was done, as I have not even updated my client? Edit: The transaction fee is tiny but due to frequency will worry some people. They might think it will keep draining funds.
  34. O

    v0.10.12.x RC4 Testing

    Me too. Two counts so far:
  35. O

    v0.10.12.x RC4 Testing

    yidakee, from memory, I think collateral goes to collateral wallet. Fee for auto denom goes to miners but as you pointed out should probably be free, or at least let people control what is auto denominated.
  36. O

    v0.10.12.x RC4 Testing

    What is latest version number? My client seems to stuck trying to denominate. I appear to be on: v0.10.12.9-2-g06365bc-beta
  37. O

    v0.10.12.x RC4 Testing

    Thanks. I guess merchants will run encrypted wallets then.
  38. O

    v0.10.12.x RC4 Testing

    woah, how many transacts in 28 mb wallet?
  39. O

    Development Updates - July 7th

    Any comments from dev team re: potential dust and blockchain size? Thanks. :)
  40. O

    RC3 Soft Fork

    I think we were lucky some of the multipools updated because it was not in their best interest. The unknown pools are unlikely to update, IMHO. The random banning of some MNs is a little bit worrying though. Anybody know what is triggering it?