DarkGravity Well (typo in the abstract) jumped right at me. Sux, I am at work, so having to read this on phone. I could definitely help reword some sentences. We really need to enrich the document with mathematical and code snippets from DGW and some other key DarkSend areas. Evan, I am with "them". A whitepaper is absolutely necessary to appeal to scholars. Thanks, updated! |
|
|
|
Highly unlikely as they're chosen randomly
But still possible. Checkout the whitepaper, master nodes don't control the collateral payments anymore. It's payment nodes, which are the last 2 block solvers. So it's the pools that would have to collude, in which case we'd know and stop using them. http://www.darkcoin.io/downloads/DarkcoinWhitepaper.pdf |
|
|
|
Already darkcoin forks popping up, if darkcoin wants to be a success there has to be more innovation ^^.
More innovation? You mean like the DGW, that was implemented literally a few minutes ago? DarkCoin "forks" popping up that don't contain DGW or DarkSend.... More like Litecoin forks with scientific hashing.  AS i sayd, i think darkcoin took a great track, but it has to sustain. There is a very good reason im here now  , and its the only alt crypto i ever recognized as worth my time . I wholeheartedly agree. This can't be the end of the innovation by any means - DRK needs to be understood as THE privacy innovation crypto, and we all need to get behind Evan on that. All these pump-dumpers complaining that "Darksend's never finished" can go hang. Any dev worth the project they're working on knows encryption features are never 100% "done". I'd love to see it to be the first cryptocoin to implement the latest developments in quantum cryptography, or something similarly newsworthy. I have no idea if that's even possible, but we need to shoot for the stars! Well like I've said before, this is my full time job. After DarkSend is done and opensourced, we'll move on to whatever the community wants. I just want to make a coin to take the 2nd spot, I think we can do it. There's not many coins with a full time dev onboard. #2 spot! Now that's the kind of ambition I like! eduffield is different from 99.9% of the other coins "devs". Most are just a copy and paste, with a few changes to blow rewards and crap. Full time job, working on it for years, DarkSend, listens to community , clearly a bloody smart guy with huge ambition. I could go on and on. But with eduffield, I have supreme confidence in this coin. Just can't wait for the full DarkSend release! Almost everybody who holds this coin has and should have confidence, but comments like "750m market cap this year are realistic" are a little exaggerated. Who seriously think that DRK will go beyond $1500. I hope noone is that delusional I don't know. I can get pretty wacky when I open my dark wallet. Any chance of a clock timer on the release of DarkSend? I know its probably not the best idea to do a fixed time for release, but it would be nice  haha yeah that would be very nice, but I'm sure it's too hard to pinpoint when it will be ready exactly. I'm sure it will be released as soon as it's done! I think we're all like raging bulls all pumped up and anxious to for the release of DarkSend, so we can burst into the ring and get promotion the hell out of this coin and it's features! I know we can't put a date on it, but I'll be over the moon if we see it by the end of the month! What is Evan's confidence level with the current rate of development and the previously estimated release date? If he can commit to a certain date, a countdown timer to when DS will go live and then another for code release may very well result in a boost to short term exchange rates. By the way, does anyone know whether Armory is completing any transactions using DRK at this point? I am not worried in the slightest about short term exchange rates and don't care about a set release date which will add pressure. I would rather Evan spend the time getting the codebase and everything right before we go live. I don't care how many beta tests we have as long as once its released and verified by the community there are no show stoppers. +1. Totally agree. Last thing anyone wants it a failed launched of DarkSend. It's great that evan wants to get it perfect before it goes out of beta. I'm glad I've been part of the beta testing. So here's the plan for development, tell me if this makes sense or not: 1.) Beta V4, V5... - Large changes that require everyone to upgrade to use DarkSend 2.) Beyond this point, DarkSend is ready for real use and will be available in binary form (closed source still) 3.) Release Candidates - RC1, RC2, etc - I'll be taking bug reports, but these are smaller changes and none of them should require everyone to update 4.) First stable release - I think this stage should also be closed source until we're sure everything is perfect 5.) Public audits, where the closed source is shared with someone who people trust to review DarkSend (I'm not sure who that would be yet) 6.) After all audits pass and we have a real product, opensource |
|
|
|
how do you defend against attackers who try to DOS by requesting to be part of a joined transaction but then fail to sign off on the transaction? This is the big problem with coinjoin that prevents it from scaling well. have you guys solved it somehow?
There is a penalty for leaving the connection before the darksend completes. And how does that work? You put up a collateral transaction that only the current master node can cash to get into the pool. If you misbehave in any way, the master node will cash it. Each time that costs 0.1DRK, so it could add up pretty quick if you're attacking it. Masternode's are chosen randomly using a deterministic algorithm that can't be tampered with. This has a nice side effect, people will want to run full nodes to get the random fees. So we should have a pretty strong base of nodes. what prevents masternodes from being dishonest? bump Dishonest how? I think I covered everything here: https://bitcointalk.org/index.php?topic=421615.msg5717144#msg5717144what stops the masternode from cashing all of the collateral transactions of participants who do sign off on the transaction? That's a great question I haven't gotten before! I've thought of that and I'm planning on implementing a slave node which will also sign off on the transactions. So the transactions require 3 signatures to cash. |
|
|
|
Are there any bounties for light or Android wallets? I developed one of the Doge lightwallets and would love to contribute to the DRK community
That would be great. Please contact LimLims, he has all the bounties  Thanks Evan Done! That's a good idea, I have it in two stages: - Make a lite android wallet - Darksend compatible android wallet |
|
|
|
I'd just like to know what they are, what they do, who hosts them? Are these ip's from wallets? Is that why I'm confused?
How are the 'addnode' s created? I don't get that part, LOL But I do see what you mean above, and understand, just still curious about the other Can you clarify what you mean? Oh you know, those addnodes we put in our darkcoin folder? addnode=54.80.16.112 addnode=23.23.186.131 addnode=50.16.206.102 addnode=50.19.116.123 addnode=98.165.130.67 addnode=54.242.50.205 addnode=50.17.98.53 addnode=54.225.43.37 Where do they come from? What do they actually do? Are they running some kind of software? Are they websites? Sorry I didn't know what you meant, it seems obvious in hindsight. Right now those are centralized DarkSend master nodes. They are static and never change, pretty much the same as Blockchain.info's CoinJoin mixer. The code Evan is working on will not need those. That's where the hash of the previous block comes in to play. To summarize: hash(block) -> some kind of mapping -> IP address. Every client will simultaneously run this computation and know that that particular client is the master node. It will be seamless to the end user. You won't have to add any nodes to your config. Evan(definitely) and InternetApe(assumption) are hosting them. I guess I still want to know how they are created/function and presumably what software they run We host a few full nodes, there's just normal darkcoind. |
|
|
|
one more question, does anyone know for certain if the exchanges have updated their clients in time?
I do, I contacted all of the personally. They all updated quickly. Thank you, it's good to know Yeah I tried! I suppose at least a week before a hard fork is needed beyond this stage of the coin. We were so limber a few weeks ago! |
|
|
|
one more question, does anyone know for certain if the exchanges have updated their clients in time?
I do, I contacted all of the personally. They all updated quickly. |
|
|
|
out of several rigs all using the same set-up and configs, this rig is the only one playing up. I'm wonder if I should try a pool server closer to the UK:  Like I said, every now and then there is a bunch of rejects that lead to this rig being banned from drkpool. I'll fix that, it's a bit sensitive. We had people running scrypt and it was recording all of their shares for 10 minutes before banning them, so I patched the code to be much more quick about it, maybe I overdid it. Thanks |
|
|
|
how do you defend against attackers who try to DOS by requesting to be part of a joined transaction but then fail to sign off on the transaction? This is the big problem with coinjoin that prevents it from scaling well. have you guys solved it somehow?
There is a penalty for leaving the connection before the darksend completes. And how does that work? You put up a collateral transaction that only the current master node can cash to get into the pool. If you misbehave in any way, the master node will cash it. Each time that costs 0.1DRK, so it could add up pretty quick if you're attacking it. Masternode's are chosen randomly using a deterministic algorithm that can't be tampered with. This has a nice side effect, people will want to run full nodes to get the random fees. So we should have a pretty strong base of nodes. what prevents masternodes from being dishonest? bump Dishonest how? I think I covered everything here: https://bitcointalk.org/index.php?topic=421615.msg5717144#msg5717144 |
|
|
|
Evan,
Just wondering what you think the effect of "stealth addresses" in bitcoin would have on DRK? Do you think it will devalue DRK? Would it provide the same level of anonymity as DarkSend?
Thanks!
I don't think they're nearly as strong as something like DarkSend. Although, I could implement that into the client and call it "StealthSend" or something. |
|
|
|
cd /home/user
sudo rm -r darkcoin
sudo rm -r .darkcoi[/b]n (backup your wallet and conf BEFORE doing that)
git clone https://github.com/evan82/darkcoin
cd darkcoin/src
make -f makefile.unix USE_UPNP=
./darkoind &
ENTER
cd ../..
cd .darkcoin
replace the created wallet with your wallet and also put in the darkcoin.conf
cd ..
cd darkcoin
qmake "USE_UPNP=-"
make[/b]
./darkcoin-qt &
OR
cd src
./darkcoind &
There must be something wrong with the source.... are you running on 64 bit or 32 bit...? These are my steps and it still ends up on the wrong fork.. This is a total cluster FK... rm -rf .darkcoin rm -rf /usr/bin/darkcoind git clone https://github.com/evan82/darkcoinmake -f makefule.unix USE_UPNP= darkcoind & tail -f .darkcoind/debug.log drk@cpool:~/darkcoin$ darkcoind getinfo { "version" : 90000, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 34139, "timeoffset" : 9, "connections" : 6, "proxy" : "", "difficulty" : 278.98827638, "testnet" : false, "keypoololdest" : 1394936545, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } Try stopping the daemon, deleting ~/.darkcoin/chainstate, blocks and restarting. |
|
|
|
The simplest way to protect against the time warp exploit, in all its forms, is with a simple rule about blocks whose timestamp is before the previous block.
Just make an adjustment to the difficulty baseline so they don't get the benefit of difficulty adjustments made after their own timestamp.
In other words, if a new block is timestamped prior to the previous four, you proceed as if the base difficulty were the same as it was prior to those four blocks.
poof, every time warp exploit in the world becomes impossible.
I'm not sure, if this is enought. Hasn't he got those 4 blocks cheaper? He still can go far to the future and stay there generating cheap blocks, waiting real chain to catch in time. There is a rule in DGW making it so it won't include the timestamp if that is the case, plus it uses a different strategy that is far more simplistic. The KGW exploit was done against Darkcoin in the mainchain, so I ran it against DGW and it seemed to work just fine. |
|
|
|
Due to exploits found in KGW, I've implemented a new difficulty retargeting algorithm called DarkGravityWave. What is DarkGravityWave? It uses multiple exponential moving averages and a simple moving average to smoothly adjust the difficulty. This implementation is far more simplistic and better suited to adjust difficulty than KGW and also fixes all known exploits. Here's the commit if you're interested: https://github.com/evan82/darkcoin/commit/07c99052edc617975cdcbe4482e02c52e2d1fbf5 |
|
|
|
I cant get my coins off the old official pool the automated and manual system is not working for me!!!!!!!!!!!!!!!!!!!!!!!!
Who do I contact to fix this on the 20th my Coins will get taken from me.
Email me at evan@darkcoin.io and we'll figure out what's going on. Thanks |
|
|
|
Already darkcoin forks popping up, if darkcoin wants to be a success there has to be more innovation ^^.
More innovation? You mean like the DGW, that was implemented literally a few minutes ago? DarkCoin "forks" popping up that don't contain DGW or DarkSend.... More like Litecoin forks with scientific hashing. AS i sayd, i think darkcoin took a great track, but it has to sustain. There is a very good reason im here now , and its the only alt crypto i ever recognized as worth my time . I wholeheartedly agree. This can't be the end of the innovation by any means - DRK needs to be understood as THE privacy innovation crypto, and we all need to get behind Evan on that. All these pump-dumpers complaining that "Darksend's never finished" can go hang. Any dev worth the project they're working on knows encryption features are never 100% "done". I'd love to see it to be the first cryptocoin to implement the latest developments in quantum cryptography, or something similarly newsworthy. I have no idea if that's even possible, but we need to shoot for the stars! Well like I've said before, this is my full time job. After DarkSend is done and opensourced, we'll move on to whatever the community wants. I just want to make a coin to take the 2nd spot, I think we can do it. There's not many coins with a full time dev onboard. |
|
|
|
|
Show Posts
