Thank you so I have installed the new wallet, deleted the old data and did a full resync already and in the debug window I can see that the current block 135636 apparently up to date so how can I check if I am on the right blockchain or not ?
Check the number of the last block on the site https://chainz.cryptoid.info/dmd/And make sure the number matches the last block in your wallet. |
|
|
|
Hello
Help is needed
-Earlier the wallet was launched
-The wallet stacked
-But in the wrong chain
-All deleted
-Down load wallet from the beginning
-The wallet stacked
-But in the wrong chain
So what's next!
PS. Many others in the wrong chain
Br.
What others? There is only one old wallet left in the network and it receives no reward except for electricity consumption.  If you have a weak Internet connection or some other problems, add onions node to the file diamond.conf and launch TOR browser or Advor. Your wallet will work in bridge mode and get blocks from two networks (IPv4 and TOR). The list of trusted onion nodes can be found in the tab - all Masternodes. Click sort by time Active and select the longest running nodes.  |
|
|
|
It's good that you're going to work with cryptocurrency, cause it's money of future. But I can't find the information about what exactly currency you're going to work with?
DMD is a currency in itself. You can compare it's value with any existing systems, but the future distribution market will be focused on art and jewelry. |
|
|
|
the reward per block started to decline , which algorithm? will it be constant or will it stop at a certain level?
This will be a smooth reward reduction:  You can see other details in White Paper on the first page of this forum |
|
|
|
Hi, I need some advice.
I just purchased my first lot of DMD coins.. I got the wallet to fully sync and got my coins transferred to my wallet just fine. Stayed open the whole day.
Now today whenever I open my wallet it auto-exits as soon as it's finished loading. I can't even get the GUI to stay as it auto closes.
Not a virus problem like other wallets either I checked already (had the same issue with truckcoin being listed as a virus)
I'm at wits end here and can't figure this out. Really don't want to have to delete the blockchain and start over. Any advice?
Obviously you have used the default folder C:\Users\You Name\AppData\Roaming\DMDV3 and your system is not set to work around the clock. Just use a different location for the wallet: 23. Q: Alternative wayif you have any other problems you can report them in more detail on the #Slack channel |
|
|
|
Yes hallared, 3.0.1.0 final has been released a week before becoming a mandatory wallet update,
I think everybody had enough time to prepare for the protocol change.
I am also wondering what happens to outdated master nodes. The reward is already reduced a tiny bit.
Old wallets will no longer be able to function properly and their owners will have to upgrade to the new version. |
|
|
|
Thanks for the quick reply. I have done everything you suggest and I'm fully synced up to the latest block. I had also deleted all files from the Diamond folder, except wallet.dat.
But, when I closed the wallet, I got the following message: "Error: A fatal internal error occured, see debug.log for details". Here's the relevant part:
2018-04-07 10:47:35 *** System error while flushing: CDB : Error -30974, can't open database
2018-04-07 10:51:24 CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2018-04-07 10:51:24 Shutdown: done
What do I do now?
if you have often similar problems then recommend using a different folder location for your wallet files. Example of starting the wallet with the DMD folder next to the executable diamond-qt.exe 23. Q: Alternative way |
|
|
|
~
i call such stuff bot zombies
started scripts running and running and running even if their initial usecase is long gone
~
we need bot zombie hunters in the internet
We should manage the official ANN topic of Diamond project somehow or report to forum moderators to prevent any potentially massive abusements from spammers, in particular spamming threads from bot zombies. Bot zombies, strange term which I learn from you, cryptonit. By the way, what I know is Diamond only has signature campaign for Senior Member and above. Have you had plans to expand a litlle bit more for Diamond supporters, such as for Member ranks and above to join? Thanks. We have several options for signatures. You can see it here: https://diamond-info.github.io/sig.html |
|
|
|
there is a problem with masternode rewards this new patch.
some days my nodes are getting just 1 reward.
i have spreadsheet of daily rewards since live.
something is very wrong.
I didn't notice any difference in the reward for MN after the wallet update. If you have more evidence than a mere allegation of mythical problems, go to the #Slack channel and show your screenshots. |
|
|
|
You’ve got a great roadmap and the team itself. I’m pretty sure you’ll come through with flying colors! But how your currency fundamentally differs from others is still kind of unclear to me.
I will give you the most basic differences that you could better understand what is at stake. 1. DMD has almost zero power consumption compared to other coins. If your wallet is used for POS mining on your desktop computer, which is constantly turned on, then you will not even notice these energy costs. 2. The DMD has a deflationary system in which income is gradually reduced to a minimum value (but will never be equal to 0) which will provide compensation to all nodes and participants of the POS network. At the same time, unlike Bitcoin, all lost coins will gradually return to the network. Thus, the number of coins in the system will never be lower than the set value of 4.38 million, but will never and exceed it. |
|
|
|
I have problems to sync. My wallet is is struck at block 126230 (3 hours behind). It looks I'm not the only one. Some of the peers I'm connected to are on that block, while others are on 126834. What can I do?
exact same issue here, same block stuck on 126230. and all my coins currently immature. it would appear we are on wrong chain, I have stakes that are minted with around 50+ confirmations that I suspect are orphans. reinstalling didn't fix. (latest version wallet) answer to Q18 is solving this make sure u delete peers.dat too https://diamond-info.github.io/#q18once we after block 130000 this issues will be solved the new 3.0.1.0 wallets will then stop to talk with old wallets please everyone be aware that at latest on april 6th u MUST update ur wallet to the latest one 3.0.1.0 all old wallets will at block 130000 lose connection to mainnet Thanks a lot. It takes a hell to download everything. Is there a bootstrap we can download? There is also an even easier way to save all your wallet files and the entire working blockchain, this is stated here: 8. Q: Step7but to make a blockchain backup u need to be on a save sync correct chain first so this is not helping u if u have issues already Yes, of course. backups are always done when you have completed all the settings and your wallet is ready to go. |
|
|
|
I have problems to sync. My wallet is is struck at block 126230 (3 hours behind). It looks I'm not the only one. Some of the peers I'm connected to are on that block, while others are on 126834. What can I do?
exact same issue here, same block stuck on 126230. and all my coins currently immature. it would appear we are on wrong chain, I have stakes that are minted with around 50+ confirmations that I suspect are orphans. reinstalling didn't fix. (latest version wallet) answer to Q18 is solving this make sure u delete peers.dat too https://diamond-info.github.io/#q18once we after block 130000 this issues will be solved the new 3.0.1.0 wallets will then stop to talk with old wallets please everyone be aware that at latest on april 6th u MUST update ur wallet to the latest one 3.0.1.0 all old wallets will at block 130000 lose connection to mainnet Thanks a lot. It takes a hell to download everything. Is there a bootstrap we can download? There is also an even easier way to save all your wallet files and the entire working blockchain, this is stated here: 8. Q: Step7 |
|
|
|
The main chain (including the wallets Bittrix and Livecoin) has not experienced a fork.
This happened only with some wallets on the network.
Simple resync solves this problem.
The reason for the incident is that one or more wallets began to distribute the wrong blocks.
Given that the DMD network consists of two parts (IPv4 and TOR network) between them should be closely connected.
Not all users use the add TOR nodes to a file diamond.conf, therefore, in case of violation of exchanges between the two systems, such an effect is possible.
Thx shveicar, interesting info. i tried to search some extra info about TOR nodes, but didn't find any, there is a list of TOR nodes to add to the configuration file ? cheers. For get a list of TOR nodes, you need to run the wallet, wait 100% sync and go to the all Masternodes tab. Click on the Active tab and select the long-running TOR nodes from the list.  Open your diamond file.conf and put these nodes in the list: listen=1
maxconnections=25
port=17771
onion=127.0.0.1:9550
addnode=diamond2a36tghig.onion
addnode=diamond7sgqpcbsy.onion
addnode=diamond5vyabnrkp.onion
addnode=diamond6w3aqwkxs.onion
addnode=zlwhhhfwblhep62x.onion
addnode=scapxcqswhmbxzsh.onion
addnode=ya6qpdzaxkdqzhz3.onion
You will only need to deposit 5 to 10 reliable nodes to be sure that your wallet has a good exchange with reliable TOR nodes. In addition, you will need the program AdvOR or TOR browser for start the TOR network with a port 9550 or any other port that matches what is specified in the file diamond.conf. To make sure your wallet is really connected to the TOR network, after 100% sync, go to the Menu -> Tools -> Peers list tab and you will see .onion nodes in your shared list  |
|
|
|
|
The main chain (including the wallets Bittrix and Livecoin) has not experienced a fork.
This happened only with some wallets on the network.
Simple resync solves this problem.
The reason for the incident is that one or more wallets began to distribute the wrong blocks.
Given that the DMD network consists of two parts (IPv4 and TOR network) between them should be closely connected.
Not all users use the add TOR nodes to a file diamond.conf, therefore, in case of violation of exchanges between the two systems, such an effect is possible.
|
|
|
|
Hii anyone here can help me ..my wallet stuck at 8 hour sync for long time ..I not found answer on diamond info GitHub about this stuck..do I need to delete back in my wallet DMDV3 except diamond.conf, masternode.conf wallet.dat and folder backups .or just repair wallet reindex block ??
Yes, delete all the files as described here: 18. Q: https://diamond-info.github.io/#q18and re-sync your wallet |
|
|
|
I respect old coins, but only those that really have development. If you look at the NXS with a clear look (not filled by nonsense about space and about the distant worlds full of wealth) then you will see this:  I know one thing. if people have plans to conquer space and are not able to correct the simplest mistakes, then I would never buy a ticket for such a space ship  But keep playing this "pumps and dumps" game. I like making money on the it  |
|
|
|
Masternode holders are the ones who have invested the most, and who also have the most to lose. I think it makes perfect sense the have masternode holder voting.
If you think that is "centralised", then crypto itself is pretty centralised. Large holders can influence the price a lot more than small ones...
Well, maybe people think that because it is centralized, with a z. I'm not sure who are you trying to sell that smoke to, as if all crypto were based off PoS and Masternodes. PoS is even more centralized as BTC core and cash with Bitmain level of huge ASIC farms, every bit like it, only PoW is more secure than PoS, and at the same time masternodes are every bit like a pyramid scheme, interesting that while a coin like ETH hasn't found the way to make a move towards a fair PoS scheme, DMD has both PoS and Masternodes. But yeah, you just keep selling that smoke. POW is more secure than POS? What kind of nonsense are you talking about. A bunch of hungry miners consuming on their farms hundreds of kilowatts of electricity and jumping from pool to pool for quick profits, according to your theory very reliable system supporting the network. You think Masternode is a pyramid? - the system allows you to make quick transactions and has several unique features (voting and auxiliary functions for easy wallets) - more ignorant statements I have not heard. What did you forget in the DMD? Find yourself any other coin for criticism and wait for your wealth. |
|
|
|
|
In front of us we have a lot of interesting things, so DMD is still an attractive asset for investment.
|
|
|
|
We pure lend money for this guy, for FREE, for about three month, until he pay us our own money back, with no interest at all. This is his idea of sustaining the dmd. He is a dmd core member, the dmd website points to his website, so i blame dmd coin. As soon as i got my money back, lended for free, i will never touch that coin again.
I can understand your disappointment, but Cloud mining is not a pyramid that constantly grows to the point of collapse. This is a long-term project aimed at maintaining the market. Those investors who regularly receive payments to the DMD can also increase their assets through POS minting. Therefore, changes in the rules for Multipool shares are caused by the need to prevent problems for this service by eliminating excess profits for owners of a large number of shares. |
|
|
|
windows qt wallet always crashing, any idea why this is happening?
I do not know why some users on Windows 10 have such problems. I tested my wallet for several days and have never seen such a problem. I used the enterprise version of Windows 10 (windows 10 enterprise 2016 ltsb x86 9058173) which removed unnecessary modules and the app store. In addition, I disabled all automatic updates and system shutdown hard drives and hibernate. Exactly the same settings I did in Windows 7. All these settings are necessary for the continuous operation of the computer with the DMD wallet in POS mode. I also turned off the power to check the wallet for damage to the blocks, but I never got this effect in the new version 3.0.0.15. Therefore, please prepare your computers for continuous operation (check system services configuration). If you see any problems after that, go to the #Slack channel. We have opened a section #support where you can place the logs from the wallet. Without it we can only of the guess what was going on. |
|
|
|
|
Show Posts
