Search results

tungfa From what I read Evan sent an e-mail to the distribution list of pools, exchanges, etc. I did not see a specific post detailed the exact time or block for enforcement. Check out: https://darkcointalk.org/threads/v10-15-onyx-release.2683/page-37#post-27820

This seems to be related to permission issues: Forbidden You don't have permission to access /wp-content/uploads/2014/09/ on this server. Apache/2.2.22 (Ubuntu) Server at www.darkcoin.io Port 443 Also, on https://www.darkcoin.io/downloads/ The 'lock' icon for PGP is not appearing:

Isn't the spike more perceptible with DRK as sending payments after anonymization would require grouping considerably more inputs that with a classical BTC transaction? Especially in oblox's example where he sent his whole balance at once to a new wallet?

Hey MangledBlue, JGCMiner was only trying to help... This has been requested by flare earlier in this thread:

Sent 1111 tDRK, transaction ID: b4f8cff8d705bffdf84b38d205e206d3cd8bfd1a5942c0c7dd8574a38b7b4618

David is exactly right. I am not talking about the initial creation of the wallet that requires the generation of 1000 keys (see screenshot below). I get this systematically every time I start darkcoin-qt.exe. Notice, it does not mention generating the keys anymore: It is also interesting...

The darkcoin-qt.exe client takes about 1 minute and 30 seconds to start each time and remains stuck on the start-up screen (Loading wallet...) during that time. My hardware: Windows 7, Intel Core i7-2600 @ 3.40 Ghz, 8 GB RAM. DRK-47 created on jira.darkcoin.qa...

If found back this explanation from Evan in the RC4 testing thread:

mmZncG5zJL5S84j7DQz5JZjZPibCqmm7pH Thanks!

Just sent 444.88888888 tDRK with anonymous funds (8 DS rounds) transaction id : 6a602b0e61cd50f97e85fc1ec3bb5be3c55e14a1045ecf801d247d7d469d97b0

Can you not use the build prepared by flare and available in the following post? https://darkcointalk.org/threads/rc5-testing.2245/page-3#post-19041 Sorry if it doesn't help, I'm a windows/linux user myself.

My wallet has been anonymizing like crazy the whole day; currently 10k out of 13k anonymized through 8 DS rounds. If anyone wants me to send some tDRK to play ping pong, feel free to give me your address!

I am running a windows wallet at home with about 13k tDRKs with 8 DS rounds with an anonymized amount set at 30k. I will report back on the progress later today.

I'll have a windows wallet continuously denominating tDRKs. I'm also willing to send tDRKs back and forth to generate some transaction traffic. flare Can you keep us posted once you know more about the test plan for RC5? Thanks!

It was added on testnet in version 0.x.12.4, see - usemasternode: But was only meant in RC for testing purposes.

To achieve this, we could have stayed with RC4 on testnet longer to make sure things were working properly instead of going to mainnet with immature software. There was no hurry to go live. Now things are different as there is buggy software on mainnet and the need to fix things quickly (or...

As discussed on IRC, I could rephrase my concern into : "Where will DRK stand in another 6 months?" Based on past performance, I doubt we will have a functional solution by then if nothing changes.

Thanks for your reply, fernando. That's how I would have felt a couple of releases ago. However, we are systematically confronted to structural failures and the need to go back to the drawing board to redesign core functionality instead of building further. Hence why I'm losing faith.

I believe now is a critical time to look back at the past months and carefully consider options for the future of Darkcoin. While there still is a core group of people living in the "Cult of Evan" I am starting to think that DRK is in trouble. Talk about cognitive dissonance. The initial hype...

flare Short digression to thank you for all your efforts related to testing and following up bugs and issues here and at jira.darkcoin.qa I can see you do a lot of work behind the scene! We need someone like you to put structure into all this :wink: