Search results

Any idea what happened to wiki.darkcoin.eu? I went to edit it regarding opensource status, and it didn't load this morning at all... tried now (8pm here), again down... Is it a glitch on elbereth's server? I haven't got a copy of the texts, or the FAQ, on my hard disk, although they could...

What the f*** is this? They locked DRK thread... (?)

Instead of going full-blown anonymity services through masternodes, can't we just have a good IP obfuscation network through masternodes, so as to anonymize Darkcoin transactions?

What do you want to add / change in the wiki? (if you mean the normal one and not the reddit one - as you wrote)

I think it's also related to masternodes knowing what they transact, from past posts.

Sounds like a plan... will it be trialed on testnet first to see how it works? If yes, do a test with a client that maliciously tries to "enforce on" to see what happens in that scenario and also do a simulation run on what will happen when we activate "enforce on" on the main network and some...

That's for the darkcointalk.org webmaster to fix it (propulsion?)

http://wiki.darkcoin.eu/wiki/FAQ#I_have_1000_DRK._How_do_I_set_up_a_Master_Node.3F I placed it as "alternative guide" at the bottom.

Since RC3 is delayed and we'll have more time to check things, please perform some examination and hardening on time-related attack vectors. As far as I'm aware this area could use some checking and could also present a problem if such vectors are found. You* might want to try hacked clients...

It's all about expectations. You announce that you hope to get it right but, as has been seen so far, this is a tricky update and might as well need patching. One solution would be to do what Vertcoin does with merge mining of their testbed coin. They apply the changes to the merge-mined test...

I'm worried that the fork is a bit on "autopilot" and we'll have many on the wrong forks. People won't just update because they are in sync with our own bubble-reality of DRKness where we monitor these things 24/7 - they have lives to run. 1. There's too little exposure on the fact that there...

My mind seems to be pretty efficient in retaining relevant pieces of information to whatever I'm interested at, however I do use a search engine to find posts. So it's half memory and half search engine...

I'm posting this here because it was deleted on bitcointalk by a mod, for no apparent reason: Things that can be paralleled by using developer resources from developers wanting to help or through bounties: 1. I2P 2. "Your client needs update" code for every wallet that is forgotten in some...

https://bitcointalk.org/index.php?topic=421615.msg5727866#msg5727866

Someone will have to test this because I'm not engaged with testnet debugging.

BUMP'ed after the hacked client exploit in payments. Any assumption* that a client has for other clients (that they will perform as expected) should be fail-safed. Whether it is proper version reporting, network communication, payments, etc etc. The exact opposite assumption is the basis, that...

From what I read there are quantum-resistant algorithms for that purpose - however I'm not aware of their other pros/cons... The ecdsa that bitcoin uses though is as good as dead when a QC comes out (or if it's already out and nobody knows): https://bitcointalk.org/index.php?topic=3008 (nice...

1. Quantum computing resistance for public/private keys. The algorithm currently used by Bitcoin isn't QC-proof. It will allow DRK to be "first Quantum Resistant" - offering hedging and diversification options for Bitcoin holders and expanding the innovation frontier. This will require some very...

If someone hacks a client to show correct protocol version but has mismatching behavior (due to being different), can he sabotage the network?