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

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: Mrbee on October 01, 2018, 12:32:21 PM

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?

if u interested in history of DMD Diamond
there is a book u can order about the first few years of DMD Diamond

https://www.amazon.com/Diamond-Phoenix-Crypto-Christopher-Thompson/dp/1977849806

shveicar

legendary

Activity: 1414

Merit: 1013

DMD info: https://diamond-info.github.io/

Quote from: Mrbee on October 01, 2018, 12:32:21 PM

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.

Mrbee

full member

Activity: 454

Merit: 100

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?

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: ?? on ??

Quote from: cryptonit on September 23, 2018, 04:47:57 AM

or use direct external swap providers: https://coinswitch.co/ or https://simpleswap.io/

How long will the swap last, @cryptonit?
I am very busy with my work this week, so I hope that the swap lasts more than one week and I will have chance to swap my coins.

swap BTC for DMD will be available as long as BTC exists
if BTC would disapear some other main coin will establish that u can swap into DMD

https://www.youtube.com/watch?v=QFSAWiTJsjc

Diamonds Are Forever - Shirley Bassey

Diamonds are forever, they are all I need to please me
They can stimulate and tease me
They won't leave in the night
I've no fear that they might desert me
Diamonds are forever, hold one up and then caress it
Touch it, stroke it and undress it
I can see ev'ry part, nothing hides in the heart to hurt me
I don't need love, for what good will love do me?
Diamonds never lie to me
For when love's gone, they'll lustre on
Diamonds are forever, sparkling round my little finger
Unlike men, the diamonds linger
Men are mere mortals who are not worth going to your grave for
I don't need love, for what good will love do me?
Diamonds never lie to me
For when love's gone, they'll lustre on
Diamonds are forever, forever, forever
Songwriter: John Barry

Nodeasy

jr. member

Activity: 112

Merit: 1

Reserved for translation into Chinese

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote

where can i get hands on DMD Diamond

most people have no issue get registered at https://bittrex.com/Market/Index?MarketName=BTC-DMD and use it
for people who cant get on bittrex there is https://www.livecoin.net/en/trade/index?currencyPair=DMD%2FBTC
and https://wallet.crypto-bridge.org/market/BRIDGE.DMD_BRIDGE.BTC

last but not least u can also get hand on DMD by use swap services
example here https://exchange.bit.diamonds/
or convert btc payouts of multipools (like nicehash) here https://multipool.bit.diamonds/
or use direct external swap providers: https://coinswitch.co/ or https://simpleswap.io/

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: Empty42 on September 19, 2018, 02:57:24 PM

everyone still having wallet problems?

there is actual no network problem
if u have a support case join our telegram or slack

telegram: https://t.me/DMDcoin
Slack: https://dmdcoin.slack.com/
Slack Invitation: https://bit.diamonds/contact.php (Send us a message via Contact Form)

Empty42

newbie

Activity: 50

Merit: 0

everyone still having wallet problems?

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: big_coins on September 19, 2018, 11:31:25 AM

the wallet on windows is very delicate.

sneeze on it and corrupt.

I think it should be made more robust especially for new users who are not computer geeks.

DMD wallet u see now is still a experimental software
every early adopter who join us already now accept this for the advantage to be part of it early

yes wallet software will improve a lot over the years
and what will hit mainstream in like 2020 will be total different as what we see now

big_coins

full member

Activity: 175

Merit: 100

the wallet on windows is very delicate.

sneeze on it and corrupt.

I think it should be made more robust especially for new users who are not computer geeks.

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: maxocoin on September 19, 2018, 07:46:21 AM

Yep, but that shouldn't be needed. I use that machine for more things and it needs to restart from time to time. If you follow the proper OS shutdown procedure you shouldn't break anything. Even Word asks you if you want to save stuff, if you have an unsaved document.

Yes, my walled is in the default folder as well.

Cheers
MC

we aware of it
for now please do as suggested close DMD wallet before u shutdown ur PC

its a issue that affect a lot coins not only DMD
mostly coins with POS/Masternode codebase

its an open issue we have on todo list
but its not a priority high one because
a easy workaround to avoid it exist
and also a easy fix if it happend exist

still we understand its a nasty little bug and he cant be ignorred forever

maxocoin

member

Activity: 102

Merit: 11

Quote from: pokeytex on September 19, 2018, 06:57:31 AM

Quote from: maxocoin on September 19, 2018, 06:10:35 AM

Quote from: shveicar on September 19, 2018, 12:19:31 AM

Quote from: maxocoin on September 18, 2018, 07:46:28 PM

Quote from: shveicar on September 18, 2018, 10:05:12 AM

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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=0

if 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

It could be that my particular configuration is more prone than others...

BUT that doesn't take away the fact that there is a Fault in the wallet's programming.

I know that this kind of things happen, specially if you are writing something to the disk and the system freezes or the power is cut, but it shouldn't happen if you close the system the right way.

It shouldn't happen because the OS notifies all the programs that it is going to shutdown and they should trap this notification for do their "clean up".

I think there is one of two options; or the wallet is not trapping this signal for "committing" the pending work and close the open files. Or this "cleanup" is taking too long.. Both are a programming issue.

As I said, I stake more coins on the same system and Diamond is the only that gets corrupted when I shutdown the system properly

MC

For what it is worth - I also run Windows 10 64 bit and never have a problem with the wallet corrupting. Whenever I get the update notice, I shut down all of my wallets, then I restart the computer in update mode. When I come back, I restart all my wallets with no issues whatsoever. Try that technique first before just choosing shutdown from the start button. Also, do you store your wallet.dat and other files on the C: drive or another location? Mine are saved to the default directory on the C: drive.

Yep, but that shouldn't be needed. I use that machine for more things and it needs to restart from time to time. If you follow the proper OS shutdown procedure you shouldn't break anything. Even Word asks you if you want to save stuff, if you have an unsaved document.

Yes, my walled is in the default folder as well.

Cheers
MC

pokeytex

legendary

Activity: 1504

Merit: 1002

Quote from: maxocoin on September 19, 2018, 06:10:35 AM

Quote from: shveicar on September 19, 2018, 12:19:31 AM

Quote from: maxocoin on September 18, 2018, 07:46:28 PM

Quote from: shveicar on September 18, 2018, 10:05:12 AM

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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=0

if 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

It could be that my particular configuration is more prone than others...

BUT that doesn't take away the fact that there is a Fault in the wallet's programming.

I know that this kind of things happen, specially if you are writing something to the disk and the system freezes or the power is cut, but it shouldn't happen if you close the system the right way.

It shouldn't happen because the OS notifies all the programs that it is going to shutdown and they should trap this notification for do their "clean up".

I think there is one of two options; or the wallet is not trapping this signal for "committing" the pending work and close the open files. Or this "cleanup" is taking too long.. Both are a programming issue.

As I said, I stake more coins on the same system and Diamond is the only that gets corrupted when I shutdown the system properly

MC

For what it is worth - I also run Windows 10 64 bit and never have a problem with the wallet corrupting. Whenever I get the update notice, I shut down all of my wallets, then I restart the computer in update mode. When I come back, I restart all my wallets with no issues whatsoever. Try that technique first before just choosing shutdown from the start button. Also, do you store your wallet.dat and other files on the C: drive or another location? Mine are saved to the default directory on the C: drive.

maxocoin

member

Activity: 102

Merit: 11

Quote from: shveicar on September 19, 2018, 12:19:31 AM

Quote from: maxocoin on September 18, 2018, 07:46:28 PM

Quote from: shveicar on September 18, 2018, 10:05:12 AM

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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=0

if 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

It could be that my particular configuration is more prone than others...

BUT that doesn't take away the fact that there is a Fault in the wallet's programming.

I know that this kind of things happen, specially if you are writing something to the disk and the system freezes or the power is cut, but it shouldn't happen if you close the system the right way.

It shouldn't happen because the OS notifies all the programs that it is going to shutdown and they should trap this notification for do their "clean up".

I think there is one of two options; or the wallet is not trapping this signal for "committing" the pending work and close the open files. Or this "cleanup" is taking too long.. Both are a programming issue.

As I said, I stake more coins on the same system and Diamond is the only that gets corrupted when I shutdown the system properly

MC

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: stillontop on September 19, 2018, 01:36:55 AM

Thank you for your continuous user support shveicar! What I am proposing is not something for DMD end users, but for the wallet developer.
It is possible to delay a Windows shutdown until the wallet has been shut down in a clean manner with the function I have posted.
Disabling operating system updates forever is not the best solution from a security perspective.

as the nature of DMD DIamond is technology agnostic

which means we will use the best technology that is able represent our coin rollout
fullfill our security and stability requirements
and increase cross blockchain interoperability

so dont expect that DMD Diamond wallet technology in 2 years is similar to now
maybe even much sooner there will be next technology leap

this corrupted blockchain at power outage is a limitation of actual codebase and will disapear once we make next evolution step

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

link to suggestion form: https://t.co/hwG8mkbdSe

stillontop

member

Activity: 134

Merit: 12

Quote from: shveicar on September 18, 2018, 10:05:12 AM

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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.

Thank you for your continuous user support shveicar! What I am proposing is not something for DMD end users, but for the wallet developer.
It is possible to delay a Windows shutdown until the wallet has been shut down in a clean manner with the function I have posted.
Disabling operating system updates forever is not the best solution from a security perspective.

shveicar

legendary

Activity: 1414

Merit: 1013

DMD info: https://diamond-info.github.io/

Quote from: maxocoin on September 18, 2018, 07:46:28 PM

Quote from: shveicar on September 18, 2018, 10:05:12 AM

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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=0

if 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

maxocoin

member

Activity: 102

Merit: 11

Quote from: shveicar on September 18, 2018, 10:05:12 AM

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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=0

shveicar

legendary

Activity: 1414

Merit: 1013

DMD info: https://diamond-info.github.io/

Quote from: stillontop on September 18, 2018, 08:15:10 AM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

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.

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