Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 819. (Read 1260636 times)
May 12, 2014, 12:57:19 PM
Why I have on GRS 20 Mh, but on DMD 17.5-18 Mh with the same settings?
How to fix it?
setx GPU_MAX_ALLOC_PERCENT 100
sgminer.exe -k groestlcoin -o http://dmdpool.digsys.bg:3345 -u login -p pass --no-submit-stale --gpu-engine 1170 --gpu-memclock 1020 --thread-concurrency 22400 -I 22 -g 2 --gpu-reorder --scan-time 1
May 12, 2014, 10:13:18 AM
Has anyone interfaced with Cryptsy today about getting the wallet working?
use https://www.allcrypt.com/market?id=732 to buy/trade Dmd works fine May 12, 2014, 10:08:58 AM
Has anyone interfaced with Cryptsy today about getting the wallet working?
May 12, 2014, 08:19:58 AM
Will coins kept in a pool generate POS?
I know I should keep coins in my wallet, but I was just wondering if it behaves the same as an exchange or if the pool or myself will get the extra coins.
I know I should keep coins in my wallet, but I was just wondering if it behaves the same as an exchange or if the pool or myself will get the extra coins.
If you want PoS, you should keep coins in your own wallet.
Most pool software is not designed to handle PoS and at best, that will be "profit" to the pool operator. Or exchange.
Having said that, it is recommended to disable PoS on the pool's wallets (and perhaps exchange wallets), because it may be with negative balance during staking and that might prevent normal operation. Because of this staking is disabled at http://dmdpool.digsys.bg.
So, if you intend to PoS your coins, transfer at earliest convenience from the pool/exchange.
May 12, 2014, 08:12:09 AM
I would be grateful for detailed instructions..
-on how to "activate" POS (if the wallet is unencrypted or unlocked do you even need to do anything?)
-when it definitely starts
-if it actually works already
-and HOW it works. what kind of profit is being generated (what does the 50% POS mean?)
I currently keep my DMD on exchanges for trading, but if POS works and is actually profitable I'd leave some of em in the wallet.
-on how to "activate" POS (if the wallet is unencrypted or unlocked do you even need to do anything?)
-when it definitely starts
-if it actually works already
-and HOW it works. what kind of profit is being generated (what does the 50% POS mean?)
I currently keep my DMD on exchanges for trading, but if POS works and is actually profitable I'd leave some of em in the wallet.
May 12, 2014, 07:34:56 AM
Add:
With all the previous talk about "hacking" things to adapt Diamond that created the impression that Diamond was deviating from the common standard, it's important to know that Diamond is not deviating from the original algo, at least in this case anyway. IMHO, these things need to be prominently reported in periodic status reports.
"hacking" is how we creative types refer to the process of investigating something that is not behaving properly and guiding it to behave. This is applicable to any thing in life, not just software. At least, this is how I understand this English language word.
What you propose is good practice. However, it is very difficult to implement in forum formats like this. Here is a place for collaboration, more or less.
That's correct. That's what I understand "hacking" to mean, and you also clearly explained it earlier in this thread where you were discussing what you were doing . . . where phrases like "changing the code" and "the fact that DMD's implementation is not exactly like GRS's" along with questions about this "unique" implementation and doubts about whether something similar could happen again were also expressed. Putting the facts as we now know them front and center in "bold" (and doing the same with everything else - as much as possible) should help to alleviate at least some of those legitimate worries and fears.
Hope I am finding different ways of explaining how important direct, accurate and timely updating is and that I'm not just sounding like a broken record.
Below I repost part of that discussion of yours with other contributors:
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.
in my thoughts? if the stratum is already working for other coins? even if its only 3 with this algo..... why would someone insist on changing and trying to fix something that isn't broke?
afraid of the fork? but the fork would solve the problem! also if your changing the code to change stratum and other then who says that this wont happen again ? instead of using tried and true ?
just my thoughts on breaking something that is working or not?
sure I understand the challenge of making it work and wanting to prove that your good coders but make this work like the other groestl and if we all have problems then its solved with more then just a single coin right?
The ralationship between wallet (getblocktemplate) - stratum - miner and wallet (getwork) - miner is very, very different.
In the later case, it is the wallet that controls block construction/verification etc. In the first case, it's all three parties.
In the case of the other coins, it "just works", because the neccesary work to support it has already been done. We will do it for DMD as well, don't worry.
The choice to fork again is no an easy one, at least not in this moment. Sure, the fact that DMD's implementation is not exactly like GRS's has been overlooked, but this is done thing, in the past. We need to look in the future, where we have precisely the above choices.
I for myself don't care much about any recognition, but am not feeling easy to have operated a pool and it suddenly stops because a bunch of people insist they don't share any knowledge. This cryptocoin stuff exists on the basis of community trust, which only exists when everything is open source.
common trust? well every moment that goes by and every proprietary and not open source change they make to make this "unique" running the road alone doesn't offer trust.... take a look at the entire world not just a small part of it!
the dev said" 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.
taking the fork would solve the problem and number 2 is simply taking on a doubt full approach on coding that may or may not succeed.
I would think more of trying to get this working as others are working and not simply hack stuff to simply make it work for the moment then later it happens again. or not? but who knows?
with taking the fork it would get this coin back in the running trying to recover some of its credibility and would have several "devs" working on it not just this team
May 12, 2014, 07:32:45 AM
Will coins kept in a pool generate POS?
I know I should keep coins in my wallet, but I was just wondering if it behaves the same as an exchange or if the pool or myself will get the extra coins.
I know I should keep coins in my wallet, but I was just wondering if it behaves the same as an exchange or if the pool or myself will get the extra coins.
every transaction destroy coinage
once u transfer the coins away from pool or exchange they start with 0 coinage in your wallet
pool wallet could mint if it have coins old enought
exchange wallet could mint if it have coins old enought
but no exchange or pool that i know have mechanics that are able to account minted coins to the right user
short answer as exchange or pool user u will never earn any POS rewards for coins u leave there
May 12, 2014, 07:25:08 AM
Will coins kept in a pool generate POS?
I know I should keep coins in my wallet, but I was just wondering if it behaves the same as an exchange or if the pool or myself will get the extra coins.
I know I should keep coins in my wallet, but I was just wondering if it behaves the same as an exchange or if the pool or myself will get the extra coins.
May 12, 2014, 07:19:52 AM
just want to inform the dev that Cryptsy is saying it's waiting for updates from the DMD developers.
Quote
My apologies, DMD is currently under maintenance. All transactions will
resume once its back online. We are currently waiting for the developers
of the coin to get back to us with updates.
Thank you kindly for your patience and understanding.
Have a great day!
resume once its back online. We are currently waiting for the developers
of the coin to get back to us with updates.
Thank you kindly for your patience and understanding.
Have a great day!
They are joking, right?! I've been waiting for their reply for ages and got only silence in response. I left detailed updates on the progress in 'escalated' ticket.. how can they now say they are waiting for our response?!
"this ends tonight"
- angry Spartan
Tech Support Standard Operating Procedure: blame the other guy.
That's why it's critical to be extremely proactive . . . and have the documentation to demonstrate your case.
May 12, 2014, 07:15:40 AM
just want to inform the dev that Cryptsy is saying it's waiting for updates from the DMD developers.
Quote
My apologies, DMD is currently under maintenance. All transactions will
resume once its back online. We are currently waiting for the developers
of the coin to get back to us with updates.
Thank you kindly for your patience and understanding.
Have a great day!
resume once its back online. We are currently waiting for the developers
of the coin to get back to us with updates.
Thank you kindly for your patience and understanding.
Have a great day!
They are joking, right?! I've been waiting for their reply for ages and got only silence in response. I left detailed updates on the progress in 'escalated' ticket.. how can they now say they are waiting for our response?!
"this ends tonight"
- angry Spartan
May 12, 2014, 06:52:55 AM
How is it that the Cryptsy wallet is still no worky?
Could people stop asking this question over and over again, please . What is the point, who do you think will answer this question?
It has already been stated that Cryptsy is a normal company that works week days form 9-5 they are not going to do any work on Saturday or Sunday.
As soon as it's unfrozen you can bet you will be informed.
just want to inform the dev that Cryptsy is saying it's waiting for updates from the DMD developers.
Quote
My apologies, DMD is currently under maintenance. All transactions will
resume once its back online. We are currently waiting for the developers
of the coin to get back to us with updates.
Thank you kindly for your patience and understanding.
Have a great day!
resume once its back online. We are currently waiting for the developers
of the coin to get back to us with updates.
Thank you kindly for your patience and understanding.
Have a great day!
May 12, 2014, 06:27:58 AM
how to turn off the sound on dmdpool.digsys.bg?
+1
it beeps at every block found, which is annoying :-)
May 12, 2014, 06:08:52 AM
Add:
With all the previous talk about "hacking" things to adapt Diamond that created the impression that Diamond was deviating from the common standard, it's important to know that Diamond is not deviating from the original algo, at least in this case anyway. IMHO, these things need to be prominently reported in periodic status reports.
"hacking" is how we creative types refer to the process of investigating something that is not behaving properly and guiding it to behave. This is applicable to any thing in life, not just software. At least, this is how I understand this English language word.
What you propose is good practice. However, it is very difficult to implement in forum formats like this. Here is a place for collaboration, more or less.
May 12, 2014, 05:38:29 AM
POS started ?
May 12, 2014, 05:05:28 AM
Hi pool operators using NOMP!
What is your diamond.json? Something like this?
Thanks!
What is your diamond.json? Something like this?
Code:
{
"name": "Diamondcoin",
"symbol": "DMD",
"algorithm": "groestl",
"txMessages": true
}Thanks!
Oh, I forgot this bit of the instructions. Must have (as usual) assumed it was obvious.
Thing is, GroestlCoin is actually deviating from the common standard, in that it (and few other new coins) is not using sha256d for the transaction hashes, but sha256 (single pass). To accomodate GroestlCoin, NOMP and sph-sgminer actually threat it as special case. In summary, it was never the new DMD wallet's fault that stratum mining did not work -- it was how that software assumed that when you said you want "groestl" you also said you want sha256 (single).
NOMP already has a setting to fix this, thanks to some discussion with the author. For coins that use any of (currently) keccak, blake, fugue and groestl -- you need to specify
Code:
"normalHashing": true,
in the coin definition.
By the way, the morale of this story is that the DMD team has been blamed without guilt on this subject.
Thank you!!! Now it works for my pool as well.
http://groestlcoin.biz/
1% fee
auto payouts from 0.1 DMD
May 12, 2014, 04:59:09 AM
Thing is, GroestlCoin is actually deviating from the common standard, in that it (and few other new coins) is not using sha256d for the transaction hashes, but sha256 (single pass). To accomodate GroestlCoin, NOMP and sph-sgminer actually threat it as special case. In summary, it was never the new DMD wallet's fault that stratum mining did not work -- it was how that software assumed that when you said you want "groestl" you also said you want sha256 (single).
NOMP already has a setting to fix this, thanks to some discussion with the author. For coins that use any of (currently) keccak, blake, fugue and groestl -- you need to specify
Code:
"normalHashing": true,
in the coin definition.
By the way, the morale of this story is that the DMD team has been blamed without guilt on this subject.
This is what I'm harping on. This is another "now you tell us" example that comes to us in the form of a BTW, and that should have been released in headline format all by itself. Of course, if you're not releasing all pertinent data in a timely and transparent fashion, it's a little difficult to do that.
This is all open source after all, correct? And anybody who really wants to know can always dive into the code, correct?
Again, I'm scratching my head and wondering out loud about the lack of specific data regarding all the issues DMD has been facing (both here and on github, and dmdcoin.net too).
I'm befuddled.
Add:
With all the previous talk about "hacking" things to adapt Diamond that created the impression that Diamond was deviating from the common standard, it's important to know that Diamond is not deviating from the original algo, at least in this case anyway. IMHO, these things need to be prominently reported in periodic status reports.
May 12, 2014, 04:43:06 AM
Hi pool operators using NOMP!
What is your diamond.json? Something like this?
Thanks!
What is your diamond.json? Something like this?
Code:
{
"name": "Diamondcoin",
"symbol": "DMD",
"algorithm": "groestl",
"txMessages": true
}Thanks!
Oh, I forgot this bit of the instructions. Must have (as usual) assumed it was obvious.
Thing is, GroestlCoin is actually deviating from the common standard, in that it (and few other new coins) is not using sha256d for the transaction hashes, but sha256 (single pass). To accomodate GroestlCoin, NOMP and sph-sgminer actually threat it as special case. In summary, it was never the new DMD wallet's fault that stratum mining did not work -- it was how that software assumed that when you said you want "groestl" you also said you want sha256 (single).
NOMP already has a setting to fix this, thanks to some discussion with the author. For coins that use any of (currently) keccak, blake, fugue and groestl -- you need to specify
Code:
"normalHashing": true,
in the coin definition.
By the way, the morale of this story is that the DMD team has been blamed without guilt on this subject.
May 12, 2014, 04:19:17 AM
|
May 12, 2014, 04:16:51 AM
A pre-compiled Ubuntu 14.4 binary of sph-sgminer is available for download here http://dmdpool.digsys.bg/download/sph-sgminer-ubuntu.zip Please note that it may have dependencies for few libraries, that are not installed on your system. Just add them with apt-get install. Until it runs  The miner should be used with the '-k diamond' switch, to select the proper kernel for Diamond v2.0. Happy mining. Hey danbi. Not a big thing but maybe you could reset the pool stats to the time of the fork? Block finding stats are waaaay off... May 12, 2014, 03:42:44 AM
Hi pool operators using NOMP!
What is your diamond.json? Something like this? Code: {Thanks! Jump to:
|
