Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 829. (Read 1260636 times)
May 09, 2014, 07:52:19 AM
could someone summarize the problem please?
May 09, 2014, 07:40:14 AM
Danbi,
If you can take ANY other groestl coin (what..all three of them?) and have it work in a heart beat, which they do, its not the stratum, its the coin.
If you can take ANY other groestl coin (what..all three of them?) and have it work in a heart beat, which they do, its not the stratum, its the coin.
True, you can make other groestl based coins work, but this is only part of the game. There is other hashing involved besides groestl in DMD and the other coins.
Still hacking, but so far, we have two choices:
1. make DMD hash like the other groestl coins and fork (!) again.
2. Modify both stratum AND the miner and avoid the fork. I am currently working in this direction.
May 09, 2014, 07:26:32 AM
The "good" part is PoS is not working in DMD yet, so those investors "have nothing to lose" --- if this could be good thing.
u always lose gathering coinage which u only able gather in your own wallet.
POS have nothing to do with gather coinage
but with trade in coinage for POS rewards (= called minting)
May 09, 2014, 07:18:43 AM
Danbi,
There is nothing for the stratum coders to assist with. This is purely a Dev issue at this point. Groestl stratums work period. Diamonds implementation does not.
If you can take ANY other groestl coin (what..all three of them?) and have it work in a heart beat, which they do, its not the stratum, its the coin.
I've supported diamond and solo mined a fair amount of them, but starting to lose patience myself.
There is nothing for the stratum coders to assist with. This is purely a Dev issue at this point. Groestl stratums work period. Diamonds implementation does not.
If you can take ANY other groestl coin (what..all three of them?) and have it work in a heart beat, which they do, its not the stratum, its the coin.
I've supported diamond and solo mined a fair amount of them, but starting to lose patience myself.
May 09, 2014, 06:48:12 AM
The Criptsy problem is damaging DMD reputation, because all those people who brought DMD as investment simply cannot transfer it safely to their wallets. As you may know, Criptshy does not guaranatee anything there will exist in case of whatever problems. This is also part of their reluctancy to experiment much -- losing someone's DMDs will bring them damage (in bad name). The "good" part is PoS is not working in DMD yet, so those investors "have nothing to lose" --- if this could be good thing.
I cannot speak about others, but dmdpool.digsys.bg is still not working properly. I steal time from other tasks to hack the code and test it with my own limited hashpower.
If there was more support from the coin dev and especially from stratum software authors -- this could have already happened.
The wallet, stratum servers, payment frontends etc are all written in different languages, with many, many special cases to accomodate different coins and I am mostly trying to learn why and how some things are done that way (and most are buggy more than I would personally tolerate for my own software).
I can imagine most other pool operators are in the same situation.
I cannot speak about others, but dmdpool.digsys.bg is still not working properly. I steal time from other tasks to hack the code and test it with my own limited hashpower.
If there was more support from the coin dev and especially from stratum software authors -- this could have already happened.
The wallet, stratum servers, payment frontends etc are all written in different languages, with many, many special cases to accomodate different coins and I am mostly trying to learn why and how some things are done that way (and most are buggy more than I would personally tolerate for my own software).
I can imagine most other pool operators are in the same situation.
May 09, 2014, 06:42:16 AM
Do you have now a working pool ?
Or is it still the "secret private" ones...
if it is still the case, it isn't criptsy damaging DMD and actually criptsy problem is quite a good thing
Or is it still the "secret private" ones...
if it is still the case, it isn't criptsy damaging DMD and actually criptsy problem is quite a good thing
My research suggests that there ARE NO secret pools, but that is still very tentative and I could be wrong. Also, the likelihood of such is very low, as we would have heard about it. In any event, even if they did exist, they certainly aren't having any negative effect on solo mining . . . in so far as my limited research indicates anyway.
May 09, 2014, 06:38:31 AM
Do you have now a working pool ?
Or is it still the "secret private" ones...
if it is still the case, it isn't criptsy damaging DMD and actually criptsy problem is quite a good thing
Or is it still the "secret private" ones...
if it is still the case, it isn't criptsy damaging DMD and actually criptsy problem is quite a good thing
May 09, 2014, 06:32:27 AM
Unfortunately, this situation with Criptsy is damaging DMD in some way (trust). Thing is, we are now in a catch22 situation with Cryptsy -- they have apparently put DMD at low priority, because just like everyone else they do have lots of (other) things to do AND their attempt with DMD didn't work the first time AND they hear DMD is having "some" problems AND the trade volume is low (which means no profit for them) etc..
Everyone knows setting up an wallet is trivial. So blaming Criptsy on that front just makes them even more defensive. The current DMD wallet more or less works stable -- if there are fixes to make it even more stable, those should be released ASAP, especially to Criptsy (and why not everyone else). I mean, just the database corruption fixes. Nobody likes to spend unnecesary time fixing things on the computer, especially those with public support like Criptsy (and pool operators). Computers, after all exist to serve us, not for us to serve them!
Everyone knows setting up an wallet is trivial. So blaming Criptsy on that front just makes them even more defensive. The current DMD wallet more or less works stable -- if there are fixes to make it even more stable, those should be released ASAP, especially to Criptsy (and why not everyone else). I mean, just the database corruption fixes. Nobody likes to spend unnecesary time fixing things on the computer, especially those with public support like Criptsy (and pool operators). Computers, after all exist to serve us, not for us to serve them!
May 09, 2014, 06:28:15 AM
watch it.
May 09, 2014, 06:19:47 AM
Saying that Cryptsy issue is in their hands does not cut it. Sorry, nothing personal here, hopefully just good constructive feedback that is helpful, but if you were working for a multinational, you'd have been sacked by now. It's Friday already, and you've given no more information all week than, we're waiting on Cryptsy!
When I have an issue with someone, be it technical, billing, shipping, whatever, I've got an open ticket, an invoice number, whatever, and contact info. I've got up-to-date status reports on the issue. I've got names and numbers (and e-mails) of the people I'm talking to.
thats the way we tryed it..............
still u see where we are regarding cryptsy
a new unknown exchange managed to add dmd in one day
we offer every help to cryptsy regarding required files blockexplorer and so on
but we cant implement it into exchange
we have multiple support tickets running in escalation state towards the cryptsy second level support since over 7 days
i was working a few years myself in a second level support job i know how to act to get support
we did act right we just didnt get it until yet.....
Now you tell us.
That's a joke to illustrate my point. You need to be doing everything in your power to get things done, and if you are doing that, you need to communicate what you're doing, and that starts with clear information about the issue(s) to begin with, and that's not just with us, but with the entire world: setting the record straight as it were and creating clear and positive expectations for the future.
May 09, 2014, 06:06:47 AM
how do you plan to pos this coin>>
May 09, 2014, 06:03:24 AM
Saying that Cryptsy issue is in their hands does not cut it. Sorry, nothing personal here, hopefully just good constructive feedback that is helpful, but if you were working for a multinational, you'd have been sacked by now. It's Friday already, and you've given no more information all week than, we're waiting on Cryptsy!
When I have an issue with someone, be it technical, billing, shipping, whatever, I've got an open ticket, an invoice number, whatever, and contact info. I've got up-to-date status reports on the issue. I've got names and numbers (and e-mails) of the people I'm talking to.
thats the way we tryed it..............
still u see where we are regarding cryptsy
a new unknown exchange managed to add dmd in one day
we offer every help to cryptsy regarding required files blockexplorer and so on
but we cant implement it into exchange
we have multiple support tickets running in escalation state towards the cryptsy second level support since over 7 days
i was working a few years myself in a second level support job i know how to act to get support
we did act right we just didnt get it until yet.....
May 09, 2014, 05:56:47 AM
The developers should make a presentation of themselves perhaps with some pics. People tend to trust more things/people if they can see them. Just a thought.
hi polanskiman
i agree we should
and we will
but right now we really busy get this coin going in a way as we planed it
and we really thankful for any support from community to community
to save our resources for dev and management tasks
once we out of major pre post and between release stress we will try doing all the stuff thats now on hold
guides
website update
foundation webpage
promotion campaign
broader exchange acceptance
and and and.........
im sure we wont be victims of boreout sysdrom soon
May 09, 2014, 05:56:06 AM
be nice to each other 
compared to other coin communities i always had the feeling
we have here a very mature and helpful community
lets keep it this way
compared to other coin communities i always had the feeling
we have here a very mature and helpful community
lets keep it this way
I am not Jesus. I won't be turning the other cheek.
However, I will be answering appropriately according to circumstances.
I will be trying Diamond tonight.
May 09, 2014, 05:55:54 AM
Time For Serious Damage Control
If you let your guard down with a negatively divergent situation, it can quickly snowball out of control. DMD has lost (and continues to lose) boat loads of promotional capital, and the situation, far from reversing that trend of falling prestige (regardless of whether it's justifiable or not - the mere negative perception is damage enough), it seems to be getting worse.
What is needed in times like these is what has become known as "Damage Control".
Quote
. . . damage control is the emergency control of situations that may cause the sinking of a ship." http://en.wikipedia.org/wiki/Damage_control
That is what I'm talking about here: DMD is in danger of sinking if we don't reverse the current trend quickly.
Saying that DMD is currently a solo miner's paradise may sound good to solo miners, but to the rest of the world it sounds like a loser's consolation.
Now, if "solo miner's paradise" were to come at the beginning of a "PR release" that was followed by something more positive, forward looking, and professional, like "while we are very satisfied with our initial success to date in converting DMD into a solo miner's paradise, that is only the beginning in this first of a kind, revolutionary undertaking, and we are actively working to resolve *xyz issue* with pool mining (stating exactly what the issues are), get the coin trading again on Cryptsy (stating exactly what the issues are) and getting DMD listed on other exchanges, etc., etc., etc.", the perception then immediately moves positive to one of an ongoing, yet quite challenging, project being carried out by very capable people and that is being met with success.
Quote
A crisis communication plan and effective public relations handling will be the difference between your crisis hurting or enhancing your business. How can a crisis enhance your business? By the way you handle it. If you are truthful and react quickly, your business may actually enhance its reputation for being honest, community minded, genuinely concerned and proactive. http://www.evancarmichael.com/Public-Relations/334/Preparing-for-Damage-Control.html
"If you are truthful and react quickly, your business may actually enhance its reputation for being honest, community minded, genuinely concerned and proactive."
What do you think BitCoinMagazine or CryptoPros are thinking about recent developments in DMD? Do you think they are talking about the truthfulness and openness of the Dev team? Do you think they are itching to get in touch with DMD to do an article on this revolutionary change over? Or do you think they are snickering to themselves and maybe even speculating that the blockchain stop at 386228 was caused by a Dev mistake?
Perception and suspicion rule the day when truthful data is not forthcoming. People think the worst! Whether or not it's true! Preventing that is what damage control is all about (to begin with). The blockchain stopped at 386228 and we still don't know why! This forced an accelerated algo change that came with plenty of expected issues, but we still don't know what those issues were caused by or what was fixed! Damage control gets that info out there along with the current actions being taken to remedy the issues, and, remember, if done right, it can even enhance your reputation!
Saying that the Cryptsy issue is in their hands does not cut it. Sorry, nothing personal here, hopefully just good constructive feedback that is helpful, but if you were working for a multinational, you'd have been sacked by now. It's Friday already, and you've given no more information all week than, we're waiting on Cryptsy!
When I have an issue with someone, be it technical, billing, shipping, whatever, I've got an open ticket, an invoice number, whatever, and contact info. I've got up-to-date status reports on the issue. I've got names and numbers (and e-mails) of the people I'm talking to.
Adequate reporting here on the Cryptsy issue would have looked more like this:
Monday: we are in direct contact with Cryptsy
Tuesday: Cryptsy is doing a manual network sync (because they want to for some reason)
Wednesday: Cryptsy is testing wallet transactions
Thursday: Cryptsy has escalated the issue for final approval/resumption of trading
For example.
It's Friday now, an entire week has passed, and we're hearing the same thing over and over again about Cryptsy. It's time to pick up the phone (if you haven't already), and start kicking ass, or the next thing you'll know, we'll be hearing about how Cryptsy doesn't work weekends. . . again. It's time to start talking to other exchanges as well (of course, this requires a PR piece for each new exchange you're talking to . . .), and it's not like they're exactly scarce: http://www.cryptocoincharts.info/v2/markets/info/ It's time to get in contact with other Dev teams if necessary - the DGB Devs are fantastic and very willing to lend a hand . . . and probably very interested in following DMD's lead. Hey, maybe it's even time to hire a freelance, like, Vitalik Buterin, for example (and with that you'd even get two birds with one stone). http://bitcoinmagazine.com/author/vitalik-buterin/
It's time to make things happen, first with good damage control: honest release of information, and all the information, otherwise you leave yourselves open to doubts and suspicions. Second, with a strong plan of action regarding the current issues as reported in that previously mentioned release of information. Third, hard work follow-through on the plan of action.
It's time to get in touch with all your professional contacts. It's time to call in all favors. It's time to ask for favors. It's time to press your business partners like Cryptsy (if you don't they'll take you for a fool, put your issue on the backburner, and deal with other people who are pressuring them more). It's time to find out who is really your friend, and who isn't. It's time to separate the men from the boys.
Please, be clear, this is no "boardroom" shouting match - this is only stating the facts of life as they really are. Any other interpretation of this writing would be considered as completely juvenile and unprofessional. The truth often hurts, but it's also often what it takes to get things back on track. The worst thing anyone can do with truthful facts is to get defensive and lock oneself into a losing proposition. Please don't fall into that trap. Make reality work in your favor instead. Turn the negatives into positives by actively and honestly dealing with them (and if you have been, but not informing, then adjust for that error and correct the problem of misinformation and speculation that is derived from a lack of information, and actively create a positive perception instead). Remember, "if you are truthful and react quickly, your business may actually enhance its reputation for being honest, community minded, genuinely concerned and proactive."
May 09, 2014, 05:44:36 AM
@polanskiman, please don't get the idea that we are all hostile, angry, newbie bashers. Those are the exceptions. Check out this link to get going with solo mining: https://bitcointalksearch.org/topic/m.6562457
@nerioseole, it took me less time to be helpful than you spent on being a prick. Why don't you try being constructive? I gave you a great opening to shine with some collaborative knowledge sharing here https://bitcointalksearch.org/topic/m.6604921 but not a peep from you on it.[/size]
Et voila! someone who knows how to answer normally
In fact I know how to solo mine already. Got a few wallets already running that way. Thanks anyways.
Still I would like to reiterate what I said earlier. The developers should make a presentation of themselves perhaps with some pics. People tend to trust more things/people if they can see them. Just a thought.
May 09, 2014, 05:43:36 AM
A new exchange for DMD, https://sharexcoin.com/market/DMD_BTC
so a new upcoming exchange was able get diamond running
i guess we should use it to show cryptsy what business they waste by not get their deposit/withdraws going.....
edit: i just checked this sharexcoin exchange he seems to be in heavy development i would give it a few days bevor risc some coins trading there
be carefull until we confirm its working i did deposite 100 dmd and no balance arive at exchange until yet
once my issue is solved and i can confirm deposite withdrawall and tradning works i give u a update
for now i suggest dont use this exchange
update my 100 dmd arrived at exchange
someone wana try buy a tiny amount and withdraw it please
over all exchange looks pretty state opf the art with 2factor auth and so on
May 09, 2014, 04:49:46 AM
be nice to each other
compared to other coin communities i always had the feeling
we have here a very mature and helpful community
lets keep it this way
compared to other coin communities i always had the feeling
we have here a very mature and helpful community
lets keep it this way
May 09, 2014, 04:33:46 AM
The coin is already minable solo to your hearts content no pools available we are at 59 diff have fun
Thanks. Appreciated. That's all I needed to know
May 09, 2014, 04:27:21 AM
Duh!! If you would bother to read the treads for 2 minutes, you would notice that it was re-started on April 30th. Mining solo for now. You can do your google search on mining solo also - great sites to read. Sorry, but I won't spoon feed Newbies - google and learn, like we all did.
1 - You know what we say about assumptions right? Google that too.
2 - 2 minutes...
You probably have time to spend reading 44 pages. I don't. DMD is not the only coin I am mining. The information I am asking should be stated on the OP, it's not, thus my post. I did howerver read a few post but since I don't spend my whole day in forums like you seem to do, I asked only to be answered with a trolling post.3 - Didn't ask you how to solo mine. Keep your condescending tone for yourself.
Jump to: