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

[Jarski]

Just curious. Has anyone seen any staking yet?  My coins aren't old enough but I'm sure there are plenty of people here with coins over 30 days old that should be seeing something.

Didn't staking start on 400000th block? So it staking should start after 30 days more or less. Latest block was 404242.

[1713927496]

1713927496

[NoxX]

Just curious. Has anyone seen any staking yet?  My coins aren't old enough but I'm sure there are plenty of people here with coins over 30 days old that should be seeing something.

Didn't staking start on 400000th block? So it staking should start after 30 days more or less. Latest block was 404242.

That was my question too, I thought that staking was enabled once we hit 400000, but then for all the older blocks too. Within blocks 1 - 399999 there are many that are older than 30 days, they should stake already...

[johndec2]

Looks like the devs need to clarify the situation?  Is it 30 days after block 400,000 or is it 30 days after minting (pre or post algo change) ?

[Kloks]

Looks like the devs need to clarify the situation?  Is it 30 days after block 400,000 or is it 30 days after minting (pre or post algo change) ?

As I understood from the first post, POS will start when money supply will be more then 400 000 DMD.

Not after 400 000 block.

[djm34]

Looks like the devs need to clarify the situation?  Is it 30 days after block 400,000 or is it 30 days after minting (pre or post algo change) ?

As I understood from the first post, POS will start when money supply will be more then 400 000 DMD.

Not after 400 000 block.

good one  Can you explain the difference ?

[Kloks]

Looks like the devs need to clarify the situation?  Is it 30 days after block 400,000 or is it 30 days after minting (pre or post algo change) ?

As I understood from the first post, POS will start when money supply will be more then 400 000 DMD.

Not after 400 000 block.

good one  Can you explain the difference ?

result of the - getinfo command in the wallet:

.....
"blocks" : 403436,
"moneysupply" : 387564.87036400,
.....

Looks like some blocks cost less then 1 dmd. Maybe it was in the first version of Diamond.

[mig6r]

Hello
I'm trying to mine (dmdpool) with sph sgminer and -k groestlcoin doesn't work.
What is the secret ?

[cryptonit]

Hello
I'm trying to mine (dmdpool) with sph sgminer and -k groestlcoin doesn't work.
What is the secret ?

example for AMD280:

sgminer.exe -k groestlcoin  -o http://dmdpool.digsys.bg:3345 -u cryptonit.2 -p 2   --gpu-engine 1100 --gpu-memclock 1100 --xintensity 300 -g 1 --thread-concurrency 8192 --difficulty-multiplier 0.0039062500 -w 256 --lookup-gap 0

[srcxxx]

It was my 7th attempt to set up a Diamond mining pool.

It failed again.

I ask Diamond devs or danbi for help.

NOMP always says "Daemon instance 0 rejected a supposedly valid block".

I have the latest NOMP source, I have compiled 2.0.1 daemon from your repo myself and even redownloaded the complete blockchain (instead of using your Original.rar).
Nothing helps.

Also, please note that only the single pool is working. No other pools are operating. They have 0 miners.

So I recommend that you look into this issue to avoid some 51% or timewarping attacks on your blockchain.

Thank you

I am rather busy this week with other stuff, and don't visit very often here.

But, as the Diamond team people were repeatedly telling me in this thread while I was combating it, "are your blocks foundation compatible?"

That is, do you send 0.05 DMD to the DMD contribution address with each block?
What are your wallet log files showing? That is, whatever the reason for the reject, it *is* listed there.

I hope to be able to help with more issues soon.

Hi danbi!

Thank you for your help again.

This is what I'm getting in debug.log:

05/15/14 03:54:37 received block 0000000003d0ac2948ef
05/15/14 03:54:37 pindexBest = 388054pindexBest = 388054ERROR: AcceptBlock() : rejected by synchronized checkpoint
05/15/14 03:54:37 ERROR: ProcessBlock() : AcceptBlock FAILED

Also, what's the deal with 0.05 DMD? How do I do that?
Add a 0.5% fee in nomp pool config? If yes, what's the address?

Your help is much appreciated.

Thanks!

[HR]

So I have a DMD deposit that never arrived in my wallet... was there a blockchain switchover/fork or something?



I have tried to sync my wallet on both mac and PC but the DMD are not showing up in my account

I tried the block explorer for the txid ....returned null values

address: dcA2zFYYgvaWBaNBCb1UdLErGfdGtq6MSy
txid: e36a5d96352fb178bd9b2485ac922a1e3c847cde3d3c61224fe86ee910183b50


Thoughts?  Any feedback would be appreciated!

The Diamond block chain has struck due to an attack. It was decided to prematurely fork it and switch to Groestl hashing at that point. Surely, a lot of transactions have been canceled and some mined blocks too (I know to have mined two blocks myself during that time, that got orphaned).

Your DMDs are (back) at Criptsy's wallet. You should open a case with them to have the coins returned to your balance. Or, they should demonstrate where that transaction went..

I have almost the exact same issue (with only a slight difference in time and quantity of coins) with a support ticket that was opened soon after on April 29 whose status is still "Being Processed".

I have tried all three methods outlined in this support doc
https://cryptsy.freshdesk.com/support/solutions/articles/170993-3-methods-for

With both the new 2.0.1 wallet as well as the old 1.0.4 client.

All without success, and Cryptsy is apprised.

[srcxxx]

Hi!

What does foundation compatible mean?

I tried to read the link below, but it is 47th page about Summer Coin. No mention of "foundation".

Does it mean that from every 1 DMD that is mined on a pool, pool needs to send 5% to foundation?
If yes, then it means 1% pool will actually be 6% for miners, no?

PS: I'm looking into this while trying to figure out why my pool doesn't work. It breaks here:

    if (!Checkpoints::CheckSync(hash, pindexPrev))
    {
        if(!GetBoolArg("-nosynccheckpoints", false))
        {
            return error("AcceptBlock() : rejected by synchronized checkpoint");
        }
        else
        {
            strMiscWarning = _("WARNING: syncronized checkpoint violation detected, but skipped!");
        }
    }

Thank you

Tried compiling from github, no dice here either... If they can fix the code, we will add the coin to RejectMining.com

we did just compile a diamondd for linux
poolowner who wana betatest it send me PM

i need one for my p2pool but would be nice to compile it myself.
How to fix the code ?

source updated https://github.com/pitdmd/DMD_Pit

precompiled linux diamondd headless wallet https://mega.co.nz/#!XI5QlAzJ!xKD4JtMLpJPAGdf0rAmiwARkZfdYRAO9fE3BcL71NAU


please keep in mind pool need custom stratum u need to be groestl combatible stratum
and u need to be foundation share compatible

here some point to start researching regarding needed foundation stratum changes
only interesting for people who setup a pool https://bitcointalk.org/index.php?topic=581065.920

regarding groestl stratum changes please pool owner with already running groestlpool share their knowledge

WITHOUT FIXED STRATUM POOLS WONT GET ACCEPTED BLOCKS!

[mig6r]

Hello
I'm trying to mine (dmdpool) with sph sgminer and -k groestlcoin doesn't work.
What is the secret ?

example for AMD280:

sgminer.exe -k groestlcoin  -o http://dmdpool.digsys.bg:3345 -u cryptonit.2 -p 2   --gpu-engine 1100 --gpu-memclock 1100 --xintensity 300 -g 1 --thread-concurrency 8192 --difficulty-multiplier 0.0039062500 -w 256 --lookup-gap 0

Many thanks, it's ok !

[johndec2]

Would someone from the dev team like to answer the question?  It's not really all that difficult to clarify I would imagine.  The 400,000th coin should be minted in about a week.  I'm guessing that blocks are ahead of money supply due to a fork earlier in the coins life when some blocks got skipped.  I've seen it happen before.

Looks like the devs need to clarify the situation?  Is it 30 days after block 400,000 or is it 30 days after minting (pre or post algo change) ?

As I understood from the first post, POS will start when money supply will be more then 400 000 DMD.

Not after 400 000 block.

good one  Can you explain the difference ?

result of the - getinfo command in the wallet:

.....
"blocks" : 403436,
"moneysupply" : 387564.87036400,
.....

Looks like some blocks cost less then 1 dmd. Maybe it was in the first version of Diamond.

[cryptonit]

Would someone from the dev team like to answer the question?  It's not really all that difficult to clarify I would imagine.  The 400,000th coin should be minted in about a week.  I'm guessing that blocks are ahead of money supply due to a fork earlier in the coins life when some blocks got skipped.  I've seen it happen before.

Looks like the devs need to clarify the situation?  Is it 30 days after block 400,000 or is it 30 days after minting (pre or post algo change) ?

As I understood from the first post, POS will start when money supply will be more then 400 000 DMD.

Not after 400 000 block.

good one   Can you explain the difference ?

result of the - getinfo command in the wallet:

.....
"blocks" : 403436,
"moneysupply" : 387564.87036400,
.....

Looks like some blocks cost less then 1 dmd. Maybe it was in the first version of Diamond.

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

[danbi]

But, as the Diamond team people were repeatedly telling me in this thread while I was combating it, "are your blocks foundation compatible?"

That is, do you send 0.05 DMD to the DMD contribution address with each block?
What are your wallet log files showing? That is, whatever the reason for the reject, it *is* listed there.

I hope to be able to help with more issues soon.

Hi danbi!

Thank you for your help again.

This is what I'm getting in debug.log:

05/15/14 03:54:37 received block 0000000003d0ac2948ef
05/15/14 03:54:37 pindexBest = 388054pindexBest = 388054ERROR: AcceptBlock() : rejected by synchronized checkpoint
05/15/14 03:54:37 ERROR: ProcessBlock() : AcceptBlock FAILED

Also, what's the deal with 0.05 DMD? How do I do that?
Add a 0.5% fee in nomp pool config? If yes, what's the address?

Your help is much appreciated.

Thanks!

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

[johndec2]

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".

[danbi]

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".

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 

[johndec2]

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!

[popshot]

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!

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.

[johndec2]

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