Search results

  1. kryptofoo

    v0.11.0.x Core Testing

    Known issue? v110005 win-32
  2. kryptofoo

    v0.11.0.x Core Testing

    Having 3rd party software manage and transmit wallet passwords sure makes me nervous. Not for myself (I would not use this until it is widely tested by a very large community) but for others who may run into trouble if it is buggy or worse.
  3. kryptofoo

    v0.10.17 - Onyx v3

    I ran into a similar issue, albeit while testing v11 on testnet. I finally got my windows-qt client to sync by creating a new wallet.dat - seems my old wallet.dat was too large or otherwise incompatible. Once sync was done I could open the old wallet.dat file, but decided to send all funds to...
  4. kryptofoo

    v0.11.0.x Core Testing

    My win32 qt client v110004 just keeps on denominating until there is nothing left to denominate. It does not adhere to the "amount" setting.
  5. kryptofoo

    v0.11.0.x Core Testing

    Looks like the "unlock wallet" popup dialog remembers the checkbox "for anonymization only" setting from the previous unlock. When trying to send funds I did not notice that this box was still checked. After clicking send I get an error message saying "the wallet was unlocked only to anonymize...
  6. kryptofoo

    v0.11.0.x Core Testing

    I also have the 0 balance issue on the send tab, darksend is 100% complete for 1022.1 tDRK. Although it shows balance is 0, it still lets me send for example 100 tDRK using darksend funds. win32 client.
  7. kryptofoo

    v0.11.0.x Core Testing

    OK so just finished syncing blockchain with windows-qt-110004 starting from block 0. I used a v1016 wallet which was giving me lots of CPU/hang problems with v110003. This version v110004 worked just fine! The speed issues I mentioned in the previous post were because my VPN was connected, after...
  8. kryptofoo

    v0.11.0.x Core Testing

    Testing now with windows-qt-110004. So far so good on the CPU but still 22 weeks behind; looks like it is syncing MUCH slower in this version is that expected? also, I see a ton of ORPHAN BLOCK messages in debug.log for example 2015-01-09 17:55:01 ProcessBlock: ORPHAN BLOCK 751...
  9. kryptofoo

    v0.11.0.x Core Testing

    Status bar shows 94% - far from accurate - and a bunch of inputs already have 5 and 6 rounds of darksend. Darksend also overshoots requested anonymous amount by a lot (see previous posts). I don't know, it almost feels like we have a bit of a darksend verschlimbesserung in this version. Edit...
  10. kryptofoo

    v0.11.0.x Core Testing

    even though I have 1820 tDRK in my darksend balance on overview tab (has finished my requested 4 rounds), on the send tab my darksend balance shows 0 tDRK. has this been reported already? Edit: seems I can still send the anonymous funds by selecting the inputs in coin control
  11. kryptofoo

    v0.11.0.x Core Testing

    Anyone knows why darksend overshoots the final balance by so much in this version? for example I ask for 1000/8 rounds and end up with 2700+ darksend balance. or, I ask for 1000/4 rounds and end up with 1820 darksend balance. The v10 clients were getting much closer to the requested amount.
  12. kryptofoo

    v0.11.0.x Core Testing

    hmmm, testing seems a bit slow this time around. my two duffs: It would be great if we had some test scripts for everyone to verify basic and advanced functionality in this new client. I guess there were quite significant code changes in this version and it would be nice if we can avoid a lot...
  13. kryptofoo

    v0.11.0.x Core Testing

    Ooops, darksend overshot... by a lot (started with 0 darksend balance). And still have some 10 tDRK denoms at 6 rounds, darksend continues...
  14. kryptofoo

    v0.11.0.x Core Testing

    Why doesnt testnet set the difficulty back to very low value if no blocks are found in say 20 minutes? thought that was kind of a "standard" feature...
  15. kryptofoo

    v0.11.0.x Core Testing

    in the windows-qt client when clicking start darksend, i am not asked to unlock the wallet. I see the status message "wallet is locked", and I have to unlock it from the settings menu. there used to be a popup...
  16. kryptofoo

    v0.11.0.x Core Testing

    I think it is safe to say my v60001 wallet did not work on the v11client (windows-qt 32bit & 64bit). I can access the older wallet by running a v1017 client on testnet but can't send my tDRK to the new 'y' address in v11, the address is invalid. Edit: I could finally move my tDRK from v10...
  17. kryptofoo

    v0.11.0.x Core Testing

    Thanks for the idea. No block source available with v16 testnet, I guess nobody is running that client any more. This is not a problem for me personally it is only tDRK, but it does raise a big red flag IMO. Thing is, my v1016 wallet still worked with my v1017 clients, I did notice some CPU...
  18. kryptofoo

    v0.11.0.x Core Testing

    I got my windows-qt client working. I had to delete my old wallet.dat and use a new wallet, this seems to have solved the client hanging errors. The wallet was from an older v16 client. Maybe I missed a line somewhere telling me to upgrade my wallet? So I created a new wallet, let the client...
  19. kryptofoo

    v0.11.0.x Core Testing

    I switched to the 32 bit windows client which I thought was working fine, but after a while it is hanging again, pegging one CPU core, blockchain stuck at 7 weeks behind. I was unable to get to the settings menu to change the option you suggested, because the client was unresponsive immediately...
  20. kryptofoo

    v0.11.0.x Core Testing

    Thanks - the 32bit version is working fine!
  21. kryptofoo

    v0.11.0.x Core Testing

    anyone else having trouble with the windows-qt 64 client? On my PC (win8 64 i5 8GB SSD) it pegs one CPU core and becomes unresponsive while trying to update blocks. I have deleted the whole testnet3 subdirectory and tried fresh install, everything goes great until about "11 weeks behind" then...
  22. kryptofoo

    v0.10.17.x Testing

    progress bar is buggy, goes to 100% long before darksend is completed. V101718 windows-qt
  23. kryptofoo

    v0.10.17.x Testing

    Oops now I'm getting a bunch of blank transactions and collateral charges. Actually it seems darksend mixing should be completed, I have already reached the target rounds and amount, but it keeps on going with these blank TXs and collateral charges.
  24. kryptofoo

    v0.10.17.x Testing

    Nice - darksend is working again and is fast in v101717. No longer getting any blank transactions or strange error messages in v101717. Just a few nuisance items perhaps: When I am anonymizing 2000 tdrk 4 rounds, I still have a lot of denoms going through 5 or 6 rounds. My completion bar reads...
  25. kryptofoo

    v0.10.17.x Testing

    Took me 26 transactions (and a lot of work selecting inputs) to consolidate all those UTXO's into one single input. Now I'm going to start anonymizing again, 2000 tDRK 4 rounds, let's see how things end up this time.
  26. kryptofoo

    v0.10.17.x Testing

    After denominating 2000 tDRK 4 rounds on version 10.17.04, I am struggling to do anything with my darksend funds in version 10.17.08. I am trying to sweep my funds into one address so that I can restart the darksend process but I am either getting "transaction too large" or "unable to find...
  27. kryptofoo

    v0.10.17.x Testing

    This was probably reported here but my client does not seem to respect the "darksend rounds to use" setting. I have it set to 4 rounds but many of my denoms have reached 5 or 6 rounds so far. Win32-qt client.
  28. kryptofoo

    v0.10.17.x Testing

    Just loaded up 101701 wallet on my windows box. Only showing 1 masternode on testnet? Planning to add 3 MN's once the ubuntu stability issue is resolved. I for one would feel much better about testing such a groundshaking feature as intantX on at least a 100MN network testnet. A double spend...
  29. kryptofoo

    v0.10.16 - Onyx v2

    I'm also running 16.05 on my MNs; masternodes list is empty according to all of them. CPU load has stabilized, with a few surges to 40-50% (amazon m1.medium)
  30. kryptofoo

    v0.10.16 - Onyx v2

    i had two MN's that spiked CPU for about 30 minutes after start then settled down. The others seemed OK. Running them on M1.Medium AWS instances. My masternode list is strange on every server is different as others have noted. My masternodes feel very lonely.
  31. kryptofoo

    v0.10.16.x Testing

    6000 TDRK, 4 rounds, stalled at 17% getting "Last Darksend was too recent" messages now.
  32. kryptofoo

    v0.10.15 - Onyx Release

    I forgot, how many blocks before a new masternode becomes eligible for selection & payment?
  33. kryptofoo

    What other altcoins are DRKcoiners into?

    Just curious, what is your definition of "failed"? If purely price based, why rule out PoS on past price performance.
  34. kryptofoo

    Masternode Proof of Stake

    Can you briefly describe how a masternode p2pool network would work? Am not grokking this idea. Edit: Doesn't restricting mining to masternodes still leave us with an arms race resulting in large mining operations that can afford high powered equipment? In this case, we would just be adding the...
  35. kryptofoo

    Masternode Proof of Stake

    Anonymity and instant TX is Darkcoin's calling card. How it implements consensus is another matter. Getting tired of huge pools not updating, having huge share of the network from time to time, and not paying or reluctantly paying masternodes. Give 100% of the reward to masternodes and let them...
  36. kryptofoo

    Onyx Release & Mining Pools

    Are you sure you mean the masternodes would perform mining in the form of PoW, or do you mean they are simply responsible for consensus and signing blocks as in a type of PoS scheme? I can understand the latter but not necessarily the former. I started a thread to try and capture this topic...
  37. kryptofoo

    Masternode Proof of Stake

    Folks including myself are getting ever more concerned about centralization of mining operations on Bitcoin and of course in our beloved darkcoin PoW network. Is this community open to even considering moving to a sort of Masternode/Proof of Stake system? I'm talking about ending PoW and...
  38. kryptofoo

    v0.10.15 - Onyx Release

    Nice work, thanks! Bummed that you decided to wait one month for enforcement. Two weeks seems like more than adequate time to notify people and get the majority updated. :(
  39. kryptofoo

    v0.10.15.x Testing

    It does seem like a reasonable compromise to make sure payments are equal and cannot be gamed. But please be sure to explain it thoroughly up front to head off the uproar. if it gets mentioned only in passing e.g. as a single bullet point in the release notes, the community may latch on to this...
  40. kryptofoo

    v0.10.15.x Testing

    update: successfully got through one round of darksend, then had payment to yourself 0.1 DRK, got one "collateral not valid" error message, now just rotating between "submitted to masternode, waiting in queue" and "idle".