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

[polanskiman]

I had a backup copy of wallet.dat that was dated before the 26th, I used that one and did a full sync, all my failed mints dissapeared .. just yesterday I minted sucessfuly twice

As already stated by Danbi on post #1577 (https://bitcointalk.org/index.php?topic=580725.msg7569389#msg7569389) using an old backup (specially pre-dating PoS) of your wallet is not a good idea. I quote:

"Important: Because of the way PoS works, you should never restore your wallet from an old copy, once you have minted coins via PoS. This is, because PoS (sometimes) creates new private/public keys (addresses in your wallet)  and sends minted coins to these addresses in your wallet. If you restore an old wallet you will not have the secret keys and your minted amounts will be gone for good. Once you start minting, always make frequent backups of your wallet.dat file!"

Those who still have minted coins that are valid, you've been warn in doing such wallet swaps.

The only stake attempt the day of 26th when PoS started was a failed mint, I don't mind losing that from wallet

The backup I used was a few days before 26th before minting.
I have staked successfully since re-sync with backup and have backed up wallet after minting, I feel safe with that

Good, but if you noticed, I said "Those who still have minted coins that are valid". My message was meant as a warning to those who might blindly attempt your advice without reading previous posts, and god knows there are a lot here.

[danbi]

same problem even if i copy the blockchain before close the wallet then open it again it's won't load same error

It wont work. You need to use a block-chain pre-dating the PoS each time you close and re-open your wallet. Even after synching if you backup the block-chain and try to using it, you will end up with the same assertion error.

Some have stated that re-downloading the wallet from scratch eventually solved the assertion error. I haven't tried that.

This is not entirely true. You do not need pre-PoS block chain. The problem is not in the block chain itself, it is a corruption in the local (on disk) block index database. We do not yet have a fix for it.

All we know is this problem is caused/accelerated by bogus nodes on the network feeding lots of orphans (you can detect them by looking in the log file -- they will feed you like 100 ORPHAN blocks then your node will disconnect them for misbehaving -- but that would be too late).

We will have a new wallet version today that will just disconnect these old nodes, as we should -- because they need to upgrade in order to participate in the current network.

I will also upload later today an up to date block chain that does not have corrupted block index.

[polanskiman]

same problem even if i copy the blockchain before close the wallet then open it again it's won't load same error

It wont work. You need to use a block-chain pre-dating the PoS each time you close and re-open your wallet. Even after synching if you backup the block-chain and try to using it, you will end up with the same assertion error.

Some have stated that re-downloading the wallet from scratch eventually solved the assertion error. I haven't tried that.

This is not entirely true. You do not need pre-PoS block chain. The problem is not in the block chain itself, it is a corruption in the local (on disk) block index database. We do not yet have a fix for it.

All we know is this problem is caused/accelerated by bogus nodes on the network feeding lots of orphans (you can detect them by looking in the log file -- they will feed you like 100 ORPHAN blocks then your node will disconnect them for misbehaving -- but that would be too late).

We will have a new wallet version today that will just disconnect these old nodes, as we should -- because they need to upgrade in order to participate in the current network.

I will also upload later today an up to date block chain that does not have corrupted block index.

Thanks for the clarifications. Will a MAC client version be also available?

[istvandv]

We will have a new wallet version today that will just disconnect these old nodes, as we should -- because they need to upgrade in order to participate in the current network.

I will also upload later today an up to date block chain that does not have corrupted block index.

+1 for new wallet to kick those old nodes
+1 up to date block chain

 

[danbi]

Thanks for the clarifications. Will a MAC client version be also available?

A Mac wallet will be available too.

[polanskiman]

Thanks for the clarifications. Will a MAC client version be also available?

A Mac wallet will be available too.

You're the man. Any help needed?

[4roxx101]

DO NOT SEND COINS TO CRYPTSY,.  I believe they are still on the V1 wallet.

the .... i mean dev needs to sort this out the lazy idiot just lost me alot of coins.

will you remove this aswell??

[popshot]

will you remove this aswell??

Thank you, that's much better.
However not sure what you want from us ... We are not the owners of Cryptsy. File the freshdesk ticket and experience first hand the dealings with that exchange.
We've just hard forked so quite impossible that they are still using the old client as people would not be able to make withdrawals from there, but they can - at least small amounts as reported.

[4roxx101]

how is that better,. the fact is still the same,. the OP needs updating.

[4roxx101]

will you remove this aswell??

Thank you, that's much better.

I see you the mean guy here,. can i ask a question,.

Why do you list crypsty as a trade site when they are not geared up to take you coin?

[stoody]

i think this is the right blockchain



{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}

[4roxx101]

So very quick to remove posts but not answer them,. even worse not answer a pm. well done here guys,. you should be proud of your achievements.

[stoody]

So very quick to remove posts but not answer them,. even worse not answer a pm. well done here guys,. you should be proud of your achievements.

i have been buying and selling DMD on cryptsy every day and i havent had any prob 30 DMD on the 29th 49 DMD on the 27th and 120 dmd on the 24th of this month... i would check the wallet ID number u sent it to... i changed mine when the new wallet came out...

[danbi]

Thanks for the clarifications. Will a MAC client version be also available?

A Mac wallet will be available too.

You're the man. Any help needed?

Code is already on github, but I forgot my portable build environment, so it will have to wait for the evening (EU time).

[pallas]

Code is already on github, but I forgot my portable build environment, so it will have to wait for the evening (EU time).

Can I already compile the headless wallet or should I wait?

[danbi]

Code is already on github, but I forgot my portable build environment, so it will have to wait for the evening (EU time).

Can I already compile the headless wallet or should I wait?

Yes, you could also compile it with GUI on any supported OS. Or just wait for our test to complete and download the binary.

We always compile the released binaries strictly from the github sources.

[4roxx101]

Hmmm,.

why are my posts being removed?

[4roxx101]

will you remove this aswell??

Thank you, that's much better.
However not sure what you want from us ... We are not the owners of Cryptsy. File the freshdesk ticket and experience first hand the dealings with that exchange.
We've just hard forked so quite impossible that they are still using the old client as people would not be able to make withdrawals from there, but they can - at least small amounts as reported.

I suggest you talk to cryptsy,. i know you do not own cryptsy and i am in communication with them.

i expect you to remove the exchange from your op as stated in my pm to you,. they do not accept your coin. fact, pls remove from op so others dont fall into the same hole i did. pls dont not remove this aswell, prehaps if you delt with your emails alot of this would be kept from public view, therefore you would not need to keep removing posts. but thank you for taking time to deal with issues miners have mining your coin and trying to put them out there for others to trade with raising the profile of the coin.

[4roxx101]

will you remove this aswell??

Thank you, that's much better.
However not sure what you want from us ... We are not the owners of Cryptsy. File the freshdesk ticket and experience first hand the dealings with that exchange.
We've just hard forked so quite impossible that they are still using the old client as people would not be able to make withdrawals from there, but they can - at least small amounts as reported.

I suggest you talk to cryptsy,. i know you do not own cryptsy and i am in communication with them.

i expect you to remove the exchange from your op as stated in my pm to you,. they do not accept your coin. fact, pls remove from op so others dont fall into the same hole i did. pls dont not remove this aswell, prehaps if you delt with your emails alot of this would be kept from public view, therefore you would not need to keep removing posts. but thank you for taking time to deal with issues miners have mining your coin and trying to put them out there for others to trade with raising the profile of the coin.

Thanks for the PM, much appreciated popshot. good luck with Diamond, its a good coin

[popshot]

i expect you to remove the exchange from your op as stated in my pm to you,. they do not accept your coin. fact, pls remove from op so others dont fall into the same hole i did. pls dont not remove this aswell, prehaps if you delt with your emails alot of this would be kept from public view, therefore you would not need to keep removing posts. but thank you for taking time to deal with issues miners have mining your coin and trying to put them out there for others to trade with raising the profile of the coin.

Point taken.

I removed  your post as one of them contained a vulgar and offensive word and the other one was as if you were not capable of using edit function to correct a spelling mistake thus spamming with unnecessary post.
I've just replied to your email, and probably need to apologise that it took me 1h to do it because I'm at work? Sorry for offending you with keeping you waiting.

EDIT: ANN updated.