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

Hi!

Where can you buy/sell DMD right now?

Is cryptsy now fixed?

Thanks

CryptoCoinsInfo.com

Mining calculation is now working for Diamonds with Groestl algo!

Check the detail page for 24h & 30 days difficulty and price stats. All values are nearly realtime, max. 60 secs delay.

edit: removed and fixed.

Ok well now it looks like it is good to go. Deleted the block and redownloaded from the mega.co link. Seems to be ok now...weird!

I'm stuck downloading the blockchain right now around 386228 block from 7 days ago...any ideas?

danbi's DMD pool - never received a confirmation email. If you'd like me to test on your pool, please unlock my account

I suppose that PPS makes sense if that's available soon it'll be welcomed.

Well, there are two sides to this. Introducing mining pools would indeed centralise mining, adding stratum which uses getblocktemplate makes it more secure for the network. But in essence they do the same job and 90% of miners wouldn't see any difference whether it's stratum or not. 'Getwork' pool is indeed a bandwidth hog but such pool would be a temporary measure until we release stratum compatible client.
Solo mining is a game of luck, you never know when you would come up with the correct hash - the more power you have the higher your chances, however already several people gave up on solo mining because of difficulty being too high for them. Mining pool with PPS for example is a different matter it allows whoever with whatever mining gear to join in and get paid for the amount of shares he contributed. We would definitely see more people mining making the coin available to greater group of people. Big MegaHashers would still keep their share while smaller ones would not waste their electricity in vain waiting for the miracle.

I think it should be a democratic decision and the community should choose which path to take. If there was someone who would set up an oldschool pool we would see how much hash support he would get and how much solo miners ...

its not poolmining against solomining
its asic against everymans hardware

and by move towards groestl we did clear choose a mining type where everyone can take part and not a few big asic owner
groestl is also much more friendly to a broader spectrum of possible mining hardware (amd, nvidia, cpu, and soon even arm based tablets/smartphones)
yes groestl wont be asic resistent forever but our prime mining window is expected to be around 15 months and we think noone will invest into asic development for such a timeframe


everyone can have his own opinion
my opinion isnt better than yours
but my opinion is the basic of the diamond coin specs  

I don't think you can speak for everyone, because I don't want to get out of the solomining. There is a great sense of gratification that comes from accomplishing it on my own.

But I also don't want to be pushed out by pools.  It'll be bitcoin all over in that solomining will die quickly and pools will reign supreme.

Maybe its time to make my own coin which forbids pool mining.

its opposite way around
small miners are cpu or single gpu miner
and this people want to escape the solo mining lotto

i understand we all know pools will increase nethashrate

but main purpose of this mining is spread coins between as many interested people as possible

not that a few people earn a golden nose

the golden nose phase is later when even without mining u can see how ur diamonds increase  

we full agree

just if someone wana create a temporary pool it would be a option
or set up a p2pool
(could ask for higher fees for more bandwith useage)
until we fixed the stratum combatible mining

cpu miner as example or singlegpu miner would sure spend the extra fee to mine on a temporary getwork pool to escape the find block lotto

its not like we earn anything if we give the hint that such a pool could pay off his aditional "resource costs"

why is it such a huge deal for pool mining to get rolling? I thought the change in algo was trying to create a more equitable landscape for individuals looking to be involved.  The only thing that pool mining will ensure is that the hashing power is centralized and small solominers will leave.

soloming, just now

"pool 0 not providing work fast enough"

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

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

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.

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!

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

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