|
ShadowCash Proposal Conditions
1.) Converted funds will be locked for a period of 90 days
2.) We're looking for some kind of commitment from the core team that they'd work on darkcoin for at least a year beyond this. They could work on whatever they like, at the pace they're working now.
3.) DRK Will be paid for in a 1:1 relationship, dollar wise from this moment forward. 494909 (SDC MarketCap) / 9833182 (DRK Market Cap), therefore 5.03% of the total number of DRK coins will be created on a future block, totaling 240277DRK. The exchange rate will be 31.33SDC for 1DRK.
4.) SDC users will be awarded DRK based on coins destroyed and signed (sign the private key proving you own the key). A user will send coins to a non-redeemable address, if those coins for example equal 1% (64435 SDC) of the total number of SDC ( that would amount to 2056DRK being awarded.
|
|
|
|
why don't they just join DRK instead... not need another coin  never heard of shadowcoin before The proposal merges the two coins and they'll keep whatever stake they had, but in Darkcoin instead. It's the first "coin-merge" to ever happen in crypto. Hopefully this is not intended at a 1 to 1 ratio? No, there's a conversation rate between ShadowCash/DRK to keep the same value. |
|
|
|
why don't they just join DRK instead... not need another coin never heard of shadowcoin before The proposal merges the two coins and they'll keep whatever stake they had, but in Darkcoin instead. It's the first "coin-merge" to ever happen in crypto. |
|
|
|
We're currently in talks with the ShadowCash developers to join the teams together and become the second largest team in crypto. As the twitter states , it's not about their technology, we already have a working anonymity implementation. It's about the team itself, their programmers and designers are top-notch and we could go far together. This should greatly benefit both teams. It's hard to survive in crypto and there's a great cleanup that's happening right now. Darkcoin will survive and through a merger they'll come out ahead too. For anyone who wants to read the proposal as it stands: https://docs.google.com/document/d/1HrGDKKtr5cKKE8Iu7aOw1vXbVTGk9078sQaWlprZYrs/edit?usp=sharing |
|
|
|
I see some people are running a newer version. I see mn's on 10.15.20 and 10.15.21
is 10.15.19 not the best/newest now?
15.20/15.21 have some caching improvements and bloom filters for broadcasting (much less bandwidth). I've gotten the load of my server down to about 1/6 what it was. Feel free to test if you want: https://github.com/darkcoin/darkcoin/tree/dsee-improvements |
|
|
|
is it possible to burn drk for drk 2.0 to get rid of old clients and start fresh?
its not a real proposal, just wondering if its technically possible.
Each protocol bump should kick everything else off the network, and thus be a fresh start. This enforcement thing has been holding back development since May. The current mining architecture just isn't a good fit for what Darkcoin is trying to achieve. I have proposed making mining via Masternodes mandatory many times, and just get called a 'Nazi' and a 'retarded fucking Jew' (by the same people...  ) - the nearest I've had to a sensible argument against it is that pools need beefier hardware than Masternodes, but why not require pools to obtain compliance tokens from Masternodes first that are required for a block to be accepted? There are lots of ways it could be done but nobody seems interested. I am more and more coming to believe that PoW is a dead end. Centralised pools do not secure the network, they are a security liability. Nobody wants to talk about it. Mining costs do not translate into coin value. Nobody wants to admit it. For the last six months PoW has just held back development, it has done nothing whatsoever to add value. Shifting block reward in favour of Proof of Service is a good move, but the timeframe is too long and it's meaningless if PoW can still fuck things up. PoW has been a spanner in the works for half a year now, my fear is that it is also going to make InstanTX unworkable as well. BUMP BUMP BUMP Couldn't agree more! This would cause an immediate hard fork. All new clients would only talk amongst themselves and the old ones would still be mining. Mining pools for example, would need to update the moment it came out to avoid 100% of their blocks getting orphaned. |
|
|
|
looks like you can grab it from github already .. but lets wait till Evan gives an official announcement.
Feel free to start updating. I'm just compiling it and writing the announcement. edit: v0.10.15.19 is out. Added a bit of debugging and another sanity check |
|
|
|
Enforcement caused forks yet again and it's been disabled. Anyone not on the correct fork just needs to restart the daemon with --reindex and it'll be fine. Can anyone who was stuck on a fork please email me the debug.log to evan@darkcoin.io? |
|
|
|
|
Enforcement is active!
getcheckpoint
{
"synccheckpoint" : "00000000000169b3d57f49f0319cf571999258ad2a8e612ffbbeff5a510c50d6",
"height" : 163496,
"timestamp" : 1415024853,
"subscribemode" : "enforce",
"enforcing" : "on"
}
|
|
|
|
2. Masternode IP obfuscation will make the MN network basically invisible as well if done right.
When is this being built? What is the priority? Shouldn't the priority of this be higher than instantx? I agree it should be, but seems like the "flashier" instantx will be arriving first. Actually, I am worried that IP obfuscation is off the table as I haven't heard anything about it from Evan in months.  It's definitely not off the table. Actually, it's been replaced with a multi-path routing algorithm. Instead of the one direction communication like the old way, this will support 2-way communication without revealing your IP. https://darkcointalk.org/threads/open-source-announcement-and-future-plans.2528/ |
|
|
|
Anyone that had a client on the wrong fork, please send your debug.log to evan@darkcoin.io |
|
|
|
I've disabled enforcement for the time being. There are a couple daemons that have forked randomly throughout the day, this needs to be looked into in depth to figure out what's going on, then it will be re-enabled.
darkcoind getcheckpoint: {
"synccheckpoint" : "00000000003a2be2024a4ce8589c8dc229c6dc0205e9af9c118e0b1a12caad76",
"height" : 160436,
"timestamp" : 1414545317,
"subscribemode" : "enforce",
"enforcing" : "on"
}
Not workee? It takes a minute: getcheckpoint { "synccheckpoint" : "0000000000396d4a5a17ef07d21d116468f35947ff31f9ed28503c30d7fdfd10", "height" : 160440, "timestamp" : 1414545437, "subscribemode" : "enforce", "enforcing" : "off" } |
|
|
|
EDIT: Suchpool are on the case. Great pool as always.
We did resync, we seem to maintain it now. We have no clue why the network forked, enforcement was live since a couple hours and we have been paying the 25% rewards as soon as the patch got out, and also were on the latest wallet 15 minutes after the update has been released. This will need to be investigated, for the moment it seems to hold. I've disabled enforcement for the time being. There are a couple daemons that have forked randomly throughout the day, this needs to be looked into in depth to figure out what's going on, then it will be re-enabled. |
|
|
|
|
Let me know about payment distribution in a couple days. I can make changes if need be.
|
|
|
|
Successfully enabled enforcement.  getcheckpoint { "synccheckpoint" : "0000000000166aaacca1d17a941d7a09460a3512e9af6ab5d5b677e29d600121", "height" : 160228, "timestamp" : 1414511509, "subscribemode" : "enforce", "enforcing" : "on" } |
|
|
|
|
Show Posts
