Author

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

legendary
Activity: 1121
Merit: 1003
**Diamond Coin Beta Testing**

Diamond Foundation is now offering beta testing of the new wallet.

We have internally tested the diamond wallet and have would like to test it with multiple users and machines.
We would like to select a few individuals for beta testing. Those interested in joining our beta testing program. Please visit our forum at http://dmdcoin.net/forum/index.php/board,11.0.html and introduce yourself.
Testing goals:
POS staking (minting of coins)
Ensure both transactions and confirmations work perfect.
Monitor Hybrid POW/POS activity
–––
Regards,
Brian
Beta team coordinator
Diamond foundation
ECM
newbie
Activity: 12
Merit: 0
Though the changes have to be made on the diamond kernel file as we cannot longer use the kernel groestcoin.cl for DMD mining. Anyone who knows how to implement the changes? Danbi maybe?

the kernel is the same, you can copy it over.
the changes are in sgminer C code.

Well aint that sweet?! Thanks Pallas!
I first tried to just change the -k switch from '-k diamond' to '-k groestlcoin'. That only gave me a lot of rejects because of low difficulty target. When I now instead tried to rename the kernel to diamond.cl (and changing the name of the regular DMD kernel to something else)...voila, works perfect!
Now running a steady 12.74mhs per Gigabyte 280x card. That is a 65% improvement.

This is the link for SRCXXX modified kernel: https://mega.co.nz/#!9MAAHQJL!cqvdNfIeqcD39AZgvalgcGRKvS5U44xYTtlAZXqUi1U
remove your bin files and restart the miner.

If you got a faster running rig with his kernel, please consider donating:

* donate GRS to Groestlcoin project: FYEAbFBG3xY5VUtE9GXC56v5UKt4xkoUkb
* send BTC to SRCXXX private account: 1NpEXJvoLSG99m3d1vpM7tHx8uXkksf7wL

I just sent a BTC equivalent of 10 DMD. Not much but if everyone that benefits from this improvement did the same...
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Though the changes have to be made on the diamond kernel file as we cannot longer use the kernel groestcoin.cl for DMD mining. Anyone who knows how to implement the changes? Danbi maybe?

the kernel is the same, you can copy it over.
the changes are in sgminer C code.
ECM
newbie
Activity: 12
Merit: 0
WOW! Is every update from AMD going to be like this?! AWESOME!!!

I was doing 7.7MHS with my Gigabyte 280x before (Catalyst 14.2) and by simply uninstalling and installing the new drivers I am doing 12.1MHS. No other changes. That is an amazing increase by 57%!

Ive seen on the GRS forums that ppl were very happy to reach 11.1MHS with same cards. And I did notice that I did something different by accident. When I uninstalled the old drivers I used the AMD removal tool (has worked really good for me) and before installing the new driver I installed the same APP SDK as I had used before, version 2.8. I did notice that some people are using the newer version of that 2.9 although Im no expert to say that is where the trick is. Though as the APP SDK is (as far as I unstand it) the OpenGL drivers, it should benefit from the updated version. And now that Im digging a little I notice that the 2.9 version was released in Nov last year, which is after I started mining, so prob I downloaded the old version from an unofficial source.
I also dont have ADL SDK installed as a poster on GRS forum suggests.

I way to tired to play around with this at this moment. But I have some things to look at to see if I can juice them even more.

Oh, and the cards are at 61 degrees Celsius (one at 69) and I am running a Win 7 64bit machine.

More updates to come!
got lost... what's your point ? should we use the 2.9 version or the 2.8 ?

Sorry for my messy post from last night. I was already waay too tired to sit at the computer.
I did some testing today and I see no change what so ever between using APP SDK 2.8 and 2.9. A good guess is that its included in the Catalyst driver pack so I was using the latest version anyway.


Thanks for the tip srcxxx Smiley

Hi Guys!

Don't know if you are aware or not, but there are two news for all "Groestl" coins:

1) AMD 14.6 beta driver has massive hashrate increase. About 1.5X. R9 290 is now 15MHs, R9 280X is now 11.4MHs.

2) There is an Android miner for Groestl.

(You can check last few pages of Groestlcoin thread if you want details)

srcxxx (Groestlcoin dev)

No problem. Also see here: https://bitcointalksearch.org/topic/ann-sph-sgminer-multi-coin-multi-algorithm-gpu-miner-added-marucoin-475795
(another 8%, now 16.2 MH/s on R9 290)

Improvements are always welcome! I did try your modified kernel and it did give me a 5.4% boost, from 12.08mhs to 12.74mhs (Gigabyte 280x). Though the changes have to be made on the diamond kernel file as we cannot longer use the kernel groestcoin.cl for DMD mining. Anyone who knows how to implement the changes? Danbi maybe?
And, SRCXXX, I will be sending a small donation as soon as my GRS wallet is up and running. (having sync problems because of nodes with old wallets)
sr. member
Activity: 266
Merit: 250
Thanks for the tip srcxxx Smiley

Hi Guys!

Don't know if you are aware or not, but there are two news for all "Groestl" coins:

1) AMD 14.6 beta driver has massive hashrate increase. About 1.5X. R9 290 is now 15MHs, R9 280X is now 11.4MHs.

2) There is an Android miner for Groestl.

(You can check last few pages of Groestlcoin thread if you want details)

srcxxx (Groestlcoin dev)

No problem. Also see here: https://bitcointalksearch.org/topic/ann-sph-sgminer-multi-coin-multi-algorithm-gpu-miner-added-marucoin-475795
(another 8%, now 16.2 MH/s on R9 290)
hero member
Activity: 728
Merit: 500
Activity: yes
Can someone please post instructions on how to upgrade catalyst drivers on Debian? (pimp)
legendary
Activity: 1400
Merit: 1050
WOW! Is every update from AMD going to be like this?! AWESOME!!!

I was doing 7.7MHS with my Gigabyte 280x before (Catalyst 14.2) and by simply uninstalling and installing the new drivers I am doing 12.1MHS. No other changes. That is an amazing increase by 57%!

Ive seen on the GRS forums that ppl were very happy to reach 11.1MHS with same cards. And I did notice that I did something different by accident. When I uninstalled the old drivers I used the AMD removal tool (has worked really good for me) and before installing the new driver I installed the same APP SDK as I had used before, version 2.8. I did notice that some people are using the newer version of that 2.9 although Im no expert to say that is where the trick is. Though as the APP SDK is (as far as I unstand it) the OpenGL drivers, it should benefit from the updated version. And now that Im digging a little I notice that the 2.9 version was released in Nov last year, which is after I started mining, so prob I downloaded the old version from an unofficial source.
I also dont have ADL SDK installed as a poster on GRS forum suggests.

I way to tired to play around with this at this moment. But I have some things to look at to see if I can juice them even more.

Oh, and the cards are at 61 degrees Celsius (one at 69) and I am running a Win 7 64bit machine.

More updates to come!
got lost... what's your point ? should we use the 2.9 version or the 2.8 ?
ECM
newbie
Activity: 12
Merit: 0
WOW! Is every update from AMD going to be like this?! AWESOME!!!

I was doing 7.7MHS with my Gigabyte 280x before (Catalyst 14.2) and by simply uninstalling and installing the new drivers I am doing 12.1MHS. No other changes. That is an amazing increase by 57%!

Ive seen on the GRS forums that ppl were very happy to reach 11.1MHS with same cards. And I did notice that I did something different by accident. When I uninstalled the old drivers I used the AMD removal tool (has worked really good for me) and before installing the new driver I installed the same APP SDK as I had used before, version 2.8. I did notice that some people are using the newer version of that 2.9 although Im no expert to say that is where the trick is. Though as the APP SDK is (as far as I unstand it) the OpenGL drivers, it should benefit from the updated version. And now that Im digging a little I notice that the 2.9 version was released in Nov last year, which is after I started mining, so prob I downloaded the old version from an unofficial source.
I also dont have ADL SDK installed as a poster on GRS forum suggests.

I way to tired to play around with this at this moment. But I have some things to look at to see if I can juice them even more.

Oh, and the cards are at 61 degrees Celsius (one at 69) and I am running a Win 7 64bit machine.

More updates to come!
legendary
Activity: 1532
Merit: 1205
Diamond is in my book called Cryptocurrency "The Alt-ernative".  Here is first draft of IFC:


https://bitcointalksearch.org/topic/m.7131241


Diamond will look similar to this.  Coin specifications, history, exchanges and other miscellaneous details will be included.  Please help fund the publication of this book which I plan to publish this summer.  

dYbJYA5zUqjoLhM5H2Ni2oC6gL8UkRebVT


legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
i can confirm amd catalyst 14.6 did increase amd290 hashrate from ~9mhash to ~14mhash
i suggest every amd based diamond digger to update his driver

tested with this miner
https://mega.co.nz/#!bEVQFYCQ!99KjGDsNMWpXKqlfWdaWQxaRto-XxE-jj9liEs9ojTM

and following settings:
sgminer.exe -k diamond  -o http://dmdpool.digsys.bg:3333 -u cryptonit.1 -p 1 -T --xintensity 300 -g 1 --thread-concurrency 16384 -w 256 --lookup-gap 0 --difficulty-multiplier 0.0039062500
sr. member
Activity: 393
Merit: 250
I am trying to understand how an older wallet, that supposedly does not know about groestl participates in our network. For example, these peers:

    {
        "addr" : "184.105.143.131:34839",
        "services" : "00000001",
        "lastsend" : 1401885504,
        "lastrecv" : 1401885502,
        "conntime" : 1401879187,
        "version" : 60006,
        "subver" : "/Diamond:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 432213,
        "banscore" : 0
    },

    {
        "addr" : "80.216.198.150:52743",
        "services" : "00000001",
        "lastsend" : 1401885501,
        "lastrecv" : 1401885380,
        "conntime" : 1401882533,
        "version" : 60006,
        "subver" : "/Diamond:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 432266,
        "banscore" : 0
    },


They claim to have starting height (at the time the client started) very similar to the current one at the moment 432320

Does anyone run pre v2.0.1 wallet?
hero member
Activity: 774
Merit: 554
CEO Diamond Foundation
Thanks for the tip srcxxx Smiley

Hi Guys!

Don't know if you are aware or not, but there are two news for all "Groestl" coins:

1) AMD 14.6 beta driver has massive hashrate increase. About 1.5X. R9 290 is now 15MHs, R9 280X is now 11.4MHs.

2) There is an Android miner for Groestl.

(You can check last few pages of Groestlcoin thread if you want details)

srcxxx (Groestlcoin dev)
sr. member
Activity: 266
Merit: 250
Hi Guys!

Don't know if you are aware or not, but there are two news for all "Groestl" coins:

1) AMD 14.6 beta driver has massive hashrate increase. About 1.5X. R9 290 is now 15MHs, R9 280X is now 11.4MHs.

2) There is an Android miner for Groestl.

(You can check last few pages of Groestlcoin thread if you want details)

srcxxx (Groestlcoin dev)
sr. member
Activity: 393
Merit: 250
Anyway, if you think you could spend the time required for testing, you could contact me to discuss it.
Tell me what do you need me to do?

We will have an announcement soon.
sr. member
Activity: 280
Merit: 250
What's happening with the POS update is it coming? Any updates on that.

Yes it is coming, as was mentioned before we are in the debugging mode. We are testing all the scenarios and whenever crash happens we find the root cause and fix it. The progress we're making is rapid and we sorted out many underlying paradoxes that existed in the code. This is making Diamond not just another copy coin, but actually an improved version. Proof of Stake works (and stakes), we are testing it on the forked main chain so we are sure it's compatible with the old database (ensuring gathered coin age is preserved).

You have to understand us, that after the latest rush release (which was a flop) we are putting stability as number one priority, all the rest comes later.
Do you need some to beta test it as well. I understand that you need to be sure that there isn't any possible problem but we all know something always happens. Just keep us updated.

I have considered a procedure to do a wider beta test. The main stumbling block is most users willing to test run on Windows and producing Windows binaries is usually very slow (considering the pace of changes). We have more or less identified and fixed the glaring bugs, and are now testing various network parameters. Unfortunately, most of these parameters require a fork, which in testing means we need to update all nodes participating in the test network at the same time, or they create many forks --- this is more or less the challenge we face for a wider test.

Anyway, if you think you could spend the time required for testing, you could contact me to discuss it.
Tell me what do you need me to do?
sr. member
Activity: 393
Merit: 250
What's happening with the POS update is it coming? Any updates on that.

Yes it is coming, as was mentioned before we are in the debugging mode. We are testing all the scenarios and whenever crash happens we find the root cause and fix it. The progress we're making is rapid and we sorted out many underlying paradoxes that existed in the code. This is making Diamond not just another copy coin, but actually an improved version. Proof of Stake works (and stakes), we are testing it on the forked main chain so we are sure it's compatible with the old database (ensuring gathered coin age is preserved).

You have to understand us, that after the latest rush release (which was a flop) we are putting stability as number one priority, all the rest comes later.
Do you need some to beta test it as well. I understand that you need to be sure that there isn't any possible problem but we all know something always happens. Just keep us updated.

I have considered a procedure to do a wider beta test. The main stumbling block is most users willing to test run on Windows and producing Windows binaries is usually very slow (considering the pace of changes). We have more or less identified and fixed the glaring bugs, and are now testing various network parameters. Unfortunately, most of these parameters require a fork, which in testing means we need to update all nodes participating in the test network at the same time, or they create many forks --- this is more or less the challenge we face for a wider test.

Anyway, if you think you could spend the time required for testing, you could contact me to discuss it.
sr. member
Activity: 393
Merit: 250
Of course it's impossible to debug any software 100% especially the one of such complexity. We would be aiming at making it very robust, so we wouldn't have to change anything significant for as long as it is possible.
Client functionality for an 'ordinary' user has been already tested positively; what we concentrate now are things that would affect minority of users (i.e long term serious miners). We can test these on our Foundation wallet with thousands of micro transactions.
The client will be released once we are sure it is ready.
The next step will be definitely contacting Cryptsy and giving them a lot of time to test the software (and this time GitHub will be properly used and appropriately commented so it is transparent to anyone what changes have been made), to avoid any trade freeze. Mining pools and then 'ordinary' users will follow suit.
All of that is going to happen sooner then later.

P.S. I've updated the first post with Download links to Sourceforge for those who cannot use Mega.
Work quietly, the main thing that the update is delayed for months. Coin with the Diamond name should correspond to its name.

It is about one month since Diamond has forked and started using Groestl. The new release is very near.
sr. member
Activity: 393
Merit: 250
Yes I can solo that way, but pool mining doesn't seem to work at all.  In previous posts, there are reports of a "diamond" kernel fixing things.   I believe this is the source, just need a windows binary :/   https://github.com/danbi/sph-sgminer

Unfortunately, the author has abandoned sph-sgminer, this is why he did not integrated my Diamond kernel modifications back. Hopefully, someone will take over that project. There was a post earlier in this thread with link to Windows binary with diamond kernel.

In any case, hope to have soon an "official" build for Windows, too.
legendary
Activity: 1414
Merit: 1013
DMD info: https://diamond-info.github.io/
Of course it's impossible to debug any software 100% especially the one of such complexity. We would be aiming at making it very robust, so we wouldn't have to change anything significant for as long as it is possible.
Client functionality for an 'ordinary' user has been already tested positively; what we concentrate now are things that would affect minority of users (i.e long term serious miners). We can test these on our Foundation wallet with thousands of micro transactions.
The client will be released once we are sure it is ready.
The next step will be definitely contacting Cryptsy and giving them a lot of time to test the software (and this time GitHub will be properly used and appropriately commented so it is transparent to anyone what changes have been made), to avoid any trade freeze. Mining pools and then 'ordinary' users will follow suit.
All of that is going to happen sooner then later.

P.S. I've updated the first post with Download links to Sourceforge for those who cannot use Mega.
Work quietly, the main thing that the update is delayed for months. Coin with the Diamond name should correspond to its name.
legendary
Activity: 3696
Merit: 2219
💲🏎️💨🚓

Goodbye, and best of luck (and I truly mean that).


Can I have your DMD if you're no longer needing them? dRFU4RMoVuNaLegTLDcf3vL6LzvaRnKaYe Many thanks,
Jump to: