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

Congrats to dDzf6pvTV63wFFw3nTZyGv4ZysKitnySPZ for finding 4th block
I just received first payout 1st confirmed block from pool so I can verify that is working
payments sent to:
dETfZeUtj21VyKFDCQgJEJmYspVv5z1jU4: 0.456172 (unknown)
dP4Nd5jXyQyMEunf9iXnRxRKjxsenJaeY2: 0.532829 (myself)

I'm upping the payout threshold to 1 DMD in a few hours so transaction fees don't eat me up (Seeded pool wallet to make sure transaction fees covered).

i guess u need to read it again
https://bitcointalksearch.org/topic/m.8336153

will be updated tomorrow

what new in 2.0.3.1?

Git looks to be still on 2.0.3

Windows -QT
http://sourceforge.net/projects/diamonddmd/files/diamond-qt-2.0.3.1.exe/download

Mac
http://sourceforge.net/projects/diamonddmd/files/diamond-qt-2.0.3.1.dmg/download

@Danbi
Linux source posted yet?

This is an update on the development progress.

We will be releasing version 2.0.3.1 now, that includes the following changes:

- rejects connections from version 2.0.2.1. This will block both 2.0.2.1 and 2.0.2.2, the later being harmed because it identifies as 2.0.2.1. This is necessary, because this version permits communication with older versions, that do not understand the current PoS protocol, but could inject malformed blocks in the network.

- lowers the peer penalty for "not enough work" blocks received. Originally, the penalty is set to the maximum threshold to ban the peer node. This essentially means that once you get infected you can never talk to other nodes until you junk your block chain and sync again.

- makes small correction to the sync checkpoint protocol, which seeks to reduce/eliminate the chance of arriving at this "not enough work" situation.

All these chances do not fully resolve the issues, but provide for much faster network convergence. Version 2.0.3.1 is already running on the announced permanent nodes, which has resulted in the network withstanding few more attacks.

Please note version 2.0.3.1 is not a mandatory update. You use it to save yourself some headaches, eventually.

We have identified the reason(s) for the block index corruption. The code defect is present in most (all?) ppcoin descendants, but requires specific conditions to be triggered. It so happens that Diamond is a bit more susceptible to such bad block injection, because of past data in the block chain. Both the current data corruption and the original problem are being addressed, but since this requires very slow testing, we decided to release 2.0.3.1 now in order to help some users.

We also know what is causing the "not enough work" problem. This requires a bit more complex fix, and more testing. Again, the code deficiency is not unique to Diamond.

Only first 5 block finders will be posted from now on with their respective rewards for beta testing (after 5 blocks confirmed).  Sorry about cluttering thread but I need testers
Testers will get rewards as blocks get confirmed.  And I will post winners when contest finished

utahjohn i hope ur pool dont find lot blocks 
if u write a posting for each here

2nd block found It was dP4Nd5jXyQyMEunf9iXnRxRKjxsenJaeY2 (that's me) again (It's nice having close to zero lag time to server (My miners on LAN here) ).
So 5 DMD total still available for bonus (from my Alpha testing of the pool) So that is 1.66666667 DMD bonus each for next 3 block finders on my testing pool ...

First block on my DMD testing pool found, Looking thru log to see who it was and bonus will be sent to tester when block confirmed
Only 4 more DMD left for bonus now ... so get in while you can (only 1 DMD bonus each for first 5 block finders).

It was dP4Nd5jXyQyMEunf9iXnRxRKjxsenJaeY2 (that's me)
So 5 DMD total still available for bonus (from my Alpha testing of the pool) So that is 1.25 DMD bonus each for next 4 block finders on my testing pool ...

Thanks for the clarification cryptonit  As this is also my goal to get Multipool paying DMD directly going.
I think it will be a good thing to have more pools online.  Currently I am only mining DMD for DMD payout at my beta pool (address in sig).
The ability to get paid in whatever coin desired is my focus, as well as Wafflepool also working on this using an internal pool exchange instead of relying on outside exchanges.  (This would just monitor current coin exchange rates from exchanges used by coin).  If pool internal resources of coin are exhausted then outside exchange would be used, thus avoiding exchange transaction costs and fees whenever possible

if u allow dmd  payout at ur pool we can announce it as a pool on our ANN

but we wont announce a non dmd payout pool even if he mine dmd

Awesome. Thanks!
Oh forgot to add my stratum host

stratum+tcp://judge.bemining.net:9969 -u DMDAddress -p DMD

I am testing the ability for miners to 'tell me' what they want their payout in. :-)

its not really helping us if a judgecoin payout multipool mine dmd
thats mean 100% sell pressure from all coins mined there

thats exacltly the opposite of a dmd payout multipool.......

avoid beeing mined and insta-sold
and mine other coins and insta-sell them for creating buy-pressure on own coin.....

one reason why we left scrypt was asic second was to get rid of multipools......

Welcome to the thread sigwo.  Danbi is lead wallet dev here, I believe and he can answer your questions ...

The Judge team multipool has added diamond   I am part of dev team there.
http://judge.bemining.net/

They don't have as many testers as I do on my diamond pool yet LOL.
All my hashrate now going to my own testing

Anyone care to point me to the DMD hashing algo explanation? I was told by /u/utahjohn that it is a variant of groestl. I would like to add DMD to my pool. Thanks!