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

[polanskiman]

@danbi

Is your pool website down? I'm unable to connect to http://dmdpool.digsys.bg/.
Is mining in the pool working or not?

The pool is running fine, has about 100 miners connected. The web frontend works, the pushpool and the stratum interfaces work. Pool is finding blocks.

Perhaps a network problem? What do ping and traceroute say?

I can't connect to the web frontend either. Ping, traceroute, lookup, port scan. All failed

Now it's working again, at least for me, after almost 2 hours. Must have been some DNS problem somewhere. Hope it does work for you too now Polanskiman. Thank you for testing things that I'm not quite sure how to do

Yes working fine for me too now. Cheers.

[polanskiman]

By the way, my 2.0.2.2 MAC compiled version worked fine yesterday. Today I downloaded the officially posted 2.0.2.2 version and again the assertion problem appeared.

[utahjohn]

By the way, my 2.0.2.2 MAC compiled version worked fine yesterday. Today I downloaded the officially posted 2.0.2.2 version and again the assertion problem appeared.

Most likely still a blockchain database problem, that's why I am waiting for the official clean blockchain database

Not a big deal to wait a day, your coins are still gaining age  I have limited resouces and am concentrating on mining Maiacoin (X15 Limited PoW, then pure PoS).  I probably won't be mining DMD for another 19 days till PoW phase on Maiacoin is over anyway BTW I am staking on it already

[polanskiman]

By the way, my 2.0.2.2 MAC compiled version worked fine yesterday. Today I downloaded the officially posted 2.0.2.2 version and again the assertion problem appeared.

Most likely still a blockchain database problem, that's why I am waiting for the official clean blockchain database

Not most likely. For sure

Let's wait...

[polanskiman]

By the way, my 2.0.2.2 MAC compiled version worked fine yesterday. Today I downloaded the officially posted 2.0.2.2 version and again the assertion problem appeared.

Most likely still a blockchain database problem, that's why I am waiting for the official clean blockchain database

Not a big deal to wait a day, your coins are still gaining age  I have limited resouces and am concentrating on mining Maiacoin (X15 Limited PoW, then pure PoS).  I probably won't be mining DMD for another 19 days till PoW phase on Maiacoin is over anyway BTW I am staking on it already

Like those that I lost during the PoS fiasco on 26/06? 

No staking for me since that day 

[danbi]

New clean block chain is available at

Code:

ftp://diamond.danbo.bg/dmdchain20140701.zip

It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.

As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.

[danbi]

This has been covered in previous posts, read last few pages

I did read them. Perhaps I missed something, could you point me to the exact post?
Are you referring to the "a better one is being built" blockchain?

The main page still has the link to Original.rar which is old.

And also what should I do once the blockchain has downloaded from that single node?
I probably need  to somehow switch to multiple nodes again?

It is exactly the same as with any other coin. You are welcome to use this "trick" with your own coin, as well ;-)

Some explanation:
The bitcoin block chain local storage is designed in such a way, that it would store more or less each and every block it receives, including orphans. This is so, because of the requirement to be able to switch to the "better" chain. Ironically, it is so also for very old heavily confirmed blocks (and old orphans) that have no chance to be elected as valid, ever.. but the database is designed in such a way as to "never delete from the blkxxxxx.dat".

Fortunately, any node in the network with correct software, will feed you only one copy of each block so the easiest way to filter out this cruft is to just delete the blockchain and download it again. Still, if you do this in a live network, different nodes will send you different blocks at different times, so you will again accumulate some (but less) cruft. This is why it is important to control your connections. It can be any node that runs current software.

In theory, you could run with one or more connect= statements in your configuration all the time. This will work better overall, as you will spend less resources, probably sync faster etc, BUT will expose you to a situation where you disconnect from the network if all your connect= nodes go down. The bitcoin network is however designed to be used by people who will not spend their time monitoring the software and will just expect it to work -- this is why it has so many auto-configuration mechanisms built in, which sometimes create little havoc. But.. this is life.

You are welcome.

[utahjohn]

New clean block chain is available at

ftp://diamond.danbo.bg/dmdchain20140701.zip

It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.

As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.

I get server not found using the link edit the http:// out of your link

[cryptonit]

New clean block chain is available at

ftp://diamond.danbo.bg/dmdchain20140701.zip

It is almost twice less in size than the previous one provided, which was bloated with more than one copy of the same block.

As discussed earlier, it was created by connecting to a known good node (one running current software) ONLY, disabling IRC learning of peers, incoming connections and removing peers.dat. Anyone can create such a distilled blockchain -- we do this all the time to test the new client functions normally, this one is provided just for your convenience.

I get server not found using the link edit the http:// out of your link

Code:

 ftp://diamond.danbo.bg/dmdchain20140701.zip 

[utahjohn]

Damn your ftp server is overloaded started d/l at 150K+ now down to 50-60K ... oh well still the fastest method to get my wallet back up ...

[danbi]

Just a word of warning, regarding that dreaded block index corruption problem.

The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.

The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.

[danbi]

Damn your ftp server is overloaded started d/l at 150K+ now down to 50-60K ... oh well still the fastest method to get my wallet back up ...

Will improve soon. Loading a web server there as this forum software suggests all the time

[Coinler]

hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?

[polanskiman]

Just a word of warning, regarding that dreaded block index corruption problem.

The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.

The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.

I know. Just found it strange that it did work yesterday with the compiled version I did. I closed the wallet several times and all good. This morning I tried to use your compiled version and the assertion pb poped up again. I am aware that this update does not fix per say the assertion problem directly but it does address it indirectly by preventing older wallets predating 2.0.2.1 to connect? Or Perhaps even 2.0.2.1 wallets are also feeding loads of orphans to 2.0.2.2?

[polanskiman]

hi does anyone have a config for this coin? i was mining groestlcoin and switched to dmd but for some reason it doesnt connect to the pool at all?

Please be more precise in what problem you are encoutering. It would help us in helping you.

[danbi]

Just a word of warning, regarding that dreaded block index corruption problem.

The wallet version 2.0.2.2 does NOT fix it. It only makes sure old nodes that apparently send the deadly orphan blocks cannot connect to you.
This problem only affects the block index (blkindex.dat) and not the block chain (blk0001.dat) or the wallet (wallet.dat). There is no corruption there and no coins are lost etc.
We decided to spend the time with this release now in order to give you tools to deal with and recover faster.

The real issue is being investigated and possibly several independent fixes will be implemented. Unfortunately, it seems to happen with other coins too but none has found a solution so far.

I know. Just found it strange that it did work yesterday with the compiled version I did. I closed the wallet several times and all good. This morning I tried to use your compiled version and the assertion pb poped up again. I am aware that this update does not fix per say the assertion problem directly but it does address it indirectly by preventing older wallets predating 2.0.2.1 to connect? Or Perhaps even 2.0.2.1 wallets are also feeding loads of orphans to 2.0.2.2?

This is also possible. However, we have identified only pre 2.0.2.1 nodes doing it...

Anyway, I don't think it is the code/compilation. It is the "old" wallet that corrupted the database, the new just bombs on it, just as the old would.
Did you have any chance to test my build on other OS X versions than Mavericks? maybe it needs adapting -- now that the code is in github, perhaps you could do another compare Thanks!

[polanskiman]

This is also possible. However, we have identified only pre 2.0.2.1 nodes doing it...

Anyway, I don't think it is the code/compilation. It is the "old" wallet that corrupted the database, the new just bombs on it, just as the old would.
Did you have any chance to test my build on other OS X versions than Mavericks? maybe it needs adapting -- now that the code is in github, perhaps you could do another compare Thanks!

My current environments are all in 10.9. One in 10.9.2 and one in 10.9.3. My old MAC running 10.7 is dead. Anyone else using MAC among the DMDers? Or I am the only black sheep?

What do you mean another compare? I used the updated code from your github repo to compile yesterday. Both yours and my release are based on the exact same code. The only difference lies on the version I am compiling with. I am currently using Qt 4.8.6 instead of Qt 5.3.0

[utahjohn]

Great work Danbi   My wallet fired right up after placing new clean blockchain in.. Sync'd in a matter of minutes

[utahjohn]

http://xgold.org/#whatis

[utahjohn]

02:01:50

getcheckpoint


02:01:50

{
"synccheckpoint" : "000000000390100991ea4a9fd7e6d8e1c503821dc5ee96449049d9f1367b1703",
"height" : 469658,
"timestamp" : "2014-07-01 07:57:29 UTC"
}

getpeerinfo showing all connections to 2.0.2.1 at moment ... give it a day or so for users to update ...

Unfortuately those on 2.0.2.1 will still be accepting connections from older clients.  I would post a new database in a week or so after majority have updated to 2.0.2.2.