I just noticed this thread. Gonna quote some things. I was that PM he was talking about.
I've addressed several concerns about Digital Commerce Coin (dCM) via private message and I've intentionally tried to keep it off of our Einsteinium thread. I've made a few posts in the past regarding what happened but there are still people who still need answers. I hope this helps.
What is (was) Digital Commerce (dCM) coin?
Digital Commerce Coin was a cryptocurrency initially developed by KryptoKreative, Wallenstein, and SeriousCoins. After it's initial inception, bobsurplus and aszu were brought in by KreativeKytpo and as such I was contacted to offer release support, wallet design, graphics, and marketing plans. The initial goal of the coin was to be focused exclusively in API creation and e-commerce adoption. dCM was released on Bittrex as a 130btc IPO (divided between 6 devs) before releasing on the market for open trading.
What was my role in dCM coin?
As stated above, my role was to do graphics, marketing, wallet design, logo, etc. I created the wallet graphics and setup / operated social media accounts. It was also my role to offer my percentage of IPO funds back into the coin. Within the first 1.5 weeks I had already spent 5 btc on renting hash, supporting the price, hiring a developer for PoS fixes, paying for the merchant center backend, and server fees. I was not a lead dev by any means, but whoever controlled the ANN thread placed my name up as "lead dev" which is very misleading.
What happened to dCM?
Within a few days of our release, there was another coin (Harmony) that literally copied our ANN and tried to copy our success. This upset a few members of our team to the point of publicly addressing the issue in the Harmony forum. I think this is where the rift started within the team. There was a lot of big problems between KreativeKrypo and Bobsurplus that seemed to stem beyond what was happening with Harmony. Bobsurplus left the team and a lot of problems happened in public which drove our price below IPO level and breaking my buy support. At this point, it seemed the team stopped communicating as a group. Messages would go ignored or unanswered and the core team would be offline for days on end. I was locked out of the ANN thread and my name was moved up as a lead dev. I am still waiting and trying to figure out what happened to our plans. All of IPO money I've received is still being kept intact, unspent, and waiting for news on what's going to happen with it. A lot of people are calling the coin a scam, but I assure you that was not the intention at all. The coin fell like a house of cards due to FUD and it scared away the lead devs.
What is the future of dCM?
Honestly, similar FUD campaigns were used on Einsteinium which caused the price to drop heavily. I stuck through to make sure the coin didn't die and now I am spending extra time to rebuild EMC2 into something valuable for investors. Once Einsteinium is a success, I may take full control over dCM if the original devs don't come back. I'm not a quitter and I stand by everything I do. Please let me know if you have any more questions about dCM via private message.
Also here is the windows wallet file.
https://www.dropbox.com/s/bdus007am89p6o8/dCom-qt-1.02.exeSome people have been having trouble syncing. I wouldnt doubt that the blockchain is forked. If anyone wants, i can dropbox my appdata folder sans wallet.
As of writing this, here are some console commands and values im getting.
getblockcount = 102984
getcheckpoint =
{
"synccheckpoint" : "dc303d701db0e49bc5456cc7b1f0fae645f3fa31261fa3600a3d56ebeb8275f5",
"height" : 102979,
"timestamp" : "2014-09-03 21:12:38 UTC"
}
getconnectioncount = 4
getdifficulty =
{
"proof-of-work" : 0.21441682,
"proof-of-stake" : 0.00031395,
"search-interval" : 134
}
getinfo = (i removed some personal info / nonsense from the result)
{
"version" : "v1.6.2.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"newmint" : 0.00000000,
"blocks" : 102986,
"moneysupply" : 1535997.09057900,
"connections" : 4,
"difficulty" : 0.21441682,
"testnet" : false,
}