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

yes
but with all the experience people gathered now at
http://multipool.bit.diamonds/
u can basically mine DMD with any major algo
with groestl direct and with a lot indirect

everyone who still have low network connections
a blockcount that is different from blockexplorer http://dmdpool.digsys.bg/bc/
and strange wallet behavior please make sure u redownload the latest wallet
http://sourceforge.net/projects/diamonddmd/files/diamond-qt-2.0.4.exe/download
thx

when pow goes active again it will be Groetsl algo again right?  

I too had a similar problem, but after re-upgrade wallet, level network connection was restored.  The number of empty blocks is significantly reduced.

Ditto

Only 2 out of 4 connect=

14:57:23

getpeerinfo


14:57:23

[
{
"addr" : "54.191.208.14",
"services" : "00000001",
"lastsend" : 1411504331,
"lastrecv" : 1411504331,
"conntime" : 1411498217,
"version" : 60006,
"subver" : "/Diamond:2.0.3.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 577468,
"banscore" : 0
},
{
"addr" : "193.68.21.19",
"services" : "00000001",
"lastsend" : 1411504331,
"lastrecv" : 1411504271,
"conntime" : 1411500622,
"version" : 60006,
"subver" : "/Diamond:2.0.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 577469,
"banscore" : 0
}
]

I am noticing that with new wallet, clean blockchain even whole new wallet.dat/new address my wallet is only making two at most three connections when there should be four? Seems to be getting disconnected. Has one of the nodes been switched off or is my ip ban in network or is this some other issue?

Ok - crazy questions - I noticed in the last (2) days a lot of stale mints (?'s) that is.  Does this have something to do with the mining on the windows wallet issue?  As a precaution I downloaded the new blockchain and wallet as outlined above.  Just wondering if we will have an issue once pow goes active again.

I ditto that. Very strange.
But this happens only when downloading from danbi's webiste. It hasn't shown the warning message when downloading from SourceForge.

That's what Google has to say:  

So, I assume the system is a bit overreactive.

For the first time ever Chrome threw up a malware warning about the wallet. I have never had this happen with the Diamond wallet.

Diamond wallet version 2.0.4

The exact procedure has been outlined many times in this procedure, but I will repeat it again.

1. Make sure you have no existing Diamond installation/blockchain. If you do, move them out of the way.

2. Prepare an configuration file. The file should contain this (you can replace the connect= destination with a known good node):

listen=0
noirc=1
connect=193.68.21.19

3. Make sure the peers.dat file is deleted.

4. Run the Diamond wallet and wait until it syncs fully with the network.

5. Stop the Diamond wallet. Here, it is advisable you use the -detachdb flag or stop it with "diamondd stop true" in order to detach the database from environment. This will make it irrelevant to backup the contents of the database/ directory.

6. Copy the files blk0001.dat, blkindex.dat and database/* to a new directory, in this case with the name of the archive you will be creating. In this case dmdchainYYYYMMDD (YYYY - year, MM - month, DD - day) is used.

7. Run "zip -r9 archivename archivedir" to create an ZIP archive.

8. Run "7z a -mx=9 archivename.7z archivedir" to create an 7zip archive.

That's pretty much it. On Windows, you are likely to use GUI interfaces to these programs.

What program do you use for generate this files?

as u see error-devil never sleeps
but i think our response and reaction times improved a lot

that just mean u successfull minted with all ur coins
because blocks come slow until POW reactivated it will need some time until u have them back in balance (200 blocks)

Today, we have discovered that some nodes were submitting blocks that were coming from mining. Such situation shouldn't have been possible. After doing some research, we found out that Windows Diamond Wallet binary that had been published was a release candidate and not the final version. We urge you to re-download the Windows wallet, especially those people who for some reason mine; all your blocks are being rejected, you are wasting electricity and making the network unstable. This will effectively make you clients banned and could move you to the wrong fork.

By downloading the correct wallet, the wallet will repair itself and drop all wrong blocks - which ultimately would spare you redonwloading the blockchain.

This concerns only Windows (binary) users - Mac Wallet and the source are the correct versions.

We apologise for this situation; we must have been very tired already that evening after spending a few days assembling this emergency update. When people are tired all kinds of silly mistakes can happen. From now on we will be double checking the files we upload with the use of MD5.
  

Windows wallet:
http://diamond.danbo.bg/downloads/diamond-qt-2.0.4.exe
or
http://sourceforge.net/projects/diamonddmd/files/diamond-qt-2.0.4.exe/download

Latest clean block chain (not necessary but some might find it helpful):
http://diamond.danbo.bg/downloads/dmdchain20140923-clean.zip
or
http://diamond.danbo.bg/downloads/dmdchain20140923-clean.7z

Does the new wallet reset coin age?  I updated from 2.0.3.1 and was actively staking (weight 7796) when I shut down the wallet.  When I brought up 2.0.4 just a minute later, my balance shows 0, with the entire balance is in the stake column, but the wallet says I am not staking because I do not have mature coins.  Since the balance is 0, with all of the coins listed under Stake, I can't do anything with the coins, either.

feedback i wana share:


I can just say thx and please excuse i share your words
there is just no better promotion than someone who speak his true opinion!
This is what drive our engine and let motivation never end to make @dmdcoin  a successstory
https://twitter.com/CryptonitDMD/status/514160878875574272

and yes he is talking about:
This is the last week to join in and still earn september full reinvest bonus!
[email protected]

The PoS does not create additional addresses, nor does it create any change. PoS is sending the coins together with the interest back to the same address that had them. This is why PoS can only group coins from the same address in one pile (up to 100 DMD).

The wallet still has 'transaction bloat' in that it grows in size. But these transactions are not traversed each time the wallet needs to decide on coins, as happens with addresses, so it does not slow down the operation.

In general, it does not hurt to set the change address to your wallet's 'main' address, or even to an address in another wallet that you may have. What you 'lose' is the 'anonymity' of your transactions, which as I explained is a bit overstated anyway (except if you do not take special precautions, but then you know what you are doing). If you ever want to send some coins from your wallet, you won't by accident create new addresses.

You can examine what and how many addresses you have in your wallet with the 'listaddressgroupings' RPC/console command. You were not aware you had that many addresses, right?

seems x13 is best payout at nicehash for the moment to maximize ur DMD Multipool earnings
if ya mining x11 there maybe give it a try (most x11 mining solutions should be able mine x13 too)

http://multipool.bit.diamonds/

thanks danbi.
a couple questions:
do you suggest to set a change address even for wallets which don't make a lot of send transactions?
are the minting transactions creating such additional hidden change addresses as well?

The new change address functionality.

Diamond v2.0.4 brings new functionality to reduce wallet bloat. I will repeat the premise and reasons here with introduction to the interface.

The Bitcoin protocol is designed in such a way, that when you send coins, you almost always end up with some 'change'. This happens, because the protocol operates on 'amounts' (that you either generated, received or were result of such 'change' operation). The amounts, unlike fiat currencies are not in set number of denominations. Instead, each Bitcoin 'amount' is an number of "satoshi" represented as a number with many decimal places. When you send some amount to someone, a subset of your existing coins is picked up (either automatically, using rather primitive algorithm, or manually via coin control). The total sum of this amount being X is chosen to be larger than the amount you wish to send plus any fees. When you send the amount Y, the remainder, which is Z = X - Y is sent to a new address, which is specifically created for the purpose to hold your 'new change'. The idea here is to assure you of anonymity for your cash flow, because nobody could know which is the sent amount and which is the change. Which in essence 'sits' in your own wallet, because you now have new keys to claim it.
The Bitcoin wallet assumption and claims of privacy are however not always true, as (because of the way amounts in the wallet are chosen) it is often trivial to track whose the change is. From now on, we will talk about Diamond, but please bear in mind this is fundamental protocol principle inherited from Bitcoin and present in virtually all crypto coins.

In summary, imagine you have received an amount of 500 DMD. You believe you have just one Diamond address in your wallet (where you received that amount). This might be the case until that moment. But, one day you decide to send someone 10 DMD. The protocol has no way to subtract from the amount you have. Instead, it needs to destroy the old amount and create two new amounts. Actually three: the amount you wish to send, 10 DMD, the fee, usually 0.001 DMD and the remainder, the change 489.009 DMD. While performing the send operation, your wallet creates a new Diamond address and sends the change there. Now, you have two new addresses in your Diamond wallet (it has grown with the required records). With every send you do, this is repeated. Now, the Diamond wallet makes things convenient for you, and hides these 'change' addresses. You might have thousands of them, and not be aware. As a result, your wallet is working slower and slower -- this includes everything, from opening it to sending to PoS.

Coin control we implemented some time ago lets you select the change address. But this only works in the GUI and is not very convenient. It is also completely useless for pools and exchanges that are the primary victims of wallet bloat. This is why this new functionality was necessary.

The new functionality provides two interfaces:

1. A command line option, -changeaddress which is also available in the configuration file as changeaddress= that lets  you give the Diamond address you want the change to go to. This can be an address in the same wallet, or elsewhere. You specify this option/parameter at start up time.

2. A pair of getchangeaddress/setchangeaddress RPC commands that let you programmatically control the change address and also clear it. The commands are as follows:

getchangeaddress

returns the current change address, or nothing if there is no address set.

setchangeaddress DiamondAddress

sets the change address, or if the address is given as '' clears it. You can also clear an change address that was set via the command line of configuration file.

Having an change address set up for the wallet makes the change in any future send transaction go to that specific address. No new addresses are created in the wallet and there is no more bloat.

Unfortunately, this functionality does not 'clean' your existing bloat. We are working on that, but not yet done.