Search results

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

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

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.

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

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.

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

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.

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

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)

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.

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

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

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

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

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

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

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

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. :(

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

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".