[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 782.

stoody

full member

Activity: 126

Merit: 100

Quote from: 4roxx101 on June 30, 2014, 06:08:10 AM

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

4roxx101

full member

Activity: 154

Merit: 100

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

full member

Activity: 126

Merit: 100

i think this is the right blockchain

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

4roxx101

full member

Activity: 154

Merit: 100

Quote from: popshot on June 30, 2014, 05:39:56 AM

Quote from: 4roxx101 on June 30, 2014, 05:36:04 AM

will you remove this aswell? Huh

?

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?

4roxx101

full member

Activity: 154

Merit: 100

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

popshot

hero member

Activity: 774

Merit: 554

CEO Diamond Foundation

Quote from: 4roxx101 on June 30, 2014, 05:36:04 AM

will you remove this aswell? Huh

?

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

full member

Activity: 154

Merit: 100

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? Huh

?

polanskiman

full member

Activity: 266

Merit: 100

Quote from: danbi on June 30, 2014, 04:49:40 AM

Quote from: polanskiman on June 30, 2014, 02:45:47 AM

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?

danbi

sr. member

Activity: 393

Merit: 250

Quote from: polanskiman on June 30, 2014, 02:45:47 AM

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

A Mac wallet will be available too.

istvandv

sr. member

Activity: 342

Merit: 250

Quote from: danbi on June 30, 2014, 02:32:37 AM

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

polanskiman

full member

Activity: 266

Merit: 100

Quote from: danbi on June 30, 2014, 02:32:37 AM

Quote from: polanskiman on June 29, 2014, 08:54:21 PM

Quote

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?

danbi

sr. member

Activity: 393

Merit: 250

Quote from: polanskiman on June 29, 2014, 08:54:21 PM

Quote

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

full member

Activity: 266

Merit: 100

Quote from: utahjohn on June 29, 2014, 09:36:17 PM

Quote from: polanskiman on June 29, 2014, 09:24:01 PM

Quote from: utahjohn on June 29, 2014, 10:22:34 AM

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://bitcointalksearch.org/topic/m.7569389) using an old backup (specially pre-dating PoS) of your wallet is not a good idea. I quote:

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.

utahjohn

hero member

Activity: 630

Merit: 500

Quote from: polanskiman on June 29, 2014, 09:24:01 PM

Quote from: utahjohn on June 29, 2014, 10:22:34 AM

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://bitcointalksearch.org/topic/m.7569389) using an old backup (specially pre-dating PoS) of your wallet is not a good idea. I quote:

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

Mxrider420z

sr. member

Activity: 620

Merit: 289

Ⓚ KORE TEAM Ⓚ ★ Portuguese/SPA

Anybody wanna trade DMD´s for a Watch Dogs game for pc, i have a spare one for trading

polanskiman

full member

Activity: 266

Merit: 100

Quote from: utahjohn on June 29, 2014, 10:22:34 AM

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://bitcointalksearch.org/topic/m.7569389) using an old backup (specially pre-dating PoS) of your wallet is not a good idea. I quote:

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.

polanskiman

full member

Activity: 266

Merit: 100

Quote from: pokeytex on June 29, 2014, 09:08:39 PM

Quote from: popshot on June 29, 2014, 01:45:56 PM

Quote from: pokeytex on June 29, 2014, 09:32:20 AM

I tried checking the trxID with no luck on the block explorer. I also submitted a ticket to Cryptsy. Just wondering if it is showing confirmed?
The weird part is that I did a small purchase of 32 dmds and was able to receive that with no problem. Do you think some of the diamonds on cryptsy are on the wrong fork? Would that be messing things up when you make a large purchase?

First of all first check as others instructed whether you are on the right chain by providing us with your latest checkpoint (type getcheckpoint in the console).

Cryptsy has most likely just one wallet for Diamond and the rest is managed by some smart accounting program. The 'coins' you see and trade on Cryptsy are not real 'coins' as these are just Cryptsy tokens. Only when you want to cash in from Cryptsy the 'real' coins are sent out. If people are able to get some coins out of Cryptsy then it should really doesn't matter if the amount was small or big as your transaction forms a transaction block consisting of many transactions and they have specific weight limits (basically the same rules apply to small and big).
The transaction you provided has been confirmed over 2k times so really not sure where it might have gone.

Having some info from Cryptsy would be helpful. But... lets wait for the wallet fix to see if that helps.

Current Checkpoint is:
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"

You are in the right block-chain.

polanskiman

full member

Activity: 266

Merit: 100

Interesting entry in the peers:

Code:

"addr" : "185.16.108.205:17771",
"services" : "00000000",
"lastsend" : 1404093925,
"lastrecv" : 0,
"conntime" : 1404093925,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0

Note the subver line.

This is very easily spoofed anyways if you change the right code lines in the source code and then compile the wallet yourself.

pokeytex

legendary

Activity: 1504

Merit: 1002

Quote from: popshot on June 29, 2014, 01:45:56 PM

Quote from: pokeytex on June 29, 2014, 09:32:20 AM

I tried checking the trxID with no luck on the block explorer. I also submitted a ticket to Cryptsy. Just wondering if it is showing confirmed?
The weird part is that I did a small purchase of 32 dmds and was able to receive that with no problem. Do you think some of the diamonds on cryptsy are on the wrong fork? Would that be messing things up when you make a large purchase?

First of all first check as others instructed whether you are on the right chain by providing us with your latest checkpoint (type getcheckpoint in the console).

Cryptsy has most likely just one wallet for Diamond and the rest is managed by some smart accounting program. The 'coins' you see and trade on Cryptsy are not real 'coins' as these are just Cryptsy tokens. Only when you want to cash in from Cryptsy the 'real' coins are sent out. If people are able to get some coins out of Cryptsy then it should really doesn't matter if the amount was small or big as your transaction forms a transaction block consisting of many transactions and they have specific weight limits (basically the same rules apply to small and big).
The transaction you provided has been confirmed over 2k times so really not sure where it might have gone.

Having some info from Cryptsy would be helpful. But... lets wait for the wallet fix to see if that helps.

Current Checkpoint is:
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"

polanskiman

full member

Activity: 266

Merit: 100

Quote from: murders10 on June 29, 2014, 02:20:29 PM

Quote from: kondiomir on June 29, 2014, 01:12:14 PM

Quote from: polanskiman on June 29, 2014, 10:07:57 AM

Quote from: utahjohn on June 29, 2014, 09:48:59 AM

Quote from: kondiomir on June 29, 2014, 08:42:09 AM

My wallet synced after deleting all in appdata ( w/o wallet.dat ) then downloaded blockchain and put it to appdata.
In conf file addnode=193.68.21.19

Than syncked after some time ... but I have another peoblem. Seems the PoS system not working well. Here is a shot:

Any ideas ?

go to debug console
type getcheckpoint
copy/past output and post it here to be verified you are on proper blockchain.

I am pretty sure he is on the right block-chain. He is using the correct node. His issue is pretty much what I am having and to this very moment I still have those questions marks. Those minted coins are part of the orphaned blocks that occured on 26.

Unfortunately after restart, the wallet cannot load anymore.

I think, we need new wallet too

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

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