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

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?

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

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.

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

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

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.

New clean block chain is available at


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.

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

No staking for me since that day 

Not most likely. For sure

Let's wait...

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

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.

Yes working fine for me too now. Cheers.

I see, kind of a tricky way of putting things and reason why people ask questions. If there is a pool fee (included in the increased hashrate), state it clearly in the OP or even better in the website homepage. End of story and explain why. I have seen some references in some of your posts though, yet you dimish it by saying there is not additional fee. Since we are not all coder/dev and experts in this, I thought there was no fee, now I am hearing I am being taken some small amounts without my knowledge, whatever the justification (larger hashrate etc etc). I have personnally no problem paying a fee as long as it is clearly stated. Artificially increasing hashrate in the web backend to justify a fee is not a transparent way of doing business.

As for putting things in your thread, well many questions have been posted in your thread for the past 4 days and no answers have been given. I took it on me to answer some questions to help others and now realize I did wrong. Specially on the no fee part... sigh

I hold no grudge Scrxxx, but please understand us, and please be PERFECTLY transparent.

If everyone thought the way you think then there would not be any crypto-currency to this day. Donation is not an obligation, and your statement makes it look otherwise. In that case it is better to promote it as a commercial product, at least it's clear.

Although I understand you want to be rewarded for the work you do, it's ALWAYS better to do it transparently. Your statement only makes people want to run away. The fact is that I am seeing by the day less and less people mining in your pool.

I am pretty sure you would get even more rewards if you made your optimized kernel open source. You just need to be patient and most of all have a long term vision of things.

I agree. Thank you Danbi for this. Helped me as well.

This is what my pool says:


And that is absolutely correct.

Is there a pool fee? yes.
But your hashrate is already multiplied by it (so your actual hashrate is a bit larger than what is displayed in grs-sgminer).
This was explained in grs-sgminer thread.

Please send such questions directly to grs-sgminer thread https://bitcointalksearch.org/topic/anngroestlmyriadgroestl-pool-closed-652849

Thanks

Thank you. I re-downloaded the blockchain on the pool server and now it seems to be working fine.

Same with my home PC, all is ok.

Do you know how is the optimized blockchain going to be better?
Just smaller in size?

Thanks

just saved me loads of time thanks!

If you have a backup of your blkindex.dat file use that one and and run a -loadblock=blk0001.dat. This should make the wallet run. This assertion problem has been discussed profusely in the past 5 pages. See for further details:

https://bitcointalksearch.org/topic/m.7533507
https://bitcointalksearch.org/topic/m.7569389