[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 817.

Jarski

newbie

Activity: 16

Merit: 0

Quote from: srcxxx on May 13, 2014, 05:14:15 AM

Quote from: Jarski on May 13, 2014, 04:42:22 AM

I compiled windows sgminer from the source. Tested and works with stratum with diamond kernel!
Enjoy!] Wink

https://mega.co.nz/#!bEVQFYCQ!99KjGDsNMWpXKqlfWdaWQxaRto-XxE-jj9liEs9ojTM

Any DMD tips can be sent here: daVzPCTzZFytFGmjHERfzXiEpQYevnwxpq Grin

Doesn't work for me. Says "waiting for work to be available from pools" for some time and then that no pools can connect. Tried 3 times. Pool URL is correct, internet works ok. Perhaps missing some library/dll ?

Thanks

It only works on danbi's pool I think: http://dmdpool.digsys.bg/index.php
I am currently mining there with stratum. Remember to use stratum port 3333 instead of 3345.

djm34

legendary

Activity: 1400

Merit: 1050

For people interested, you can find also a modified version of ccminer (nvidia card) working with DMD stratum.
https://bitcointalksearch.org/topic/m.6695779

The modification is similar to the one applied to the sgminer.

btw: Can we know which pool are working or not ?
What about Dwarfpool ? may-be Atrides should be recontacted so he can implement the mod to his pool

srcxxx

sr. member

Activity: 266

Merit: 250

Quote from: cryptonit on May 13, 2014, 03:47:17 AM

Quote from: pallas on May 13, 2014, 03:43:54 AM

could you point me to the related change in the commits?
many thanks!

these answer i have to leave for danbi
i dont work with code

Hi!

Is there an updated daemon for unix?

I've been troubleshooting why my pool doesn't work and here's what I see:

Quote

2014-05-12 12:16:50 [Pool] [diamondcoin] (Thread 1) rpc error with daemon instance 0 when submitting block with submitblock {"code":-2,"message":"Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."}

Thanks!

Update: recompiled version 2.0.1 from source. Hopefully, it'll fix all problems.

srcxxx

sr. member

Activity: 266

Merit: 250

Quote from: Jarski on May 13, 2014, 04:42:22 AM

I compiled windows sgminer from the source. Tested and works with stratum with diamond kernel!
Enjoy!] Wink

https://mega.co.nz/#!bEVQFYCQ!99KjGDsNMWpXKqlfWdaWQxaRto-XxE-jj9liEs9ojTM

Any DMD tips can be sent here: daVzPCTzZFytFGmjHERfzXiEpQYevnwxpq Grin

Doesn't work for me. Says "waiting for work to be available from pools" for some time and then that no pools can connect. Tried 3 times. Pool URL is correct, internet works ok. Perhaps missing some library/dll ?

Thanks

Jarski

newbie

Activity: 16

Merit: 0

I compiled windows sgminer from the source. Tested and works with stratum with diamond kernel!
Enjoy!] Wink

https://mega.co.nz/#!bEVQFYCQ!99KjGDsNMWpXKqlfWdaWQxaRto-XxE-jj9liEs9ojTM

Any DMD tips can be sent here: daVzPCTzZFytFGmjHERfzXiEpQYevnwxpq Grin

Change your sgminer.conf

"kernel" : "groelstcoin"
to
"kernel" : "diamond"

If share difficulty too high (16) add:
"difficulty-multiplier" : "0.00390625"

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

thanks danbi, srcxxx and cryptonit for the information, very helpful! :-)

danbi

sr. member

Activity: 393

Merit: 250

Quote from: srcxxx on May 13, 2014, 03:56:58 AM

Quote from: cryptonit on May 13, 2014, 03:47:17 AM

Quote from: pallas on May 13, 2014, 03:43:54 AM

could you point me to the related change in the commits?
many thanks!

these answer i have to leave for danbi
i dont work with code

This is the most important code:

Quote

   if (gpus[0].kernel == KL_FUGUECOIN || gpus[0].kernel == KL_GROESTLCOIN || gpus[0].kernel == KL_TWECOIN)
      sha256(pool->coinbase, pool->swork.cb_len, merkle_root);
   else
      gen_hash(pool->coinbase, merkle_root, pool->swork.cb_len);

As you can see, Groestlcoin will go into sha256(), while Diamondcoin will go into gen_hash()

Correct. It took me a lot of time to realize the solution is *that* simple, but I eventually went for adding the full support for a new kernel, 'diamond'. The reason is that at some future time GroestlCoin might change something and we will end up with non functional miner by depending on their algorithm/special case.
I also skimmed by not cloning the groestl function processing as well, but will likely do it at later date (add diamond specific hasing functions), so again, if GroestlCoin spec is changed, we don't suffer.

Since all these changes are rather trivial, I would expect other mining software to adapt. I modified only this miner, because it's what I use. If theer is interest, I can look at the code of other miners as well. Just don't ask me to compile on Windows!

srcxxx

sr. member

Activity: 266

Merit: 250

Quote from: cryptonit on May 13, 2014, 03:47:17 AM

Quote from: pallas on May 13, 2014, 03:43:54 AM

could you point me to the related change in the commits?
many thanks!

these answer i have to leave for danbi
i dont work with code

This is the most important code:

Quote

   if (gpus[0].kernel == KL_FUGUECOIN || gpus[0].kernel == KL_GROESTLCOIN || gpus[0].kernel == KL_TWECOIN)
      sha256(pool->coinbase, pool->swork.cb_len, merkle_root);
   else
      gen_hash(pool->coinbase, merkle_root, pool->swork.cb_len);

As you can see, Groestlcoin will go into sha256(), while Diamondcoin will go into gen_hash()

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: pallas on May 13, 2014, 03:43:54 AM

could you point me to the related change in the commits?
many thanks!

these answer i have to leave for danbi
i dont work with code

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: Cryptoinn on May 13, 2014, 03:40:24 AM

i have a problem, sended some dmd from pool http://dmdpool.digsys.bg/
tx info should be here http://www.diamondblocks.info/tx/09765220f7200c0f6a15be7f6bc1d969a2723302e3311d43a341bd233eacc1d4
but looks like it offline.
after 2 hours, coins still didn't come to cryptsy

whats happened? Huh

http://dmdchain.cyber.si/ is the block explorer as stated on first page of this ANN thread
website is going through a relaunch info's there not up to date

for cryptsy deposit and withdrawal troubles please get in touch with their support
it seems they still didn't finish their wallet upgrade

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: cryptonit on May 13, 2014, 03:41:07 AM

Quote from: pallas on May 13, 2014, 03:24:33 AM

I had a look here:

https://github.com/danbi/sph-sgminer/commit/a9cd797df5d7917d4de7ab06727b695b0b20a3d1

It seems there is no difference between diamond and groestlcoin, what am I missing?

groestlcoin did choose using regarding transactions sha256 instead of sha256d which most coins uses
diamond did stay on the established standard of sha256d

at solomining this doesnt matter because transactions are handled inside wallet

at stratum mining block have to be prepared by miner + stratum the right way to be accepted by the wallet

could you point me to the related change in the commits?
many thanks!

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: pallas on May 13, 2014, 03:24:33 AM

I had a look here:

https://github.com/danbi/sph-sgminer/commit/a9cd797df5d7917d4de7ab06727b695b0b20a3d1

It seems there is no difference between diamond and groestlcoin, what am I missing?

groestlcoin did choose using regarding transactions sha256 instead of sha256d which most coins uses
diamond did stay on the established standard of sha256d

at solomining this doesnt matter because transactions are handled inside wallet

at stratum mining block have to be prepared by miner + stratum the right way to be accepted by the wallet

Cryptoinn

full member

Activity: 190

Merit: 100

i have a problem, sended some dmd from pool http://dmdpool.digsys.bg/
tx info should be here http://www.diamondblocks.info/tx/09765220f7200c0f6a15be7f6bc1d969a2723302e3311d43a341bd233eacc1d4
but looks like it offline.
after 2 hours, coins still didnt come to crypsy

whats happened? Huh

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

I had a look here:

https://github.com/danbi/sph-sgminer/commit/a9cd797df5d7917d4de7ab06727b695b0b20a3d1

It seems there is no difference between diamond and groestlcoin, what am I missing?

srcxxx

sr. member

Activity: 266

Merit: 250

Quote from: danbi on May 13, 2014, 02:12:57 AM

Quote from: srcxxx on May 12, 2014, 10:37:23 PM

Hi Danbi!

Thanks so much for this info. I added this parameter and now pool is accepting blocks. However with almost 20 hours of 20mhs I could not find any blocks yet.

Do I need to do anything else? Perhaps disable POS in the wallet?

PoS is irrelevant in this case. I disable it on the pool wallet, because it fills up the log file and also there is a risk to remain with negative balance when it stakes. Not good for pools.

I will do a clean diff with the current NOMP and my installation to see if there is any difference, but I don't believe there is -- after finding out what the "problem" is, I just cloned it from github again.

Actually, thanks for pointing out regarding growing the filesize...

Because last time my server crashed because the ~/.Diamond folder was 17GB. Only today it became 2GB.

How do you disable POS?

Also, which daemon are you using? The binary that was posted here a few days ago?

Many thanks for your help!!!

PS: this is what I got just now:

Code:

> diamondd getinfo
error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error

danbi

sr. member

Activity: 393

Merit: 250

Quote from: DarkAGeS on May 12, 2014, 10:43:17 PM

Quote from: danbi on May 12, 2014, 03:42:55 PM

There are two options. Either you create one worker and have all your miners use it, or you create separate workers for each rig.

If you use the pushpool interface, it does not really matter. pushpool does not have vardiff and is more or less identical to solo mining. Multiple workers help only see which one is not working.

If you use stratum, you should use different workers, at least for groups of similarly sized rigs. This is because our stratum has vardiff and will adjust difficulty based on the speed with which you submit shares.

how to use pushpool interface? what is that? looks like this is what I'm looking for.
Is it normal if all my workers will use same login?

To use the pushpool interface, specify -o http://dmdpool.digsys.bg:3345 for the miner.

danbi

sr. member

Activity: 393

Merit: 250

Quote from: srcxxx on May 12, 2014, 10:37:23 PM

Hi Danbi!

Thanks so much for this info. I added this parameter and now pool is accepting blocks. However with almost 20 hours of 20mhs I could not find any blocks yet.

Do I need to do anything else? Perhaps disable POS in the wallet?

PoS is irrelevant in this case. I disable it on the pool wallet, because it fills up the log file and also there is a risk to remain with negative balance when it stakes. Not good for pools.

I will do a clean diff with the current NOMP and my installation to see if there is any difference, but I don't believe there is -- after finding out what the "problem" is, I just cloned it from github again.

nrg_wolf

legendary

Activity: 882

Merit: 1000

is crypsty working fine for this coin?

and why does the Groestl cpu miner not work, can anyone shed some light on this?

DarkAGeS

full member

Activity: 219

Merit: 100

Quote from: danbi on May 12, 2014, 03:42:55 PM

There are two options. Either you create one worker and have all your miners use it, or you create separate workers for each rig.

If you use the pushpool interface, it does not really matter. pushpool does not have vardiff and is more or less identical to solo mining. Multiple workers help only see which one is not working.

If you use stratum, you should use different workers, at least for groups of similarly sized rigs. This is because our stratum has vardiff and will adjust difficulty based on the speed with which you submit shares.

how to use pushpool interface? what is that? looks like this is what I'm looking for.
Is it normal if all my workers will use same login?

srcxxx

sr. member

Activity: 266

Merit: 250

Hi Danbi!

Thanks so much for this info. I added this parameter and now pool is accepting blocks. However with almost 20 hours of 20mhs I could not find any blocks yet.

Do I need to do anything else? Perhaps disable POS in the wallet?

The miner is correct, it gets accepted shares on your pool and I have latest NOMP from github.

Thanks in advance!
srcxxx

Quote from: danbi on May 12, 2014, 04:43:06 AM

Quote from: srcxxx on May 12, 2014, 03:42:44 AM

Hi pool operators using NOMP!

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.

Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 817. (Read 1260636 times)