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

Hi
When reappear information about Diamond Online http://www.coinwarz.com ?

Yes it's been working fine for days at danbi pool.
With same configuration, your pool doesn't work.

EDIT: found the problem: your pool doesn't want:

--difficulty-multiplier 0.0039062500

While the others do. Please fix it otherwise I can't use it because I would loose failover capability, thanks.

Please be sure you are using the correct miner.

99% rejects, share above target or job not found.

Heh I was able to get it working just fine with test net as my mining rigs are down and had to mine with CPU... looks to be an issue with MPOS tho no recording shit.
Well I'll hold off on "odd" algo pools untill I get my front end up n running...

Diamondcoin @ Nonce-Pool

http://dmd.nonce-pool.com

I believe it doesn't work. I found a block but it doesn't show. Also the hashrate is much lower than real.

And for those of us with an aversion to mega.co.nz downloading 50 megs of encrypted files to our browser as trade off for downloading something from their website, what is the non-mega link please?

Another Pool up and running @ http://dmd.cryptorian.us/ 1% fee

Is a 5% block finder bonus for those who find blocks (extra 0.05 dmd for each block u find on pool)

Tested with danbi's modified sph miner download links and instructions can be found on the "gettingstarted" page


This is stratum only pool!! Must use miners that are linked via getting started page!

Any news?

This is a bad or good, I'll try it, I hope there are more applications DMD

thx for feedback  i didnt know that
so i will use coin-age from now on to represent the age of the coins  
even it have a special meaning and is amined at the unspend coin-age


no its not the time since the coin was mined

coin-age is the unspend age the coin gathered in your wallet
each time a coin is part of a transaction or u minting pos rewards with this coin it spend all his coin-age

your coin-age must be above 30 days before u able to claim any POS rewards in minting mode

I like your wording.

It is also true, that the pool wallet contains some very old coins. The way the wallet software works, it always tries to send out recent coins so if you had some miners not take their coins when the pool started, those "old" coins remain.

In theory, this could be used bythe pool to generate PoS profit. Doing this is a bit tricky, as the pool needs to have enough liquidity or it will stop paying out. But this is resolvable in a number of ways.

What is more interesting, is pools could also function as banks, giving interest to those miners who do not withdraw their coins. Very much in how (sometimes) mining associations worked in the wild, wild west (but guns often changed the outcome)
Thing is, no software exists yet to handle this functionality and as most miners are interested in quick ROI, there is no incentive to develop it.

Fine, whatever. For all us dummies, can you say "after 30 days in your wallet" instead of "30 days coinage" ?

I'm pretty sure quite a lot of coins stay on a mining pool side for long periods of time. I would say the best explanation for the start of gathering coin age is the moment when they reach your personal wallet that you fully control.

Thanks for the clarification danbi but how many miners read source code for fun   99% of the time even pool miners coins hit their wallets the same day they are mined so "30 days from mining" is probably close enough!

This is how the source code refers to this value.

It is also not the time when the coin was mined, but the time the coin came to your wallet. To be even more precise, it is the time of the block that carried the output transaction with your public key (DMD address) in it.

I do agree coinage is a bit confusing at first. But English is easily melting in the mouths of non-Native speakers 

Thanks for the reply cryptonit.  Looking forward to the new update.  I know English is not your first language but you've done pretty well so far except for the use of the word "coinage" and I think it confuses people.

In English, coinage means the total amount of a coin issued.  For example: "The 1930 Australian Penny had a total coinage of 1500" (a very rare and valuable coin).  You are using it to describe how long since the coins were mined as in coin + age.  English doesn't work like that (yes it is a funny language).  "30 days from the date of mining" is much clearer than "30 days coinage".

The 0.05 DMD has to be sent to the DMD contribution address, which is dZi9hpA5nBC6tSAbPSsiMjb6HeQTprcWHz (check the source for confirmation, define DEV_ADDRESS). No new block that does not carry such transaction is permitted on the network.
This contribution is in addition to the 1 DMD (plus tx fees eventually) that get mined in PoW -- so it is not a "fee" and nobody "loses" anything.

I have implemented that contribution as 5% fee in NOMP. Initially, I though the values there are absolute and put 0.05 in the configuration, but then studying the code realized it is in percents (it always help to read the documentation!). I have had NOMP modified too, because it was not ordering the transactions properly in the block --- but after discussing it with teh author he fixed it, so with current NOMP it is just a configuration parameter.
A proper way to do it is to have yet another "contribution amount" definition in NOMP, which is not a percentage but a fixed amount. Talking with the author to implement this as well.

Sorry I do not mention this all every time, I expected you followed my complaints earlier in the discussion. I should probably make an HOWTO document on installing DMD pool, but I need time...

But, the error above I have never seen. It has nothing to do with being foundation compatible, with the contribution of 0.05 etc. I say this, because it acts on "received block" -- which is not a block your pool generates, but you get it from someone else -- probably they are in a fork, or so. Blocks generated by the pool (stratum) look like this in the log:

05/16/14 08:26:12 ThreadRPCServer method=submitblock
05/16/14 08:26:12 AddToWallet e34aacdf74  new
05/16/14 08:26:12 SetBestChain: new best=000000000282378b33bf363a065970a14b571d7da1af6a4e27dab59354617a1f  height=405570
 trust=34413763517  date=05/16/14 08:25:20
05/16/14 08:26:12 Stake checkpoint: 2d77e16c
05/16/14 08:26:12 ProcessBlock: ACCEPTED

in the past of the coin there was a time with pos 1% active and created a lot below 1DMD blocks
thats the reason why total coins isnt sync to blocknumber.

in fact staking happens already but not successful creating rewards
this will be addressed in next wallet release.

every coin u have in ur wallets gather coin-age each day
with next wallet release u will be able convert that coin-age into POS rewards (=minting)

we have a testnet running where we already runing on a wallets that did run through a few code reviews and code adaptions

for now it looks good but we wont release it until further testing is done

one forced early release did hurt us enough
we have no need to release update wallet early and untested

network as it is now run stable and smooth
mining works pool mining works transactions are fast and secure

next release will polish code in lot areas but mainly focus on POS which is the core mechanism of diamond evolution