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

[SaintFrantic]

That's the merchant you want to bring on board. http://www.bluenile.com/

[1713583334]

1713583334

[1713583334]

1713583334

[1713583334]

1713583334

[1713583334]

1713583334

[danbi]

So what seems to be the issue with the pool? I mean, the NOMP stratum works out of the box with grostl algorithms without issue. What seems to be the problem with the pool? From what im reading the wallet is not accepting blocks? Can someone shed some light on this?

There are several things, that pool software needs to adapt to. From my research so far, here is what it takes:

1. You obviously need an stratum server that properly supports groestl.

2. You need to take into account, that current DMD wallet *does not support tx messages*. Team, please add this to the first posting, as this is important difference.

3. You need to modify stratum server to pay to the dev address for each found block 0.05 DMD (this is 5% if your software expects percents). You also need to make sure that bout is the second one, because this is hard coded in the wallet code.

4. You need to figure out why the wallet refuses to accept the MerkleRoot of any shares you throw there... I am struck here, mostly for lack of enough time to research the issue.

Someone must know the answer, so please guys, speak up!

[SaintFrantic]

Is there any working exchange? Where you can deposit DMDs?  

[cryptonit]

Is there any working exchange? Where you can deposit DMDs?  

send a cryptsy support ticket it seems they need some pressure.....

[kammando]

Is there any working exchange? Where you can deposit DMDs?  

send a cryptsy support ticket it seems they need some pressure.....

I just sent cryptsy a support ticket in hopes they hurry up and get things up and running for DMD.

[SaintFrantic]

Is there any working exchange? Where you can deposit DMDs?  

send a cryptsy support ticket it seems they need some pressure.....

I already did. They've said their team is working on it. They weren't very sure when will exactly happen.

[Caniggia]

Hopefully they implement a proper coin and not another clone. 

[casacup]

Hi, I would like to withdrawn my DMD from cryptsy.

Will everything be ok if I use the new wallet?
And if I want to send the fund back to the exchange, will it be possible?

[SaintFrantic]

Hi, I would like to withdrawn my DMD from cryptsy.

Will everything be ok if I use the new wallet?
And if I want to send the fund back to the exchange, will it be possible?

I did withdrew my coins after the update and it was alright but now no deposit is possible. They work on it.

[casacup]

Is the problem related to the dmd wallet or is it cryptsy that hasn't updated it yet?

[cryptonit]

Is the problem related to the dmd wallet or is it cryptsy that hasn't updated it yet?

dmd wallet is able handle transactions without problems
yes we have problems with pool mining now and we work on that

but that have no impact on all wallet abilities that are used by a exchange

so

or is it cryptsy that hasn't updated it yet

this........

[casacup]

Is the problem related to the dmd wallet or is it cryptsy that hasn't updated it yet?

dmd wallet is able handle transactions without problems
yes we have problems with pool mining now and we work on that

but that have no impact on all wallet abilities that are used by a exchange

so

or is it cryptsy that hasn't updated it yet

this........

Yeah I tought it was that, thank you

[2tights]

Has something changed on the network?

[popshot]

Hello Community,

I want to update everyone on the progress of things and I'm honest as always just like each team member of Diamond Coin.

I don't want it to be another apologetic message but a frank assessment. 

As everyone knows the Block Chain went down last Wednesday (for us it was). As we were working on a new client client for quite some time we thought it would make more sense to release it then and there rather to use hardfork fix on the old wallet and do another hardfork soon after to switch it to Groestl algorithm.

The whole sudden situation caught us with our pants down, but we were convinced everything would work, because it worked in the lab, unfortunately as it turned out soon after it failed in the field.

Some people here accused us of not doing enough testing and, yes we didn't do enough because of the crazy short time frame we had to stick to to deliver a working client for Cryptsy. It was ready by Friday, unfortunately the problem with the database forced us to concentrate on making a patch. After that it turned out that mining pools on stratum do not accept blocks. We had a bit of lax day on Sunday just to have a bit of breathing space as most of us have slept for 4-2h per night over the previous several days. On Monday after talking directly with the pool owners we switched our focus to the code and started analysing its behaviour. We have identified possible sources of problems and now we are rebuilding the code to make it work as it was intended to work form the start. We have our own stratum server and can test any changes confirming it plays nicely so we could be 100% sure we wouldn't see any unpleasant surprises next time.

We have made some changes in the dev team setup which is more optimal and allows for better quality testing. We all agreed that this release in no way meets our quality expectations and to overcome this we decided that we won't limit ourselves with fixed deadlines - we will deliver product that is 100% working with stratum and everything else. 

The network is stable now, solo mining is working correctly, coins are transferable, I suspect there would be no problem with setting up working non-stratum 'getwork' mining pool (for the time being), Cryptsy is notified and should be working on implementing the new wallet this week.

I sincerely believe that you as community should not be worried at all, but trust us to put it right. We are working really hard and we won't stop until it's properly done.

Regards,
Alex

[cryptonit]

The speech to end all speeches;
following the year to end all years;
following the battle to end all battles.

[HR]

Phenomenal Network Hashrate in Diamond Happening?

Okay, if we correlate previous mining difficulty with previous network hashrate by taking the April 20 low in difficulty of 0.9, the April 22 high of 3.6, the April 23 high of 4.8, the April 24 low of 3.2, the April 26 high of 5.5, and the April 27 spike high of 9.9 and correlating those dates and values to the hashrate values of the same dates, that is to say, with the April 20 low of 61.5 MH/s, the April 22 high of 225 MH/s, the April 23 high of 327.2 MH/s, the April 24 low of 206.2 MH/s, the April 26 high of 375.7 MH/s, and the April 27 spike high of 735.2 MH/s, we can calculate an average ratio of hashrate to difficulty. Data Source: CoinWarz

61.5 MH/s to 0.9 = 68.33 : 1
225 MH/s to 3.6 = 62.5 : 1
327.2 MH/s to 4.8 = 68.17 : 1
206.2 MH/s to 3.2 = 64.38 : 1
375.7 MH/s to 5.5 = 68.31 : 1
735.2 MH/s to 9.9 = 74.27 : 1

With an average ratio of network hashrate to difficulty from our sampling being 67.49 : 1, and using a low-ball guesstimate of average current difficulty of 35, could we then safely estimate a current hashrate of approximately 2.36 GH/s in old scrypt equivalent terms and 20.86 GH/s in new Groestl algo hashrate terms?

That would mean that we've got one hell of a network hashrate happening! (if my assumptions are correct)

And that, of course, would mean there's a hell of a lot of interest in mining Diamonds!!!

Extremely positive for Diamond if you ask me.  



BTW, many thanks for the contributions, even if they're mainly symbolic and not going to make me rich.
It's the “psychic income” that comes from knowing you felt it important enough to take the time that is greatly appreciated. You know what they say, it's the thought that counts!

[2tights]

Phenomenal Network Hashrate in Diamond Happening?

Okay, if we correlate previous mining difficulty with previous network hashrate by taking the April 20 low in difficulty of 0.9, the April 22 high of 3.6, the April 23 high of 4.8, the April 24 low of 3.2, the April 26 high of 5.5, and the April 27 spike high of 9.9 and correlating those dates and values to the hashrate values of the same dates, that is to say, with the April 20 low of 61.5 MH/s, the April 22 high of 225 MH/s, the April 23 high of 327.2 MH/s, the April 24 low of 206.2 MH/s, the April 26 high of 375.7 MH/s, and the April 27 spike high of 735.2 MH/s, we can calculate an average ratio of hashrate to difficulty. Data Source: CoinWarz

61.5 MH/s to 0.9 = 68.33 : 1
225 MH/s to 3.6 = 62.5 : 1
327.2 MH/s to 4.8 = 68.17 : 1
206.2 MH/s to 3.2 = 64.38 : 1
375.7 MH/s to 5.5 = 68.31 : 1
735.2 MH/s to 9.9 = 74.27 : 1

With an average ratio of network hashrate to difficulty from our sampling being 67.49 : 1, and using a low-ball guesstimate of average current difficulty of 35, could we then safely estimate a current hashrate of approximately 2.36 GH/s in old scrypt equivalent terms and 20.86 GH/s in new Groestl algo hashrate terms?

That would mean that we've got one hell of a network hashrate happening! (if my assumptions are correct)

And that, of course, would mean there's a hell of a lot of interest in mining Diamonds!!!

Extremely positive for Diamond if you ask me.  



BTW, many thanks for the contributions, even if they're mainly symbolic and not going to make me rich.
It's the “psychic income” that comes from knowing you felt it important enough to take the time that is greatly appreciated. You know what they say, it's the thought that counts!

I assumed as much just watching the diff fluctuate so acutely.

I'm not mining very many DMD now that the diff is jumping pretty high. I've gone two consecutive 12 hour stretches before a block was solved.

[cryptonit]

diff 48 - 3,505.43 MH/s Gröstl networkhashrate  - around 350 MH/s scrypt hashingpower

based on http://dmdpool.digsys.bg/ nethash calculation

still a good value like 4 time the (scrypt equvivalent) hasrate than pre relaunch (and without pools)



another indicator

getmininginfo

{
"blocks" : 392415,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 35.09868325,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2390291173,
"pooledtx" : 0,
"testnet" : false
}

35 - diff 2390.291173MH/s - around 230  MH/s scrypt hashingpower

@HR dont wana invest time to analyze your numbers just state my nethash expectations which seem to be far away from yours

[ahmed_bodi]

Hello Community,

I want to update everyone on the progress of things and I'm honest as always just like each team member of Diamond Coin.

I don't want it to be another apologetic message but a frank assessment. 

As everyone knows the Block Chain went down last Wednesday (for us it was). As we were working on a new client client for quite some time we thought it would make more sense to release it then and there rather to use hardfork fix on the old wallet and do another hardfork soon after to switch it to Groestl algorithm.

The whole sudden situation caught us with our pants down, but we were convinced everything would work, because it worked in the lab, unfortunately as it turned out soon after it failed in the field.

Some people here accused us of not doing enough testing and, yes we didn't do enough because of the crazy short time frame we had to stick to to deliver a working client for Cryptsy. It was ready by Friday, unfortunately the problem with the database forced us to concentrate on making a patch. After that it turned out that mining pools on stratum do not accept blocks. We had a bit of lax day on Sunday just to have a bit of breathing space as most of us have slept for 4-2h per night over the previous several days. On Monday after talking directly with the pool owners we switched our focus to the code and started analysing its behaviour. We have identified possible sources of problems and now we are rebuilding the code to make it work as it was intended to work form the start. We have our own stratum server and can test any changes confirming it plays nicely so we could be 100% sure we wouldn't see any unpleasant surprises next time.

We have made some changes in the dev team setup which is more optimal and allows for better quality testing. We all agreed that this release in no way meets our quality expectations and to overcome this we decided that we won't limit ourselves with fixed deadlines - we will deliver product that is 100% working with stratum and everything else. 

The network is stable now, solo mining is working correctly, coins are transferable, I suspect there would be no problem with setting up working non-stratum 'getwork' mining pool (for the time being), Cryptsy is notified and should be working on implementing the new wallet this week.

I sincerely believe that you as community should not be worried at all, but trust us to put it right. We are working really hard and we won't stop until it's properly done.

Regards,
Alex

the main issue is getwork pools are not ideal due to the protocol. They are major resource hogs.

[2tights]

soloming, just now

"pool 0 not providing work fast enough"