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

hi ashfallen0

thx for sharing ur ideas
our goal was never to replicate the success of blackcoin
but to write a own diamond success story

the combination of diamonds features is unique not a copy off
groestl algo endless (30+ years)  hybrid pow/pos with foundation support

and we are world first coin that uses totalcoin to be able trigger the coin stages dynamical depend on the minting behavior of stakeholder
if less people mint and more coin-age be burned at transactions dynamical the high reward POS stage stay active longer
because we not trigger ad a defined block and choose instead a totalcoin ammount as trigger

also our goal to host in the future a chain of merged mining coins to improve network security for them all and increase mining rewards for them all is a rare concept

another goal we aiming for is having a way for asic owners (sha256/scrypt) to mine dmd by make a partnership with a alternative payout multipool

but we understand all points u address here and in lot areas we aim in same direction
just we not gona clone BC wallet but instead will add in the future from all code-compatible wallets the "best off"
and additional  increase value of our wallet and code by find own solutions too

this will be a ongoing process the whole foundation is build around the idea to make sure diamond have ongoing development for years

br

Interesting. I wonder why they don't buy up that will bring the price high.

SIZE BID on craptsy at .00054 - 7337 left from an original order of 7555 -

I know the DMD dev team states that they wished to replicate the successes of Blackcoin by swapping over to groestl and adding PoS to the system; but for the end consumer such as myself we need some form of benchmark for progress. 

-With my BC wallet I can open my wallet for staking only, not unlock the whole thing. 
-With my BC wallet I can see what my stake is vs the network stake is and an expected stake time.
-With BC there is a DEV supplied/supported/configured pool that functioned on standard protocols at launch.
-I also had to edit the Diamond.pro file to get the wallet to compile properly; boost library is specified instead of minimum.
-No Checkpointing system in place.  Had to sync the entire 410k blockchain from scratch.  Should have a checkpoint at the last hardfork.

Don't get me wrong, I've been a DMD miner off and on since I favor low volume currencies for stability in the long run.  I see potential in the dev support channel the way it's designed, and I can see in the market depth that the PoS is having the desired effect.  I just want to see my .05 being used to work out bugs, not reinvent the wheel.   

Correct me if I'm wrong, but the BC wallet is also open-source? 

I didn't solo mine recently dmd (meaning this week), but I never had any problem solo mining it without this parameter.

No, the problem are smart arsed accusations of us not doing the job, which we're clearly doing (behind the scenes). None of the Diamond team members whoever it is now and was in the past got a single Diamond out of it. We've invested a lot of our own money into infrastructure upkeep and other measures that allowed this coin to survive for so long. The amount of time and effort we've already put into it and are intending to put is well worth 5%. For now and foreseeable future we all work not for "skimmed" Diamonds, but because we believe in an idea. Do you (and I'm responding here generally) equally criticise mining pools for applying 2% fees while their work is limited to providing the static service?  

It's the smart arsed comments that are the direct cause of 'whatever' attitude and for sure are not helpful. Cryptonit is doing his best to respond to whatever question he is asked. Bear in mind that we don't always have answers and need to consult one another, so don't expect him to be an expert in every single issue. Be realistic people, we are just humans.

WayForward, what you think is your own opinion, and my opinion is quite contrary to yours, it's cryptonit that makes this coin alive and dumping on him some sort of responsibility for coding problems is just ridiculous in my view.  There are no coding issues at the moment and developmental and testing process goes smoothly as never before.

If you don't appreciate more direct contact with the developers (that you have here) that's fine. We can resort to making announcements only, so the coin can be judged on its own merits.
 

Yes, we know full well and it's a pain. I've just checked, we have 24 pages of unique accounts in our ban list. It's a massive amount, but they still keep coming.

Once the site is ready, we'll sort it out once and for all. Thanks to anyone reporting these things on the forum so we are able to remove the spam promptly reducing the nuisance it may cause.

About what a massive dump you say? Diamon will have only 4.7 million coins, this is a drop in the ocean compared with the Amount in other alt coins.
If developers DMD implement all what they say + coin will add to the Chinese exchanger, maybe in the fall we will see the price of $ 10 per coin.

Now the complexity coin production is not quite adequate to its cost, but still waiting the coming changes.

Is this still profitable to solo mine over a pool?

I think its caused all these coding problems to be honest.     I still watch the thread and the same problems exist.  This cryptonit whatever is killing the coin.  Its not we want a proper written reply but the deflection and smart arsed remarks to genuine questions  is the problem.  Its a cant be bothered attitude.  

They could get all the trust back and more if they left the communication to the forum to a native english speaker - as thats your audience mainly.

Price dropped to half after a massive dump - probably the early miners who had such a low difficulty from the get go after the code change to groetl.

once we move to new website we will also solve that forum spam troubles

Forum website http://dmdcoin.net/forum/index.php/board,1.0.html spammers attack again, hopefully in the new version of the site you will take additional security measures.

A couple of questions:

• is your pool PROP?
• does your pool require a minimum hashrate in order to receive payouts?
• similar to a P2P, does your pool setup progressively reward increasing hashrates?

A couple of potential issues:

• I've been testing and, by my calculations, on one machine I should be getting 1/8 total coins mined (assuming that 1/8 hashrate directly correlates to a 1/8 payout), and I've only seen just over 0.5 coins in a period where your Tab Stats show 8 confirmed coins (just over half the expected payout, with 100% reported efficiency and almost zero rejects on my end) - am I calculating wrong?
• much to my chagrin, another miner with a lesser hashrate hasn't received anything . . . something obviously wrong with that, right?
• is it normal to see oscillating shares in the Worker Stats, with values that actually decrease from time to time?

Best regards and looking forward to hearing back from you.

All I know is that he is answering while you are not, and since it is not clear who the team is, I can only assume who is who. If Danbi is part of DMD team then good for you because at least I can understand what he says in a proper American English or perhaps Oxford English!!

As a "bonus", you should know that the "diamond" and "groestlcoin" kernels work identical on solo mining or pushpool mining. They only differ in stratum (getblocktemplate) mining, as GroestlCoin has deviated from the common dtandard (*) by using sha256 for the transaction hashes instead of sha256d as most other coins do.
This means, that irrespective of how you mine Diamond, you can always use the 'diamond' kernel. It will also work for solo mining GroestlCoin and non-stratum GroestlCoin pools.

(*) Then, today there is no such thing as "standard" in this area, because all blockchains are different and coin devs do pretty much what is in their imagination.

"Issue" Resolved

I said in my original post that the only things I changed in my startup script were from the http address to either stratum+tcp://dmdpool.digsys.bg:3333 or stratum+tcp://groestlcoin.biz:3334 and the username. (username only on groestlcoin.biz, of course)

Another "duh" moment: I also needed to change the kernel to diamond.  

At the moment, high extraction complexity not corresponds to the low price.

Just a thought... The value of DMD is 1/2 what it was 2 weeks ago. Why?  Could it be that the market is not impressed by the non delivered promises of the devs?  Where is the PoS?  Yes, I've heard all about the testnet not quite working out...  Dudes, don't promise things you can't deliver... In fact, don't promise things UNTIL you can deliver.  I'm still mining, got over 600 DMD but even my patience is starting to wear thin.  You aren't the only alt algo out there you know.  In fact ATM just about any other alt algo looks more tempting.

Fingers out guys.  Time to deliver and give the coin a boost. We are all aware that you are taking a 5% skim off every block.  You're getting paid, start earning your money.

@danbi, thanks for the reply. The --difficulty-multiplier 0.0039062500 parameter is part of my standard config (if I remember correctly, it's not possible to solo mine without that parameter, and it's used for Groestlcoin mining as well).

Will do some more testing and more thorough documentation when time allows before PMing you (I'm very busy for the rest of the day . . . maybe later tonight).

In the meantime, perhaps some of your other stratum miners could post config and/or bat file configurations?

Might be the network round trip time. What ping times you see to dmdpool.digsys.bg?
The server is not loaded at all. In fact, it runs a number of other tasks, over a dozen pools and... from time to time I do run an CPU miner just to fill up more the CPU cores
It does have some kind of disk bandwidth bottleneck, primarily because too many things write too many log files, but still far away from loaded. That is being addressed anyway.

Other than that, I still do believe it is my task to identify and resolve issues with the service I started (the Diamond mining pool and permanent node). So, if the server somehow causes you to generate rejects, I am looking for ways to fix it.