Hi!
I have a problem with the synchronization of the my wallet (version 3.0.1.2) from October 8. What can be done to synchronize data for these 3 days?
check the number of the last block in your wallet. If it is different then https://chainz.cryptoid.info/dmd/ you will have to restart the blockchain Remove the old blocks as it is said here 18. Q: https://diamond-info.github.io/#q18 |
|
|
|
bla bla bla..
I wonder what your purpose is? You want to seem like an even bigger piece of shit than you really are? Only people like you don't respect other people's work and try to defile any good endeavor. |
|
|
|
I'm curious about this project and I wanna learn as much info about it as possible but I feel kind of overwhelmed by the 800+ pages here. Do you reckon it's necessary to read them before making any sorta decision?
It is never too late to read the published material before making a decision. But the basic information and the main links is on the first page of this section. |
|
|
|
Blocks corruption is only possible if the computer suddenly shuts down and synchronization is not yet complete. If the wallet sync has reached 100% then the sudden power off does not harm the blockchain. In other cases, any other causes of corruption are related to the automatic updates feature, which roughly terminates many system processes. The easiest way to protect against this is to use a properly configured computer with UPS and disabled automatic updates. For safety net, you can always create your archive with the folders blocks and chainstate and in case of damage to the blockchain, just to replace the data. Delete old folders and unpack new ones to their place. Then the re-sync process will only take a few minutes. Sorry but not... In my case, EVERY TIME I do a proper windows 10 shutdown, if I forgot to shutdown the wallet first, I get a wallet corruption error and it has to "re-verify" the whole 50 weeks. That is after been stacking for days (meaning, the wallet is fully synchronised) I have 3 other stacking wallets running on that computer and this is the only one affected... There is clearly something going on... Doesn't have windows something similar to the Unix signals that you can subscribe to and close all the files as soon you you get the "shooting down signal"? Actually thing jut got worst, since it last happened, every time I try to run it now, it aborts with the typical "Windows had encountered an error in this application..." Any one knows a way to fix that? Cheers MC
2018-09-19 00:53:38 DMD version v3.0.1.2-gcbcb549 (Tue, 9 Feb 2016 16:54:57 -0500)
2018-09-19 00:53:38 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2018-09-19 00:53:38 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-09-19 00:53:38 Default data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using config file C:\Users\user\AppData\Roaming\DMDV3\diamond.conf
2018-09-19 00:53:38 Using at most 125 connections (2048 file descriptors available)
2018-09-19 00:53:38 Using 0 threads for script verification
2018-09-19 00:53:38 Old backup deleted: "C:\Users\user\AppData\Roaming\DMDV3\backups\wallet.dat.2018-08-27-15-33"
2018-09-19 00:53:38 Using wallet wallet.dat
2018-09-19 00:53:38 init message: Verificando monedero...
2018-09-19 00:53:38 CDBEnv::Open: LogDir=C:\Users\user\AppData\Roaming\DMDV3\database ErrorFile=C:\Users\user\AppData\Roaming\DMDV3\db.log
2018-09-19 00:53:38 Bound to [::]:17771
2018-09-19 00:53:38 Bound to 0.0.0.0:17771
2018-09-19 00:53:38 init message: Cargando el Ãndice de bloques...
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\blocks\index
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\chainstate
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 LoadBlockIndexDB: last block file = 0
2018-09-19 00:53:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-09-19 00:53:38 Checking all blk files are present...
2018-09-19 00:53:38 LoadBlockIndexDB: Last shutdown was prepared: false
2018-09-19 00:53:38 LoadBlockIndexDB(): transaction index enabled
2018-09-19 00:53:38 Initializing databases...
2018-09-19 00:53:38 init message: Verificando bloques...
2018-09-19 00:53:38 block index 37ms
2018-09-19 00:53:38 Read 100 fee samples and 100 priority samples
2018-09-19 00:53:38 Read 47 fee samples and 32 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 init message: Cargando monedero...
2018-09-19 00:53:38 nFileVersion = 3000102
2018-09-19 00:53:38 Keys: 0 plaintext, 3073 encrypted, 3073 w/ metadata, 3073 total
2018-09-19 00:53:38 wallet 158ms
2018-09-19 00:53:38 Waiting for genesis block to be imported...
2018-09-19 00:53:38 Reindexing block file blk00000.dat...
2018-09-19 00:53:38 CheckBlock: block=0000029b550c0095513d9bb9dd14f88442573baca94d70e49018a510979c0f9b is proof of stake=0if you constantly have these problems, perhaps something with your system settings. Try using a different location for the DMDv3 folder. For example, another disk or removable device. 23. Q: Alternative way https://diamond-info.github.io/#q23-altway |
|
|
|
Blocks corruption is only possible if the computer suddenly shuts down and synchronization is not yet complete. If the wallet sync has reached 100% then the sudden power off does not harm the blockchain. In other cases, any other causes of corruption are related to the automatic updates feature, which roughly terminates many system processes. The easiest way to protect against this is to use a properly configured computer with UPS and disabled automatic updates. For safety net, you can always create your archive with the folders blocks and chainstate and in case of damage to the blockchain, just to replace the data. Delete old folders and unpack new ones to their place. Then the re-sync process will only take a few minutes. |
|
|
|
Apologies if I've asked this before...
How do you delete an orphan out of wallet?
The "wallet repair" thing doesn't seem to mention it.
The answer to your question here 26. Q: https://diamond-info.github.io/#q26 |
|
|
|
Wallet broke again. Forgot about Teusday update auto shutdown. Oops.
Except this time no message "would you like to repair..." re synch thing.
Splash screen just disappears after a couple of seconds.
No biggie, been there... done that....Um, could someone please kindly post a bootstrap/fix link?
I'm too lazy too find it tbh.Bear market and all..ho hum... (and this time I WILL bookmark, lol)
Thanx guys.
It is easier for you to use a ready-made blockchain to fast restore the health of the wallet. https://github.com/DMDcoin/Diamond/releases/download/v3.0.1.2/blockchain.zipAlthough it seems to me that it is easier to disable automatic updates. |
|
|
|
Where can I report a bug or find out if it has reported?
Looks like the Github page doesn't have issues activated.
My problem is that every time that I shut down Windows while I stacking, the DMD databases get corrupted and it needs a full index rebuild.
This takes the best part of one day if I'm lucky :-(
Cheers
Wallet works fine on different systems. This is personally tested on windows 10 and windows 7. Even a sudden power outage does not cause more damage to the base, as it was before. It is possible that something is wrong with your system or the enabled automatic update causes these damages. if you want your wallet to work all the time, the system must be set up and prepared for this. The setting must correspond to the mode as for a mining farm. if you have a desire for fast synchronization, you can use a ready-made archive with blockchain: https://github.com/DMDcoin/Diamond/releases/download/v3.0.1.2/blockchain.zipIn this case, full synchronization from scratch will take no more than 5 minutes. But if you want to provide a log file, you can join it to the support section on the #Slack channel |
|
|
|
Hey guys/gals, DMD is a very popular coin on https://cryptogiveaways.org! We have recently paid out the latest batch of DMD claims (1403) and zeroed the balance while we update some code While we update the code we would like to ask if any of the DMD community could check over the DMD details on the website (Visit https://cryptogiveaways.org and click the DMD logo for the details module). Let us know if you suggest any changes (Post them here) We are also building a new donation system for communities to help keep there coins active on the website and present with a balance. Our new donation address for DMD is dH7JSnDZ1FQS5FXmiXSnfEXXK6SqsTUKkM Hi. We recently updated the DMD logo. You can also replace it and on your website.  archive with logo here: https://diamond-info.github.io/files/TRANSPARENT_DMD_logo.zip |
|
|
|
Nonsense you say??
You got your ass
Pumped and dumped 3 times in the last two days.
Your Overvalued and your under performing
as any source of value..
Facts not fiction!!!
The diamond way..
The Titanic is sinking..and there’s not enough
Life Boats.. LMAO 😆
Why invest in a coin that you are so negative about and write here all the time the same thing? You're either crazy or you have a split personality. Sell all and go get treated. |
|
|
|
I seriously wish I knew! I have a local and external backup.
And I love this coin, for the record. This was the first coin I mined. However, I am not a cryptographer and just think it would be more helpful to understand why this happens for reasons other than Windows updates and why it can't be improved?
The only thing I can come up with is that when I mint X number of coins and before confirmed, there is an issue with the wallet. I do not check on this throughout the day, but every other day or so. My theory, (admitting that I could be way off) is that my orphaned mint is in limbo until I find out my wallet crashed; which may be 1-2 days later. I then restart my wallet, but the confirmations have passed me by... resulting in my dilemma of missing coins. (Gripping example below)
For example, lets say my wallet crashes. I last did a back up at my last mint reward. Lets say I had 10 DMD and received a reward of 1 DMD. (This is hypothetical of course). I then make a back up for my 11 DMD wallet. A week goes by and Mr Gates at Windows decides green is the new blue and pushes the "CHANGE EVERYTHING" button which causes hell for some of us who are foolish enough or forced to operate on his OS. I find out a day or two later that my computer restarted, wallet crashed, and begin the recovery process. Upon initially restoring my back up DMD wallet, it shows I have 11 DMD. These could be described as TOTAL or IMMATURE, but who cares, I still have my DMD! After syncing with the chain, I look at my DMD wallet again, maybe after a day or two, I only have 10 DMD. This situation has happened thrice.
Again, I don't know if what I am saying is completely stupid, an isolated issue, or something others have experienced. All of this comes from someone who doesn't know the inner workings, only what I've seen and learned. I am not blaming the team or the product, shit happens sometimes, but it would be nice to have a wallet that is able to restart itself or something? I remain invested in DMD and have no intention of leaving, but would like to just share what I've experienced (and hopefully receive some feedback to help me understand more).
Turn off automatic updates and set your computer to run continuously. After all, no one is banning you from installing the enterprise version of Windows 10 enterprise 2016 ltsb. This is time-tested system and does not have many extra modules and applications that live their lives and cause crashes. If you don't like Windows 10 and you are used to working with Windows7 you can install Vmware and run the Windows7 system inside Windows 10. But at the same time you still have to turn off automatic updates and configure the computer for continuous operation. P.s Be the master of your computer and ensure the privacy of your financial information. Do not open the door to it for Microsoft that installs and downloads any data from your PC when she wants and without your knowledge. |
|
|
|
Seems like a bug in the wallet...
I've got things moving in the right direction; I opened the wallet so I could access the dmd ion in bottom right corner, clicked on icon in bottom right to "open" the miner (although the gui was not visible, but the dmd icon was shown on the task bar).
I then hovered mouse over, the small preview window came up, and I right clicked on it. I had already tried restore, so I tried maximize and it popped up.
However, I can now only view gui in full screen. I had to move my dmd files back around to get the correct ones in place because I had been trying different back ups and was losing my mind thinking I was going to lose more dmd...
I thought I was good late last night as it was syncing AND I could see it!
I was ecstatic this morning, as my most recent (last crash) disappearance of dmd was back! (Although says my entire balance is Immature) It was stuck on 3 weeks behind and I thought that was odd because it had never taken that long to sync.
As of now, at night, it is still stuck on three weeks behind. I tried to restart, rescan, and recover transactions 2, but no luck. Files are not in typical AppData folder. Additional help would be much appreciated!
Make sure you are using the latest version of the wallet - v 3.0.1.2 https://github.com/DMDcoin/Diamond/releases/ Close the wallet and add in the file diamond.conf these lines. listen=1
logtimestamps=1
maxconnections=50
bantime=3600
discover=0
addnode=94.130.99.25
addnode=94.130.107.224
addnode=188.68.52.172
addnode=37.120.190.76
addnode=37.120.186.85
addnode=213.136.80.93
addnode=173.212.238.176
addnode=185.82.22.33
addnode=84.39.96.180
addnode=51.254.212.133
addnode=173.212.254.4 Clean the wallet folder with blocks and make a re-sync blockchain. 18. Q: https://diamond-info.github.io/#q18If I had to pick my top three reasons for being in volved with DMD, the HELP would be 1 (most, but at least the most important) Issues resolved, thank you (After the sync, I still lost the DMD that disappeared on my last crash, but I'd rather lose 10% than 100%)   Thank you How can you lose DMD if you have a backup of the file wallet.dat and private key from your address? it's impossible. But if you do not make backups and do not have a private key, you should know that this is the first step after the first start of the wallet. This is stated in the basics of working with a wallet 8. Q: https://diamond-info.github.io/#q8 |
|
|
|
Seems like a bug in the wallet...
I've got things moving in the right direction; I opened the wallet so I could access the dmd ion in bottom right corner, clicked on icon in bottom right to "open" the miner (although the gui was not visible, but the dmd icon was shown on the task bar).
I then hovered mouse over, the small preview window came up, and I right clicked on it. I had already tried restore, so I tried maximize and it popped up.
However, I can now only view gui in full screen. I had to move my dmd files back around to get the correct ones in place because I had been trying different back ups and was losing my mind thinking I was going to lose more dmd...
I thought I was good late last night as it was syncing AND I could see it!
I was ecstatic this morning, as my most recent (last crash) disappearance of dmd was back! (Although says my entire balance is Immature) It was stuck on 3 weeks behind and I thought that was odd because it had never taken that long to sync.
As of now, at night, it is still stuck on three weeks behind. I tried to restart, rescan, and recover transactions 2, but no luck. Files are not in typical AppData folder. Additional help would be much appreciated!
Make sure you are using the latest version of the wallet - v 3.0.1.2 https://github.com/DMDcoin/Diamond/releases/ Close the wallet and add in the file diamond.conf these lines. listen=1
logtimestamps=1
maxconnections=50
bantime=3600
discover=0
addnode=94.130.99.25
addnode=94.130.107.224
addnode=188.68.52.172
addnode=37.120.190.76
addnode=37.120.186.85
addnode=213.136.80.93
addnode=173.212.238.176
addnode=185.82.22.33
addnode=84.39.96.180
addnode=51.254.212.133
addnode=173.212.254.4 Clean the wallet folder with blocks and make a re-sync blockchain. 18. Q: https://diamond-info.github.io/#q18 |
|
|
|
|
The best way to kill a coin is to turn it into an ERC token.
Without its own blockchain, only one shell remains of the coin.
ETH continues to swell absorbing the slag in the form of numerous tokens.
I'm sorry that many people do not understand how it works and are ready to put their money in a bottomless bag.
|
|
|
|
Letting it "run" I just got an incoming transaction from February 2018... But I am unable to see the wallet at all. (I already tried #18 for the record) and salvage wallet, and upgrade wallet format - which is right before I received the transaction....?
There may be corruption of system files on the disk C:\. Start a new wallet via a shortcut with a different location and moving in the it your file wallet.dat 23. Q: Alternative way https://diamond-info.github.io/#q23-altwayLast time I had a problem with the wallet, this is what I did (#23) and it solved it. It crashed, I did #23, and has since crashed maybe 3 times until the one this week. The crash I experienced this week is when things changed. I re-did putting the shortcut in a folder as suggested, but am still experiencing the same issue. It seems like the wallet is running, I can see it in my process explorer, but I am unable to view the GUI. I can pull up the menu by right clicking on the dmd icon in bottom right corner, but cannot view the GUI. It does show me all menu options; Show/Hide, Send, Receive, etc. Any other idea? If this problem occurs after an automatic update, you should return the system to its original state and turn off automatic updates. |
|
|
|
Lol Btc goes up 700 US and diamond tards. Slide to 47k sats. Bahaha.. rewards down, every block.. V3 fails at all levels.. I bet you thought diamonds went up!! Look at the volume traded at Bitterex!! 11000 dollars at an exchange.lmao What a shit coin.. not even 2 btc.. Sad. What’s the point..  Can you imagine if this was a good coin?? The diff would be stupid hard.. Minting this shit is ridiculous. You guys can’t read a chart, it’s obvious.. Tomorrow’s volume 5000 US.lol The devs are just punks.. with pictures.. And bullshit.. I predict 25k sats by Sept 1.. And you know what that means.. You lose again. I lose again.. again. It’s like downhill skiing . Lol You have nothing more to do than write nonsense here? Sell all your coins and go to another coin, there you have long been waiting for. |
|
|
|
Letting it "run" I just got an incoming transaction from February 2018... But I am unable to see the wallet at all. (I already tried #18 for the record) and salvage wallet, and upgrade wallet format - which is right before I received the transaction....?
There may be corruption of system files on the disk C:\. Start a new wallet via a shortcut with a different location and moving in the it your file wallet.dat 23. Q: Alternative way https://diamond-info.github.io/#q23-altway |
|
|
|
There was an attack on the network and it caused a fork on the blockchain a few days ago. You might be on the wrong chain...
I was on the wrong chain for a couple days myself. Luckily I always have a copy of my data folder just two or three weeks old so it's easy for me to get back on track.
If everything else fails, just start syncing from the beginning with the latest wallet. And then, as soon as you're done, close the wallet and make a backup of your data folder!
What kind of attack? Details? Thanks. The attack brought him nothing but creating problems to synchronize wallets (decrease the number of connections for those who have not the necessary settings in the file diamond.conf). As a result, some wallets were on the wrong chain. But this is easily eliminated by removing the old blockchain and syncing from scratch using the backup archive. So are you saying , it was a sybil attack that was isolating some nodes which allow the attackers to utilize their own nodes to withhold blocks and/or headers, reject blocks and/or headers, purposefully fail to relay block’s and/or headers and so on to cause the fork. Were the necessary settings in the conf file , using addnode= to trusted nodes to block the attacks? or Was it something else? Thanks. The main method of protecting has been the addition of recording bantime and addnode. But it is much less felt the attack for wallets using an additional connection to the .onion nodes. These records have been repeatedly cited here. You can find them by scrolling this section a couple of pages back. |
|
|
|
Hi all, there has not been a payout for DMD cloud mining since 7 days ago. It is normally paid out daily, hence this cause for concern.
May I know what might be happening? Thank you
The pool owner is on a week-long vacation. Payments will be made upon his return, it will be tentatively next week. |
|
|
|
|
Show Posts
