[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[jepistons]

Does anyone know of any other Diamond pools I can use as a back up that are good?

http://groestlcoin.biz/ no registration needed just dmd wallet addy

[1714329287]

1714329287

[1714329287]

1714329287

[1714329287]

1714329287

[Coinish]

Does anyone know of any other Diamond pools I can use as a back up that are good?

You can also use a miner that supports stratum.  I've been using one to access Danbi's stratum server instead of the http server.


Here's where I found it:
https://bitcointalk.org/index.php?topic=652849


There is a Windows build available.  Set your miner configuration to point to: stratum+tcp://dmdpool.digsys.bg:3333.  You will need to create a .bat file, or set up a config file.  It has Diamond v2.0 support built in.  You need to make these modifications:

Use the switch "--normal-hashing true" in place of "--difficulty-multiplier 0.00390625".  Use the "groestlcoin" kernel (or re-name it to "diamond"....both work the same).


It's all been working for me without any issues.  

[danbi]

Hello Danbi - There seems to be something wrong with the site again.  I mined all day to come home and find connection errors again.  Is it the same problem?  Please advise.  Pretty much the same error still - HTTP: request failed - etc.

Thanks in advance.

I don't see any problem with the pool. What connect string are you using? I see worker name similar to your name using pushpool and submitting shares. Is it ok now?

It might be some kind of connectivity issue. Could you please record the error next time and post it? Thanks!

[danbi]

Does anyone know of any other Diamond pools I can use as a back up that are good?

You can also use a miner that supports stratum.  I've been using one to access Danbi's stratum server instead of the http server.

On a side note, when pushpool was dead, the pool luck increased -- it is perhaps because pushpool (getwork) cannot get proper feedback in real time from the wallet that a new block was found on the network. Thus more hashrate is wasted than necessary.

It also seems that Chris&Chris added Diamond support to ccminer, so it should be possible to use that with stratum and nVidia hardware as well. Anyone there tested it? (I don't have nVidia hardware myself)

[pokeytex]

Hello Danbi - There seems to be something wrong with the site again.  I mined all day to come home and find connection errors again.  Is it the same problem?  Please advise.  Pretty much the same error still - HTTP: request failed - etc.

Thanks in advance.

I don't see any problem with the pool. What connect string are you using? I see worker name similar to your name using pushpool and submitting shares. Is it ok now?

It might be some kind of connectivity issue. Could you please record the error next time and post it? Thanks!

Good morning Danbi - all seems to be working again now.  I only have Nvidia 750ti's.  I have tried the stratum settings and get nothing but "booo's" when I use stratum.  Pushpool seems to be the only thing working for me.  I will record the error when it happens again.  Thanks.

[pokeytex]

Does anyone know of any other Diamond pools I can use as a back up that are good?

You can also use a miner that supports stratum.  I've been using one to access Danbi's stratum server instead of the http server.

On a side note, when pushpool was dead, the pool luck increased -- it is perhaps because pushpool (getwork) cannot get proper feedback in real time from the wallet that a new block was found on the network. Thus more hashrate is wasted than necessary.

It also seems that Chris&Chris added Diamond support to ccminer, so it should be possible to use that with stratum and nVidia hardware as well. Anyone there tested it? (I don't have nVidia hardware myself)

I am currently using ccminer 1.2 with support for dmd-gr.   The settings I run are:
ccminer35-50.exe -a dmd-gr -o http://dmdpool.digsys.bg:3345 -u xxx.xxx -p x  --no-stratum --no-longpoll

I will try messing around with the stratum settings.

[polanskiman]

Since admins don't seem very interested in the MAC wallet I compiled, I am posting it here for those who wish to test it. It is working for me on 10.9.2. Should normally work on 10.6, 10.7 and 10.8.

It seems to be synchronizing fine with me.

https://mega.co.nz/#!XAQ3yR4R!PQPUC8ryHXZOHaePjIRFSNb97OpXp8eSgUPAAr71WV4

If you have any pbs, shoot me a PM.

[pokeytex]

Does anyone know of any other Diamond pools I can use as a back up that are good?

You can also use a miner that supports stratum.  I've been using one to access Danbi's stratum server instead of the http server.

On a side note, when pushpool was dead, the pool luck increased -- it is perhaps because pushpool (getwork) cannot get proper feedback in real time from the wallet that a new block was found on the network. Thus more hashrate is wasted than necessary.

It also seems that Chris&Chris added Diamond support to ccminer, so it should be possible to use that with stratum and nVidia hardware as well. Anyone there tested it? (I don't have nVidia hardware myself)

I am currently using ccminer 1.2 with support for dmd-gr.   The settings I run are:
ccminer35-50.exe -a dmd-gr -o http://dmdpool.digsys.bg:3345 -u xxx.xxx -p x  --no-stratum --no-longpoll

I will try messing around with the stratum settings.

Ok - I switched to the stratum server and all seems to be working fine on ccminer 1.2 - I will let you know if anything goes on there but so far so good.  Thank you kindly.

[cryptonit]

Ok - I switched to the stratum server and all seems to be working fine on ccminer 1.2 - I will let you know if anything goes on there but so far so good.  Thank you kindly.

what hashrate u get?
most of all im interested in any gtx750ti groestl algo ratings with newest ccminer

maybe i exchange my 6x amd280 against 6x gtx750ti

to get some spare PSU wattage powering my asics (to be my own multipool with dmd payout )

[danbi]

Since admins don't seem very interested in the MAC wallet I compiled, I am posting it here for those who wish to test it. It is working for me on 10.9.2. Should normally work on 10.6, 10.7 and 10.8.

It seems to be synchronizing fine with me.

https://mega.co.nz/#!XAQ3yR4R!PQPUC8ryHXZOHaePjIRFSNb97OpXp8eSgUPAAr71WV4

If you have any pbs, shoot me a PM.

Your contribution has not been ignored. I spent the last few days modifying the Diamond code to build and run properly on OS X Mavericks. Some of your changes were superfluous (which is understandable, if you are not using an IDE and multi-stage "distillation" of code for publication -- we often leave cruft from experiments that "does not hurt"). With your changes however, Diamond does not build on a clean Maverick + Qt + MacPorts setup. Which is our goal, as the future builders better not carry baggage from past development environments). All this requires a lot more time, but will eventually pay off in better code quality over time.

I have built an OS X Mavericks binary, using such an clean environment and the code fixes are pushed to https://github.com/danbi/Diamond. Once we are happy with it, the official repository will be updated.

Since my binary is built using the "official" methods (of Apple, Qt), I am interested in testers to see if it would run on operating systems pre-Mavericks.
The binary is available at http://ftp://diamond.danbo.bg/pub/diamond-qt-test2.0.2.1.dmg

[pallas]

danbi, will the changes needed to compile on arm be included in the official git?
just wanted to know if they must be included in a "compile on arm" document (or "use the latest source with arm support" instead).

[polanskiman]

Since admins don't seem very interested in the MAC wallet I compiled, I am posting it here for those who wish to test it. It is working for me on 10.9.2. Should normally work on 10.6, 10.7 and 10.8.

It seems to be synchronizing fine with me.

https://mega.co.nz/#!XAQ3yR4R!PQPUC8ryHXZOHaePjIRFSNb97OpXp8eSgUPAAr71WV4

If you have any pbs, shoot me a PM.

Your contribution has not been ignored. I spent the last few days modifying the Diamond code to build and run properly on OS X Mavericks. Some of your changes were superfluous (which is understandable, if you are not using an IDE and multi-stage "distillation" of code for publication -- we often leave cruft from experiments that "does not hurt"). With your changes however, Diamond does not build on a clean Maverick + Qt + MacPorts setup. Which is our goal, as the future builders better not carry baggage from past development environments). All this requires a lot more time, but will eventually pay off in better code quality over time.

I have built an OS X Mavericks binary, using such an clean environment and the code fixes are pushed to https://github.com/danbi/Diamond. Once we are happy with it, the official repository will be updated.

Since my binary is built using the "official" methods (of Apple, Qt), I am interested in testers to see if it would run on operating systems pre-Mavericks.
The binary is available at http://ftp://diamond.danbo.bg/pub/diamond-qt-test2.0.2.1.dmg

That means that the Diamond source code on github is not up to date then?

I simply built the MAC wallet because there was no updated MAC client available yet and since 2.0.2.1 was said to be a compulsory update (if I read well somewhere) I didn't wait for things to happen. I also had a quiet weekend and nothing much to do. I had no pretension of making an art piece. I simply took the official Diamond source code from githug and compiled it while fixing a few warnings during compilation. I posted here saying I had compiled a MAC wallet but had no answer, thus I posted what I had done today.

I will pull down the app as obviously it's not up to standards.

[utahjohn]

My DMD wallet showing block > 450800, is staking now activated? (Wallet is unlocked)

My CRYPTcoin wallet is staking already also it has an icon in lower right quadrant showing that staking active ...

[shveicar]

I am also interested to know. Number of blocks transferred more than 450,000. Pos already activated?

[cryptonit]

I am also interested to know. Number of blocks transferred more than 450,000. Pos already activated?

help
debug window
console

getinfo

read
moneysupply

when that value reach 450000 POS will be activated

21:36:05

getinfo

21:36:05

{
"version" : "v2.0.2.1",,
"stake" : 0.00000000,
"blocks" : 450877,
"moneysupply" : 437370.72036400,

there is a reason why we didnt release wallt and instant start POS
once POS started all user/pool/exchange which didnt upgrade will be in wrong fork

please use the time to update and make sure ur favorite pool updated too and ur favorite exchange....

[utahjohn]

If a block rewards 1.05 DMD and 0.05 goes to devs, how can there be less than # Blocks DMD in circulation

1.05 * 450877 = 473420.85 DMD

A difference of 36050.129636 DMD   Where is it? LOL

[pallas]

The full error message:

diamondd: kernel.cpp:412: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.

Happened again today when I stopped and restarted the wallet daemon.

[danbi]

Since admins don't seem very interested in the MAC wallet I compiled, I am posting it here for those who wish to test it. It is working for me on 10.9.2. Should normally work on 10.6, 10.7 and 10.8.

It seems to be synchronizing fine with me.

https://mega.co.nz/#!XAQ3yR4R!PQPUC8ryHXZOHaePjIRFSNb97OpXp8eSgUPAAr71WV4

If you have any pbs, shoot me a PM.

Your contribution has not been ignored. I spent the last few days modifying the Diamond code to build and run properly on OS X Mavericks. Some of your changes were superfluous (which is understandable, if you are not using an IDE and multi-stage "distillation" of code for publication -- we often leave cruft from experiments that "does not hurt"). With your changes however, Diamond does not build on a clean Maverick + Qt + MacPorts setup. Which is our goal, as the future builders better not carry baggage from past development environments). All this requires a lot more time, but will eventually pay off in better code quality over time.

I have built an OS X Mavericks binary, using such an clean environment and the code fixes are pushed to https://github.com/danbi/Diamond. Once we are happy with it, the official repository will be updated.

Since my binary is built using the "official" methods (of Apple, Qt), I am interested in testers to see if it would run on operating systems pre-Mavericks.
The binary is available at http://ftp://diamond.danbo.bg/pub/diamond-qt-test2.0.2.1.dmg

That means that the Diamond source code on github is not up to date then?

I simply built the MAC wallet because there was no updated MAC client available yet and since 2.0.2.1 was said to be a compulsory update (if I read well somewhere) I didn't wait for things to happen. I also had a quiet weekend and nothing much to do. I had no pretension of making an art piece. I simply took the official Diamond source code from githug and compiled it while fixing a few warnings during compilation. I posted here saying I had compiled a MAC wallet but had no answer, thus I posted what I had done today.

I will pull down the app as obviously it's not up to standards.

The Diamond source code on github is obviously up to date. It is the only official source.

I have no idea if your build has any problems -- most likely it does not. My comment was on the github pull request you submitted -- for example, there are two additional files you created, that are not used anywhere.

Anyway, your compiled application is likely to work on older OS X versions as well. Mine might not run at all on older OS X -- we will know this when it's tested.

Because both are based on the same source, they should both work the same way.

[danbi]

The full error message:

diamondd: kernel.cpp:412: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.

Happened again today when I stopped and restarted the wallet daemon.

This is a known corruption of the block index database, for which we have not yet found a solution. The easiest way to fix it is to load the blocks from the block chain you already have, effectively rebuilding the index. You can do this by removing blkindex.dat first and then running

diamondd -loadblock=blk0001.dat

This will go like downloading the block chain from the network, only much faster and will result in clean block index.
One way to avoid this situation happening is to wait a bit more when stopping the wallet, before starting it again. Unfortunately, there is no indication when it actually stops running.

[cryptonit]

If a block rewards 1.05 DMD and 0.05 goes to devs, how can there be less than # Blocks DMD in circulation

1.05 * 450877 = 473420.85 DMD

A difference of 36050.129636 DMD  Where is it? LOL

a mix of low ammount pos reward blocks and broken pos rewards (0dmd reward) from stone age of coin

long before we took over development

moneysupply is all existing coins

and ur math is wrong in another way too beside forgetting POS blocks in the past
the 0.05 for foundation only in effect from start of groestl mining