I just got an interesting email warning against a possible attack vector against Darkcoin, someone could possibly DDOS multiple pools and lower the difficulty enough so that we'd get back into the older CPU based formula. I doubt they could make this work (and make a profit), but I believe preventing it by locking us into the GPU difficulty calculation is the correct thing to do. I've updated the source, which goes into effect on block 24000. I'll be messaging all of the pools and asking them to update their wallets. To be clear this change does nothing if we're not attacked. We would only fork in the case of an attack on the network. Thanks! This is the fix: https://github.com/evan82/darkcoin/commit/970f9d202aeb90c5d9168736a07c05ed0e2fc448 |
|
|
|
|
The official pool is humming along again, we're getting blocks and we've lowered the transaction fee to 0.01 for withdraws. Anyone who left, come on back! Thanks
|
|
|
|
Hi guys
When will the darksend be implemented?
Regards
DarkSend is coming along great, I've fixed all of the issues that were brought up during the last test and the last couple days I wrote up the anonmizing tech that lives in DarkSend. It looks like it's working great, so I should be announcing a test date where everyone can try it out soon.
Next DarkSend test, 100% of sent transactions will be anonymous. Looking forward to showing it off! |
|
|
|
Seems like the guy may be trying to return the c-cex funds as we speak....maybe.
On a separate note, does anybody know if DRK supports multisig? If is is based on bitcoind fork, it should, but with all the wonderful changes, I am not sure if that still works with DRK. Yes, still supported. In fact It'll be used in DarkSend by default in a very unique way, but I'll get into that later  |
|
|
|
|
Pool.darkcoin.io is working again, a cron got an error and payments were halted in the middle of the night. It's grinding through the last 70 blocks and paying everyone, so it's taking a bit.
drk.coinmine.pl is TOO BIG, please move your miners away to another pool!
|
|
|
|
pool.darkcoin.io not finding any blocks???
Sorry, crontab wasn't running. Just updated to a new server |
|
|
|
Yes, updating. Almost done. |
|
|
|
|
We're going to be doing planned maintenance on pool.darkcoin.io here in a bit. We're upgrading it, should be really nice!
|
|
|
|
New logos, splash screen and everything has been updated in the windows client! Thanks to Sigi and the rest of you for helping to design the look and feel of Darkcoin, check it out if you're interested: http://darkcoin.io/downloads/darkcoin-qt.exe |
|
|
|
|
I just updated the logo, splash screens, about screen and site to the new blue/metal logo! We'll be uploading a new client soon with the new logos.
|
|
|
|
The poloniex manipulation is nuts - they are killing the price and c-cex is staying stable - rising in fact.
Anyone know why polo is so easy to manipulate and c-cex not? It seems like they are taking buy/sells back and forth from one exchange to another and making profit that way.
Just asking - it seems this way and it seems like it could kill confidence.
I suspect that it's because people are realizing Poloniex may be insolvent because of the XCP debacle. I'm not comfortable depositing BTC there right now to buy Darkcoin even with the current price discrepancy and the wonderful opportunity for arbitrage. Care to fill us in on the XCP drama? I haven't been following that, what happened? |
|
|
|
When is the next round of testing?
I've fixed most of the issues we were encountering (the transactions for 0.00DRK showing up, etc) and now I'm working on the anonymity part. I should have something testable this upcoming week, I'll announce a date soon. |
|
|
|
Ok guys, pool.darkcoin.io locked my account for no reason. I tried to contact them twice via email but no response.
I dont care about account, but i have ~25 darkcoins there. That's 2 week mining for me!
So i need advice, how to contact, who is responsible?
Thanks.
That's my pool, shoot me a PM with your user info and I'll unlock it. |
|
|
|
- Block reward is controlled by moore's law: (11111 / (((Difficulty+51)/6) ^ 2))
Please help me to understand. http://explorer.darkcoin.io/block/00000000000295e2ecbbeb3b69f1ff9aaf24d2aebaefd534cfd22857e668d0a1Block 22067: Difficulty: 57527.019 Generation: 22 + 0.004 total fees 11111 / (((Difficulty+51)/6) ^ 2 = 11111 / (((57527.019+51)/6) ^ 2 = = 1.207 * 10 ^ -4 != 22 So I understand the block reward formula in the wrong way. Please explain. Also, as 22 is a whole number, there needs to be an INT() or round(__,0) somewhere thanks :-) The GPU formula is a bit different, we switched to it when they became available via blockchain folk. It's 2222222/(((x+2600)/9)^2) and it's modeled to better represent the variance of difficulty that they bring to our mining pools. i.e, under CPUs a move from 1 to 10 difficulty was large, but under GPUs a move from 100 to 110 is nothing. Thanks for the explanations. Very interesting approach to couple block reward and difficulty directly. Yes, now I could calculate it. It's 22.3382606 though, not 22. Where is the INT() ? The formula got changed - please correct posting #1 of this thread. And the block explorer is telling nonsense - Difficulty: 57527.019 The variable is an INT it's calculated in. I'll look into the diff later, thanks. |
|
|
|
- Block reward is controlled by moore's law: (11111 / (((Difficulty+51)/6) ^ 2))
Please help me to understand. http://explorer.darkcoin.io/block/00000000000295e2ecbbeb3b69f1ff9aaf24d2aebaefd534cfd22857e668d0a1Block 22067: Difficulty: 57527.019 Generation: 22 + 0.004 total fees 11111 / (((Difficulty+51)/6) ^ 2 = 11111 / (((57527.019+51)/6) ^ 2 = = 1.207 * 10 ^ -4 != 22 So I understand the block reward formula in the wrong way. Please explain. Also, as 22 is a whole number, there needs to be an INT() or round(__,0) somewhere thanks :-) The GPU formula is a bit different, we switched to it when they became available via blockchain folk. It's 2222222/(((x+2600)/9)^2) and it's modeled to better represent the variance of difficulty that they bring to our mining pools. i.e, under CPUs a move from 1 to 10 difficulty was large, but under GPUs a move from 100 to 110 is nothing. |
|
|
|
lol, how is this effectively different than a premine?
Neither the devs or anyone else got a fixed % of coins at the beginning. Doge is not premined either but people who start at the very beginning get the benefit of making coins more easily. That's not how you see it? That's the way it is supposed to be. The block reward formula's + KGW == Whale Harpoon. It see it as being a critical part of the success we've seen thus far. |
|
|
|
I'm not sure if anyone else has worked on this but I've created a draft media release about DarkCoin and the testing. I think it's important to get the word out now that DarkSend is in development and then follow up with another release once DarkSend is active. I'm not the most tech savvy person so would appreciate some help if I've got anything wrong but it may be better for it to be in layman's language considering the readers will largely be non tech media (and consumers of media)! I think it needs a quote from the Dev so I've added space in there for that. Someone also needs to be the media contact (also Dev?). Also, it would be good to start a mailing list of media (reporters who are currently covering Bitcoin and others) to send these releases to. Maybe someone could start a spreadsheet on Google docs or something? Here is the draft release: http://pastebin.com/UYRDqkRtThis is great, thanks! Here's an edited version with a quote from me. Let me know if you need anything else http://pastebin.com/2uFZ6R5g |
|
|
|
I meant transactions like 10.25636012 what happens to the .00636012 if you're only going down to two decimal places, and won't that make the .00636012 easy to track?
With that implementation there must be rounding to the lowest denomination, so the payment would be 10.25 or 10.256. I think the smallest denomination should be about a penny in value, so if the price rises we could add lower denominations. |
|
|
|
|
Show Posts
