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

[jm1978]

i never mine in the multipool so i can not help u sorry U need to wait for some of the big fishes

[1714708971]

1714708971

[1714708971]

1714708971

[1714708971]

1714708971

[1714708971]

1714708971

[1714708971]

1714708971

[jm1978]

nice venezuela and south africa i think its first time i see active wallets there

DMD Diamond as "insider tip" where u dont share info or someone else will mine ur coins
that times are over

now main source of DMD production is bvia POS and to power ur POS coin generation u need coins u buy at exchange
who start mining now and think alone by mining create a nice share of DMD is clear to late

spread the word increase the family of diamond collectors

in my opinion for late adopters the troublesome times around last wallet release are a big chance
and did open a extended time window to be able buy in and get some cheap DMD to start ur own POS mining farm which use just a few watt

Well, Cuba is also in... im cuban 

[cryptonit]

DMD Multipool / DMD Cloud payout scripts will be activated again today
seems cryptsy fixed all issues and also returned the missing withdrawal balance

thx mullick

[cryptonit]

Well, Cuba is also in... im cuban  

good cocktails
good cigars
good music
beautiful women
and diamonds!

i love cuba!

[crazyivan]

Hi again, it's me with the payout issue from DMD multipool...

It's 8 days straight now with hardly any news. Have been toldd that issues are resolved and that in a few hours (that was almost a day and a half ago...) payouts would be resumed.

I think it is not normal by now and starting to be rather suspicious.

Can someone from the exchange put some light into this, and give a final date and time for payout resumes?? My BTC are at the exchange, who for sure is making good use of them... And it should be me, who should be making profit on those BTC's... whatever quantity it may be.

Awaiting for a reply, TIA.

Hey Whitesox,

no need to worry, you should have received your multipool payment by now. We did get stuck for a few since Cryptsy wallet was offline but Mullick and their great support fixed it.
I can understand you being suspicious, especially if you had some bad experience with other coins but I can tell you one thing:

DMD dev team are the most honest people you can find in the Crypto world. There s more chance of aliens invading our planet then somebody from DMD development team scamming you. This is why this coin s got a bright future.

Thx for being patient and let us continue building this great community together.

[mullick]

Hi again, it's me with the payout issue from DMD multipool...

It's 8 days straight now with hardly any news. Have been toldd that issues are resolved and that in a few hours (that was almost a day and a half ago...) payouts would be resumed.

I think it is not normal by now and starting to be rather suspicious.

Can someone from the exchange put some light into this, and give a final date and time for payout resumes?? My BTC are at the exchange, who for sure is making good use of them... And it should be me, who should be making profit on those BTC's... whatever quantity it may be.

Awaiting for a reply, TIA.

Hey Whitesox,

no need to worry, you should have received your multipool payment by now. We did get stuck for a few since Cryptsy wallet was offline but Mullick and their great support fixed it.
I can understand you being suspicious, especially if you had some bad experience with other coins but I can tell you one thing:

DMD dev team are the most honest people you can find in the Crypto world. There s more chance of aliens invading our planet then somebody from DMD development team scamming you. This is why this coin s got a bright future.

Thx for being patient and let us continue building this great community together.

Just wanted to back this up. The cryptsy account for the dmd.multipool did have a withdrawal sent out on the bad chain. And it could not be fixed until our wallet was resynced.

It was resolved on our end today. We apologize for the inconvenience this caused

[cryptonit]

DMD Multipool and DMD Cloudmining  finished converting BTC to DMD and everyone should have recieved the DMD by now

will try to do a reactor payout round today too

i can see market react positive to fixed cryptsy deposit/withdraw
buyorderbook fills nice

lets see if the expected slow but continious value rise after POW reward reduction now will become visible

[pokeytex]

DMD Multipool and DMD Cloudmining  finished converting BTC to DMD and everyone should have recieved the DMD by now

will try to do a reactor payout round today too

i can see market react positive to fixed cryptsy deposit/withdraw
buyorderbook fills nice

lets see if the expected slow but continious value rise after POW reward reduction now will become visible

Thanks for the update.  Nice surprise in my wallet this morning!  Good day all.
-pokeytex

[cryptonit]

Reactor payout round finished 1253 DMD split between DMD Cloudmining shareholders

[Whitesox]

Hi again, it's me with the payout issue from DMD multipool...

It's 8 days straight now with hardly any news. Have been toldd that issues are resolved and that in a few hours (that was almost a day and a half ago...) payouts would be resumed.

I think it is not normal by now and starting to be rather suspicious.

Can someone from the exchange put some light into this, and give a final date and time for payout resumes?? My BTC are at the exchange, who for sure is making good use of them... And it should be me, who should be making profit on those BTC's... whatever quantity it may be.

Awaiting for a reply, TIA.

Hey Whitesox,

no need to worry, you should have received your multipool payment by now. We did get stuck for a few since Cryptsy wallet was offline but Mullick and their great support fixed it.
I can understand you being suspicious, especially if you had some bad experience with other coins but I can tell you one thing:

DMD dev team are the most honest people you can find in the Crypto world. There s more chance of aliens invading our planet then somebody from DMD development team scamming you. This is why this coin s got a bright future.

Thx for being patient and let us continue building this great community together.

Hi CrazyIvan, and thnxs for your info...

At the moment of this post I have received some beautiful 145DMD's... (I'm no whale, just small Krill...)

And please, let me correct you with all due respect... My doubts where AT NO POINT directed to the DMD community/devTeam but more towards Craptsy... Seems TOOOO long 8 days to get a problem solved for such a company as Craptsy.

And yes, I have lost coins, but mostly has been on exchanges... FYI.

So I do rely on you DevTeam with no doubt.

Now that I got the coins, I have to believe a bit more in Craptsy.

Thnxs again for all your help and calming info.

TO MARS!!!! AND BEYOOOND!!! (Moon has already been taken by DOGE/DOGED and we expect to go WAY further, don't we???)

[danbi]

New wallet version 2.0.5.7
Release URL: https://github.com/DMDcoin/Diamond/releases/tag/diamond2057

This wallet is not mandatory. However, due to new functionality and improved CPU usage it is highly recommended especially for loaded nodes, such as those that mine/mint, pools and exchanges. It should also improve performance for everyone.
Binaries for Windows and OS X (tonight) are provided. Just replace your own binary. If you build form source, stop old binary, start new binary. No other update action is required.

Changelog:

Optimizations to call hash calculation functions less.
Small optimization to Groestl hash routine.
Ban nodes that are disconnected due to old version/protocol.
Implement -zapwallettxes, borrowed/adapted Bitcoin code.
Implement ACL for connected nodes.
Fix bugs in seed node processing.
Add and activate seed nodes to facilitate bootstrap without config file.
Turn IRC off by default. (IRC may be removed in future)
Increase maximum number of outgoing connections to 16
Limit output to log file if debug is disabled.
Update wallet version to 2.0.5.7

Of special interest is -zapwallettxes. This command switch (or config file option) will wipe out any existing transactions in the wallet, then initiate rescan of the block chain (slow!) to find out the valid transactions for your coins. If used as -zapwallettxes=1 it would also preserve transaction comments etc. If used as -zapwallettxes=2 it will do a clean rebuild of the transactions without those details. If you put it in the config file, make sure you remove it after first use, as it will do the same (slow!) thing every time you start your wallet.
If you run a busy wallet, that sends a lot of (not PoS) transactions you might want to run this periodically to make sure your wallet transaction acconting is in sync with the block chain.

The new wallet is able to start without any config file. It would then use the seed nodes to find out about other nodes and connect to them as well. This lets us get rid of IRC in some o the next updates.

The new wallet code also makes certain optimisations to reduce the number of hash function calls for each block. More optimisations are planned in this area to improve CPU usage further. It also reduces the amount of log file output, if debug is disabled to reduce storage I/O load.

[crazyivan]

No problem Whitesox, I completely understand you.

Not only we have a honest dev team but also a very busy dev team. This new wallet update is a perfect proof of that. It is not a mandatory update but it does bring a lot of interesting features and improvements.

To the MARS then, as you put it. 

[elbandi]

is there an official bootstrap.dat file?

[cryptonit]

is there an official bootstrap.dat file?

https://mega.co.nz/#!IQwRjCwS!jfAqWzbBXZy-5oRsgl0LeFrmMMJRgpBXrU6SZVuGHLU
backup of my blockchain

if u dont like to use the files and want sync with help of a bootstrap.dat

extract only blk0001.dat rename  to bootstrap.dat and place it into your diamond folder

will need some hours to sync but still faster than sync over network

[Galactus]

What should now be by default diamond.conf after updating to version 2.0.5.7?

[cryptonit]

What should now be by default diamond.conf after updating to version 2.0.5.7?

if u have no special needs example solo mining
which require settings in diamond.conf
u can now run without a diamond.conf

if u want to have a diamond.conf i suggest


listen=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
addnode=167.114.184.20
addnode=37.187.176.193
#community nodes 2015.04.23
addnode=93.89.139.77
addnode=213.229.0.41
addnode=193.136.96.30
addnode=193.136.97.30
bantime=3600
maxconnections=30

(adapt maxconnections fit to ur system higher value contribute more towards network
20-30 for  weak systems 40-50 for medium systems up to 100 for strong cpu lot ram fast internet connection)

[Galactus]

cryptonit
noirc=1 now it isn't necessary?

[popshot]

cryptonit
noirc=1 now it isn't necessary?

Changelog:

Turn IRC off by default. (IRC may be removed in future)

[cryptonit]

lets track a open issue list:

# min age effective 9 days not 3 days like intended
# mouseovertext over minting diamond symbol bottom right display high inaccurate data

---------------------------------------------------
please report points u consider as wallet bugs
i will update list with valid points

beside this two minor issues i see the actual wallet code very good and improved
higher effective min age time was disturbing at first but it have no negative impact on POS

the mouseovertext is very confusing and missleading
a minimal fix would be just remove estimated times and display only
"wallet is in minting mode
u have coins who are qualified to compete for POS blocks
longer wallet online time increase the chance u find a block"

[NoobKidOnTheBlock]

I am really impressed with this coin and think that it is heavily undervalued big time for the price that people are selling it for Keep up the amazing work folks