|
Title: Bitcoin QT not synching Post by: Gabriel1918 on November 28, 2015, 09:11:05 PM Hi guys. Apologies if this is repetitive but I've gone through the relevant thrads I could find and haven't been able to find a solution. Your help is appreciated.
I bought some coins and have been unable to view them in my wallet due to Bitcoin QT never successfully loading the blockchain despite countless attempts over the last three weeks. I'm brand new to BTC so know nothing technical about it other than what I've tried so far. I'm running windows 7 starter, 2.0GHz with about 57Gb hard drive space: 1. https://blockchain.info/it/wallet/import-wallet Tried dragging wallet.dat file here based on my reading of an old thread on here but 'unexpected end of file' or some such error repeatedly comes up 2. Tried deleting blockchain and all other files (except wallet.dat) numerous times. Seems to continually stick at either 2 years 26 weeks or 1 year 51 weeks. Restarts involve QT reindexing the downloaded files due to them being 'corrupted' 3. Have run extended memory checks on my PC and memory is fine Thank you for any suggestions for the simplest solution to a. checking that the coins I bought are safe, and b. having a useable wallet Title: Re: Bitcoin QT not synching Post by: achow101 on November 28, 2015, 09:22:08 PM As long as you have the wallet.dat file your coins will always be safe.
Can you post the debug.log file here? There isn't any sensitive information in that and it will help us diagnose your problem. I suspect that it may have something to do with an antiviurs. Check that your antivirus software has the data directory as an exception. Title: Re: Bitcoin QT not synching Post by: VirosaGITS on November 28, 2015, 10:21:02 PM Hi guys. Apologies if this is repetitive but I've gone through the relevant thrads I could find and haven't been able to find a solution. Your help is appreciated. I bought some coins and have been unable to view them in my wallet due to Bitcoin QT never successfully loading the blockchain despite countless attempts over the last three weeks. I'm brand new to BTC so know nothing technical about it other than what I've tried so far. I'm running windows 7 starter, 2.0GHz with about 57Gb hard drive space: 1. https://blockchain.info/it/wallet/import-wallet Tried dragging wallet.dat file here based on my reading of an old thread on here but 'unexpected end of file' or some such error repeatedly comes up 2. Tried deleting blockchain and all other files (except wallet.dat) numerous times. Seems to continually stick at either 2 years 26 weeks or 1 year 51 weeks. Restarts involve QT reindexing the downloaded files due to them being 'corrupted' 3. Have run extended memory checks on my PC and memory is fine Thank you for any suggestions for the simplest solution to a. checking that the coins I bought are safe, and b. having a useable wallet A bit, you're mostly in the same situation of that thread just under yours; https://bitcointalk.org/index.php?topic=122198.0 Also i'm not sure you actually have enough space. I dont know if it need to unpack and need some swap file space but the block chain size is about 50gb by itself now. And the process of syncing can take many days of uninterrupted work. So go ahead and check that thread, it contain a work around, one you might not even need to go through by just getting a SPV wallet, unless you also went and sent money to one of your addresses without syncing first. TLDR: Get a SPV Wallet. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 28, 2015, 10:49:41 PM Thanks guys. Yes, I did send coins to the wallet without synching first. I posted on the thread you linked to but my post was deleted by a moderator, who told me to start a new thread as that one apparently contains out of date info.
Not sure how much of the debug log you want me to post knightdk but here's a bit: 2015-11-28 16:34:24 ERROR: AcceptToMemoryPool: non-final 2015-11-28 16:34:24 ERROR: AcceptToMemoryPool: non-final 2015-11-28 16:34:24 ERROR: AcceptToMemoryPool: non-final 2015-11-28 16:34:32 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-28 16:34:35 ERROR: AcceptToMemoryPool: non-final If you mean post all of it then I will but it's long. have had a look at my AVG anti-virus but no success in listing the file as an exception. I'm not too technical on computers so any help with that is appreciated. Title: Re: Bitcoin QT not synching Post by: achow101 on November 28, 2015, 10:55:22 PM Thanks guys. Yes, I did send coins to the wallet without synching first. I posted on the thread you linked to but my post was deleted by a moderator, who told me to start a new thread as that one apparently contains out of date info. We will need all of it. Put it in the code brackets.Not sure how much of the debug log you want me to post knightdk but here's a bit: 2015-11-28 16:34:24 ERROR: AcceptToMemoryPool: non-final 2015-11-28 16:34:24 ERROR: AcceptToMemoryPool: non-final 2015-11-28 16:34:24 ERROR: AcceptToMemoryPool: non-final 2015-11-28 16:34:32 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-28 16:34:35 ERROR: AcceptToMemoryPool: non-final If you mean post all of it then I will but it's long. have had a look at my AVG anti-virus but no success in listing the file as an exception. I'm not too technical on computers so any help with that is appreciated. On AVG (at least the version that I have) you click the options arrow and select Advanced Settings. Then go to the Exceptions option and click add exception. Then just follow the instructions and add the entire data directory as an exception. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 29, 2015, 12:20:36 AM Thanks knightdk. I've added the bitcoin data folder to the exceptions list in AVG. How do I post the debug log in the code brackets? I tried just pasting it into this post window but it doesn't work.
Title: Re: Bitcoin QT not synching Post by: achow101 on November 29, 2015, 12:28:03 AM Thanks knightdk. I've added the bitcoin data folder to the exceptions list in AVG. How do I post the debug log in the code brackets? I tried just pasting it into this post window but it doesn't work. paste it into the post window and then highlight it all and click the button with the pound symbol (#) above the emojis.Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 29, 2015, 01:05:24 AM the debug log is 530 705 lines long from just the last 24hrs. Won't paste into the window. I can wait to see if the AVG exception change has worked...
Title: Re: Bitcoin QT not synching Post by: achow101 on November 29, 2015, 01:07:35 AM the debug log is 530 705 lines long from just the last 24hrs. Won't paste into the window. I can wait to see if the AVG exception change has worked... Then just put it in http://pastebin.com/ and give us the link. Or you can give us a chunk from the bottom which includes all of the last time you tried to start it.Title: Re: Bitcoin QT not synching Post by: ranochigo on November 29, 2015, 03:46:07 AM 1. https://blockchain.info/it/wallet/import-wallet Tried dragging wallet.dat file here based on my reading of an old thread on here but 'unexpected end of file' or some such error repeatedly comes up This page no longer works.Make sure to have a wallet.dat backup before doing anything. Try knightdk's method, if it gets stuck again, try looking into your task manager and see if your disk usage and/or CPU usage is high. If it is, the computer is validating the blocks and it can take sometime. Reindexing removes the corruption and it is mostly due to the improper shutdown of Bitcoin Core. When it shuts down, make sure the windows disappear before shutting your computer down. Otherwise, in your Bitcoin Core UI, go to help>debug window>network traffic and ensure that there is some incoming traffic. Next, go to peers and ensure that at least one of them have a sync height that is higher than you. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 29, 2015, 02:23:15 PM Thanks guys. I appreciate the help. I'll do all that and get back to you. Have shut down QT correctly each time. I just restarted the computer now in case AVG needed a restart to configure the exceptions etc. QT on startup once again says 'corrupted block database detected' so it's reindexing again.
Title: Re: Bitcoin QT not synching Post by: achow101 on November 29, 2015, 03:28:41 PM Thanks guys. I appreciate the help. I'll do all that and get back to you. Have shut down QT correctly each time. I just restarted the computer now in case AVG needed a restart to configure the exceptions etc. QT on startup once again says 'corrupted block database detected' so it's reindexing again. Can you give us the debug.log?Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 29, 2015, 11:35:25 PM Ok, here's a chunk of the debug log where things appear to have started to go wrong. It now appears to be stuck at 2 years 0 months. Still receiving traffic with 8 connections. The debug log just repeats the last messages all the way to the bottom.
2015-11-29 18:13:48 UpdateTip: new best=000000000000000628e6c7baa7cd12cc2fc4ba70ffeb09d9f1e57ec3a3ff3c40 height=271978 log2_work=74.302604 tx=28086710 date=2013-11-28 17:11:53 progress=0.129911 cache=665.7MiB(1565692tx) 2015-11-29 18:13:48 LoadExternalBlockFile: Processing out of order child 000000000000000222435e115ca3f8e26d23464d8e21b0230b9459e17ffe5575 of 000000000000000628e6c7baa7cd12cc2fc4ba70ffeb09d9f1e57ec3a3ff3c40 2015-11-29 18:13:49 UpdateTip: new best=000000000000000222435e115ca3f8e26d23464d8e21b0230b9459e17ffe5575 height=271979 log2_work=74.302766 tx=28087955 date=2013-11-28 17:16:51 progress=0.129916 cache=665.8MiB(1565985tx) 2015-11-29 18:14:20 LoadExternalBlockFile: Deserialize or I/O error - std::bad_alloc 2015-11-29 18:14:26 Loaded 162 blocks from external file in 82626ms 2015-11-29 18:14:26 Reindexing finished 2015-11-29 18:14:28 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:28 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:28 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:40 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:40 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:41 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:43 nActualTimespan = 1042157 before bounds 2015-11-29 18:14:43 GetNextWorkRequired RETARGET 2015-11-29 18:14:43 params.nPowTargetTimespan = 1209600 nActualTimespan = 1042157 2015-11-29 18:14:43 Before: 19070bfb 00000000000000070bfb00000000000000000000000000000000000000000000 2015-11-29 18:14:43 After: 19061242 0000000000000006124221c630a74eb92fd741b85fca40e852c970db51f963da 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:14:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:54 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:58 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:58 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:14:59 nActualTimespan = 942018 before bounds 2015-11-29 18:14:59 GetNextWorkRequired RETARGET 2015-11-29 18:14:59 params.nPowTargetTimespan = 1209600 nActualTimespan = 942018 2015-11-29 18:14:59 Before: 19061242 0000000000000006124200000000000000000000000000000000000000000000 2015-11-29 18:14:59 After: 1904ba6e 0000000000000004ba6ea7333333333333333333333333333333333333333333 2015-11-29 18:15:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:06 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:07 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:07 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:07 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:15:11 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:12 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:19 ERROR: ConnectBlock(): inputs missing/spent 2015-11-29 18:15:19 Misbehaving: 122.57.96.16:8333 (0 -> 100) BAN THRESHOLD EXCEEDED 2015-11-29 18:15:19 InvalidChainFound: invalid block=000000000000000676058116a2878c2540d78d5b5cf959ae1ca935d5d8f7438b height=271980 log2_work=74.302929 date=2013-11-28 17:17:31 2015-11-29 18:15:19 InvalidChainFound: current best=000000000000000222435e115ca3f8e26d23464d8e21b0230b9459e17ffe5575 height=271979 log2_work=74.302766 date=2013-11-28 17:16:51 2015-11-29 18:15:19 ERROR: ConnectTip(): ConnectBlock 000000000000000676058116a2878c2540d78d5b5cf959ae1ca935d5d8f7438b failed 2015-11-29 18:15:19 InvalidChainFound: invalid block=000000000000000676058116a2878c2540d78d5b5cf959ae1ca935d5d8f7438b height=271980 log2_work=74.302929 date=2013-11-28 17:17:31 2015-11-29 18:15:19 InvalidChainFound: current best=000000000000000222435e115ca3f8e26d23464d8e21b0230b9459e17ffe5575 height=271979 log2_work=74.302766 date=2013-11-28 17:16:51 2015-11-29 18:15:20 receive version message: /Satoshi:0.11.1/: version 70002, blocks=385921, us=80.189.148.209:49480, peer=9 2015-11-29 18:15:20 Added time data, samples 10, offset +18 (+0 minutes) 2015-11-29 18:15:24 nActualTimespan = 930412 before bounds 2015-11-29 18:15:24 GetNextWorkRequired RETARGET 2015-11-29 18:15:24 params.nPowTargetTimespan = 1209600 nActualTimespan = 930412 2015-11-29 18:15:24 Before: 1904ba6e 0000000000000004ba6e00000000000000000000000000000000000000000000 2015-11-29 18:15:24 After: 1903a30c 0000000000000003a30cd9111111111111111111111111111111111111111111 2015-11-29 18:15:27 ERROR: AcceptBlockHeader: block is marked invalid 2015-11-29 18:15:27 ERROR: invalid header received 2015-11-29 18:15:27 ProcessMessages(headers, 162003 bytes) FAILED peer=1 2015-11-29 18:15:29 nActualTimespan = 1007027 before bounds 2015-11-29 18:15:29 GetNextWorkRequired RETARGET 2015-11-29 18:15:29 params.nPowTargetTimespan = 1209600 nActualTimespan = 1007027 2015-11-29 18:15:29 Before: 1903a30c 0000000000000003a30c00000000000000000000000000000000000000000000 2015-11-29 18:15:29 After: 1903071f 0000000000000003071f9b4cfd585e0e696f1f7a80308b91419ca252adb363be 2015-11-29 18:15:32 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:34 nActualTimespan = 958789 before bounds 2015-11-29 18:15:34 GetNextWorkRequired RETARGET 2015-11-29 18:15:34 params.nPowTargetTimespan = 1209600 nActualTimespan = 958789 2015-11-29 18:15:34 Before: 1903071f 0000000000000003071f00000000000000000000000000000000000000000000 2015-11-29 18:15:34 After: 19026666 00000000000000026666428d5af7d19f3c15e3805a27c49e6c08e2b04d26f491 2015-11-29 18:15:36 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:38 nActualTimespan = 986691 before bounds 2015-11-29 18:15:38 GetNextWorkRequired RETARGET 2015-11-29 18:15:38 params.nPowTargetTimespan = 1209600 nActualTimespan = 986691 2015-11-29 18:15:38 Before: 19026666 0000000000000002666600000000000000000000000000000000000000000000 2015-11-29 18:15:38 After: 1901f52c 0000000000000001f52cd3c5cf902c35f6929c5cf902c35f6929c5cf902c35f6 2015-11-29 18:15:44 nActualTimespan = 1012318 before bounds 2015-11-29 18:15:44 GetNextWorkRequired RETARGET 2015-11-29 18:15:44 params.nPowTargetTimespan = 1209600 nActualTimespan = 1012318 2015-11-29 18:15:44 Before: 1901f52c 0000000000000001f52c00000000000000000000000000000000000000000000 2015-11-29 18:15:44 After: 1901a36e 0000000000000001a36eab3788cde233788cde233788cde233788cde233788cd 2015-11-29 18:15:47 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:48 nActualTimespan = 1013191 before bounds 2015-11-29 18:15:48 GetNextWorkRequired RETARGET 2015-11-29 18:15:48 params.nPowTargetTimespan = 1209600 nActualTimespan = 1013191 2015-11-29 18:15:48 Before: 1901a36e 0000000000000001a36e00000000000000000000000000000000000000000000 2015-11-29 18:15:48 After: 19015f53 00000000000000015f532105e7d5f4d6c4e3c5b3d2b4a2c1a391b092809f816f 2015-11-29 18:15:50 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:50 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:51 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:51 nActualTimespan = 992091 before bounds 2015-11-29 18:15:51 GetNextWorkRequired RETARGET 2015-11-29 18:15:51 params.nPowTargetTimespan = 1209600 nActualTimespan = 992091 2015-11-29 18:15:51 Before: 19015f53 00000000000000015f5300000000000000000000000000000000000000000000 2015-11-29 18:15:51 After: 19012026 00000000000000012026437b348014ce19ae67b348014ce19ae67b348014ce19 2015-11-29 18:15:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:15:59 nActualTimespan = 1085950 before bounds 2015-11-29 18:15:59 GetNextWorkRequired RETARGET 2015-11-29 18:15:59 params.nPowTargetTimespan = 1209600 nActualTimespan = 1085950 2015-11-29 18:15:59 Before: 19012026 0000000000000001202600000000000000000000000000000000000000000000 2015-11-29 18:15:59 After: 190102b1 000000000000000102b15a84bda12f684bda12f684bda12f684bda12f684bda1 2015-11-29 18:16:00 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:01 nActualTimespan = 1026813 before bounds 2015-11-29 18:16:01 GetNextWorkRequired RETARGET 2015-11-29 18:16:01 params.nPowTargetTimespan = 1209600 nActualTimespan = 1026813 2015-11-29 18:16:01 Before: 190102b1 000000000000000102b100000000000000000000000000000000000000000000 2015-11-29 18:16:01 After: 1900db99 0000000000000000db99809e79e79e79e79e79e79e79e79e79e79e79e79e79e7 2015-11-29 18:16:03 nActualTimespan = 989657 before bounds 2015-11-29 18:16:03 GetNextWorkRequired RETARGET 2015-11-29 18:16:03 params.nPowTargetTimespan = 1209600 nActualTimespan = 989657 2015-11-29 18:16:03 Before: 1900db99 0000000000000000db9900000000000000000000000000000000000000000000 2015-11-29 18:16:03 After: 1900b3aa 0000000000000000b3aaff0fedcba987654320fedcba987654320fedcba98765 2015-11-29 18:16:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:05 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:06 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:06 nActualTimespan = 1060716 before bounds 2015-11-29 18:16:06 GetNextWorkRequired RETARGET 2015-11-29 18:16:06 params.nPowTargetTimespan = 1209600 nActualTimespan = 1060716 2015-11-29 18:16:06 Before: 1900b3aa 0000000000000000b3aa00000000000000000000000000000000000000000000 2015-11-29 18:16:06 After: 19009d8c 00000000000000009d8cd05c5291f5ec2b8f85c5291f5ec2b8f85c5291f5ec2b 2015-11-29 18:16:08 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:16:08 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:16:08 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:08 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:16:08 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:11 nActualTimespan = 1055108 before bounds 2015-11-29 18:16:11 GetNextWorkRequired RETARGET 2015-11-29 18:16:11 params.nPowTargetTimespan = 1209600 nActualTimespan = 1055108 2015-11-29 18:16:11 Before: 19009d8c 00000000000000009d8c00000000000000000000000000000000000000000000 2015-11-29 18:16:11 After: 1900896c 0000000000000000896cbbe7f1b24e5818b4be7f1b24e5818b4be7f1b24e5818 2015-11-29 18:16:11 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:14 nActualTimespan = 1093121 before bounds 2015-11-29 18:16:14 GetNextWorkRequired RETARGET 2015-11-29 18:16:14 params.nPowTargetTimespan = 1209600 nActualTimespan = 1093121 2015-11-29 18:16:14 Before: 1900896c 0000000000000000896c00000000000000000000000000000000000000000000 2015-11-29 18:16:14 After: 187c3053 00000000000000007c30534c1f6ca174c1f6ca174c1f6ca174c1f6ca174c1f6c 2015-11-29 18:16:17 nActualTimespan = 1024233 before bounds 2015-11-29 18:16:17 GetNextWorkRequired RETARGET 2015-11-29 18:16:17 params.nPowTargetTimespan = 1209600 nActualTimespan = 1024233 2015-11-29 18:16:17 Before: 187c3053 00000000000000007c3053000000000000000000000000000000000000000000 2015-11-29 18:16:17 After: 18692842 0000000000000000692842cbcccccccccccccccccccccccccccccccccccccccc 2015-11-29 18:16:18 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:19 nActualTimespan = 1075761 before bounds 2015-11-29 18:16:19 GetNextWorkRequired RETARGET 2015-11-29 18:16:19 params.nPowTargetTimespan = 1209600 nActualTimespan = 1075761 2015-11-29 18:16:19 Before: 18692842 0000000000000000692842000000000000000000000000000000000000000000 2015-11-29 18:16:19 After: 185d859a 00000000000000005d859a77fd130463796ac9dfd130463796ac9dfd13046379 2015-11-29 18:16:20 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:21 nActualTimespan = 1056315 before bounds 2015-11-29 18:16:21 GetNextWorkRequired RETARGET 2015-11-29 18:16:21 params.nPowTargetTimespan = 1209600 nActualTimespan = 1056315 2015-11-29 18:16:21 Before: 185d859a 00000000000000005d859a000000000000000000000000000000000000000000 2015-11-29 18:16:21 After: 1851aba2 000000000000000051aba20b1451451451451451451451451451451451451451 2015-11-29 18:16:23 nActualTimespan = 968242 before bounds 2015-11-29 18:16:23 GetNextWorkRequired RETARGET 2015-11-29 18:16:23 params.nPowTargetTimespan = 1209600 nActualTimespan = 968242 2015-11-29 18:16:23 Before: 1851aba2 000000000000000051aba2000000000000000000000000000000000000000000 2015-11-29 18:16:23 After: 18415fd1 0000000000000000415fd1fdd0369d0369d0369d0369d0369d0369d0369d0369 2015-11-29 18:16:25 nActualTimespan = 1173468 before bounds 2015-11-29 18:16:25 GetNextWorkRequired RETARGET 2015-11-29 18:16:25 params.nPowTargetTimespan = 1209600 nActualTimespan = 1173468 2015-11-29 18:16:25 Before: 18415fd1 0000000000000000415fd1000000000000000000000000000000000000000000 2015-11-29 18:16:25 After: 183f6be6 00000000000000003f6be67a434a9b101767dce434a9b101767dce434a9b1017 2015-11-29 18:16:28 nActualTimespan = 1119210 before bounds 2015-11-29 18:16:28 GetNextWorkRequired RETARGET 2015-11-29 18:16:28 params.nPowTargetTimespan = 1209600 nActualTimespan = 1119210 2015-11-29 18:16:28 Before: 183f6be6 00000000000000003f6be6000000000000000000000000000000000000000000 2015-11-29 18:16:28 After: 183aaea2 00000000000000003aaea2af8e38e38e38e38e38e38e38e38e38e38e38e38e38 2015-11-29 18:16:33 nActualTimespan = 1148708 before bounds 2015-11-29 18:16:33 GetNextWorkRequired RETARGET 2015-11-29 18:16:33 params.nPowTargetTimespan = 1209600 nActualTimespan = 1148708 2015-11-29 18:16:33 Before: 183aaea2 00000000000000003aaea2000000000000000000000000000000000000000000 2015-11-29 18:16:33 After: 1837ba62 000000000000000037ba6263d779334ef0aac668223ddf99b557112cce88a446 2015-11-29 18:16:34 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:35 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:35 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:16:38 nActualTimespan = 1000852 before bounds 2015-11-29 18:16:38 GetNextWorkRequired RETARGET 2015-11-29 18:16:38 params.nPowTargetTimespan = 1209600 nActualTimespan = 1000852 2015-11-29 18:16:38 Before: 1837ba62 000000000000000037ba62000000000000000000000000000000000000000000 2015-11-29 18:16:38 After: 182e1c58 00000000000000002e1c58c17530eca8641fdb97530eca8641fdb97530eca864 2015-11-29 18:16:40 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:41 nActualTimespan = 1051548 before bounds 2015-11-29 18:16:41 GetNextWorkRequired RETARGET 2015-11-29 18:16:41 params.nPowTargetTimespan = 1209600 nActualTimespan = 1051548 2015-11-29 18:16:41 Before: 182e1c58 00000000000000002e1c58000000000000000000000000000000000000000000 2015-11-29 18:16:41 After: 182815ee 00000000000000002815eed3ee721a54d880bb3ee721a54d880bb3ee721a54d8 2015-11-29 18:16:43 nActualTimespan = 1112235 before bounds 2015-11-29 18:16:43 GetNextWorkRequired RETARGET 2015-11-29 18:16:43 params.nPowTargetTimespan = 1209600 nActualTimespan = 1112235 2015-11-29 18:16:43 Before: 182815ee 00000000000000002815ee000000000000000000000000000000000000000000 2015-11-29 18:16:43 After: 1824dbe9 000000000000000024dbe917e45e45e45e45e45e45e45e45e45e45e45e45e45e 2015-11-29 18:16:45 nActualTimespan = 1040986 before bounds 2015-11-29 18:16:45 GetNextWorkRequired RETARGET 2015-11-29 18:16:45 params.nPowTargetTimespan = 1209600 nActualTimespan = 1040986 2015-11-29 18:16:45 Before: 1824dbe9 000000000000000024dbe9000000000000000000000000000000000000000000 2015-11-29 18:16:45 After: 181fb893 00000000000000001fb893cd9ba8a9798687576465354243132020f0fdfecedb 2015-11-29 18:16:46 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:47 nActualTimespan = 1197814 before bounds 2015-11-29 18:16:47 GetNextWorkRequired RETARGET 2015-11-29 18:16:47 params.nPowTargetTimespan = 1209600 nActualTimespan = 1197814 2015-11-29 18:16:47 Before: 181fb893 00000000000000001fb893000000000000000000000000000000000000000000 2015-11-29 18:16:47 After: 181f6973 00000000000000001f69731bc10aff9ee8dd7cc6bb5aa499388277166054f43e 2015-11-29 18:16:49 nActualTimespan = 1176553 before bounds 2015-11-29 18:16:49 GetNextWorkRequired RETARGET 2015-11-29 18:16:49 params.nPowTargetTimespan = 1209600 nActualTimespan = 1176553 2015-11-29 18:16:49 Before: 181f6973 00000000000000001f6973000000000000000000000000000000000000000000 2015-11-29 18:16:49 After: 181e8dc0 00000000000000001e8dc0822d21c10aff9ee8dd7cc6bb5aa499388277166054 2015-11-29 18:16:50 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:52 nActualTimespan = 1099096 before bounds 2015-11-29 18:16:52 GetNextWorkRequired RETARGET 2015-11-29 18:16:52 params.nPowTargetTimespan = 1209600 nActualTimespan = 1099096 2015-11-29 18:16:52 Before: 181e8dc0 00000000000000001e8dc0000000000000000000000000000000000000000000 2015-11-29 18:16:52 After: 181bc330 00000000000000001bc330077a113aad446de077a113aad446de077a113aad44 2015-11-29 18:16:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:54 nActualTimespan = 1188699 before bounds 2015-11-29 18:16:54 GetNextWorkRequired RETARGET 2015-11-29 18:16:54 params.nPowTargetTimespan = 1209600 nActualTimespan = 1188699 2015-11-29 18:16:54 Before: 181bc330 00000000000000001bc330000000000000000000000000000000000000000000 2015-11-29 18:16:54 After: 181b4861 00000000000000001b4861699999999999999999999999999999999999999999 2015-11-29 18:16:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:57 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:16:58 nActualTimespan = 1218446 before bounds 2015-11-29 18:16:58 GetNextWorkRequired RETARGET 2015-11-29 18:16:58 params.nPowTargetTimespan = 1209600 nActualTimespan = 1218446 2015-11-29 18:16:58 Before: 181b4861 00000000000000001b4861000000000000000000000000000000000000000000 2015-11-29 18:16:58 After: 181b7b74 00000000000000001b7b74f09a322bab433cbc544dcd655ede766fef87810098 2015-11-29 18:16:59 Leaving block file 96: CBlockFileInfo(blocks=395, size=134186178, heights=271249...272004, time=2013-11-24...2013-11-28) 2015-11-29 18:17:00 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:00 nActualTimespan = 1226455 before bounds 2015-11-29 18:17:00 GetNextWorkRequired RETARGET 2015-11-29 18:17:00 params.nPowTargetTimespan = 1209600 nActualTimespan = 1226455 2015-11-29 18:17:00 Before: 181b7b74 00000000000000001b7b74000000000000000000000000000000000000000000 2015-11-29 18:17:00 After: 181bdd7c 00000000000000001bdd7cd6af004559aaf004559aaf004559aaf004559aaf00 2015-11-29 18:17:01 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:03 nActualTimespan = 1174382 before bounds 2015-11-29 18:17:03 GetNextWorkRequired RETARGET 2015-11-29 18:17:03 params.nPowTargetTimespan = 1209600 nActualTimespan = 1174382 2015-11-29 18:17:03 Before: 181bdd7c 00000000000000001bdd7c000000000000000000000000000000000000000000 2015-11-29 18:17:03 After: 181b0dca 00000000000000001b0dca40de5ab277f44c118de5ab277f44c118de5ab277f4 2015-11-29 18:17:05 nActualTimespan = 1117977 before bounds 2015-11-29 18:17:05 GetNextWorkRequired RETARGET 2015-11-29 18:17:05 params.nPowTargetTimespan = 1209600 nActualTimespan = 1117977 2015-11-29 18:17:05 Before: 181b0dca 00000000000000001b0dca000000000000000000000000000000000000000000 2015-11-29 18:17:05 After: 1819012f 000000000000000019012f4137c048d159e26af37c048d159e26af37c048d159 2015-11-29 18:17:07 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:08 nActualTimespan = 1288695 before bounds 2015-11-29 18:17:08 GetNextWorkRequired RETARGET 2015-11-29 18:17:08 params.nPowTargetTimespan = 1209600 nActualTimespan = 1288695 2015-11-29 18:17:08 Before: 1819012f 000000000000000019012f000000000000000000000000000000000000000000 2015-11-29 18:17:08 After: 181aa3c0 00000000000000001aa3c0c7ff2ff2ff2ff2ff2ff2ff2ff2ff2ff2ff2ff2ff2f 2015-11-29 18:17:12 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:12 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:13 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:14 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:14 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:17 nActualTimespan = 1123006 before bounds 2015-11-29 18:17:17 GetNextWorkRequired RETARGET 2015-11-29 18:17:17 params.nPowTargetTimespan = 1209600 nActualTimespan = 1123006 2015-11-29 18:17:17 Before: 181aa3c0 00000000000000001aa3c0000000000000000000000000000000000000000000 2015-11-29 18:17:17 After: 1818bb87 000000000000000018bb87fe4b17e4b17e4b17e4b17e4b17e4b17e4b17e4b17e 2015-11-29 18:17:19 nActualTimespan = 1151848 before bounds 2015-11-29 18:17:19 GetNextWorkRequired RETARGET 2015-11-29 18:17:19 params.nPowTargetTimespan = 1209600 nActualTimespan = 1151848 2015-11-29 18:17:19 Before: 1818bb87 000000000000000018bb87000000000000000000000000000000000000000000 2015-11-29 18:17:19 After: 18178d3a 0000000000000000178d3afc5c8a0ce512956d9b1df623a67eac2f0734b78fbd 2015-11-29 18:17:19 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:19 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:21 nActualTimespan = 1190646 before bounds 2015-11-29 18:17:21 GetNextWorkRequired RETARGET 2015-11-29 18:17:21 params.nPowTargetTimespan = 1209600 nActualTimespan = 1190646 2015-11-29 18:17:21 Before: 18178d3a 0000000000000000178d3a000000000000000000000000000000000000000000 2015-11-29 18:17:21 After: 18172ec0 0000000000000000172ec03034a9b101767dce434a9b101767dce434a9b10176 2015-11-29 18:17:21 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:21 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:23 nActualTimespan = 1227984 before bounds 2015-11-29 18:17:23 GetNextWorkRequired RETARGET 2015-11-29 18:17:23 params.nPowTargetTimespan = 1209600 nActualTimespan = 1227984 2015-11-29 18:17:23 Before: 18172ec0 0000000000000000172ec0000000000000000000000000000000000000000000 2015-11-29 18:17:23 After: 181788f2 00000000000000001788f2e33b007cd49a166e33b007cd49a166e33b007cd49a 2015-11-29 18:17:23 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:24 nActualTimespan = 1142845 before bounds 2015-11-29 18:17:24 GetNextWorkRequired RETARGET 2015-11-29 18:17:24 params.nPowTargetTimespan = 1209600 nActualTimespan = 1142845 2015-11-29 18:17:24 Before: 181788f2 00000000000000001788f2000000000000000000000000000000000000000000 2015-11-29 18:17:24 After: 18163c71 0000000000000000163c71514e4a39f8f4e4a39f8f4e4a39f8f4e4a39f8f4e4a 2015-11-29 18:17:24 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:17:25 nActualTimespan = 1256242 before bounds 2015-11-29 18:17:25 GetNextWorkRequired RETARGET 2015-11-29 18:17:25 params.nPowTargetTimespan = 1209600 nActualTimespan = 1256242 2015-11-29 18:17:25 Before: 18163c71 0000000000000000163c71000000000000000000000000000000000000000000 2015-11-29 18:17:25 After: 181717f0 00000000000000001717f0ed2632632632632632632632632632632632632632 2015-11-29 18:17:26 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:27 nActualTimespan = 1208767 before bounds 2015-11-29 18:17:27 GetNextWorkRequired RETARGET 2015-11-29 18:17:27 params.nPowTargetTimespan = 1209600 nActualTimespan = 1208767 2015-11-29 18:17:27 Before: 181717f0 00000000000000001717f0000000000000000000000000000000000000000000 2015-11-29 18:17:27 After: 181713dd 00000000000000001713ddbf500611722833944a55b66c77d88e99fab0bc1cd2 2015-11-29 18:17:31 nActualTimespan = 1180751 before bounds 2015-11-29 18:17:31 GetNextWorkRequired RETARGET 2015-11-29 18:17:31 params.nPowTargetTimespan = 1209600 nActualTimespan = 1180751 2015-11-29 18:17:31 Before: 181713dd 00000000000000001713dd000000000000000000000000000000000000000000 2015-11-29 18:17:31 After: 181686f5 00000000000000001686f5e6623a67eac2f0734b78fbd401845c8a0ce512956d 2015-11-29 18:17:33 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:33 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:35 nActualTimespan = 1240556 before bounds 2015-11-29 18:17:35 GetNextWorkRequired RETARGET 2015-11-29 18:17:35 params.nPowTargetTimespan = 1209600 nActualTimespan = 1240556 2015-11-29 18:17:35 Before: 181686f5 00000000000000001686f5000000000000000000000000000000000000000000 2015-11-29 18:17:35 After: 18171a8b 0000000000000000171a8b6ad5cb3a9186f64d42b208fe6dc4ba298075e53c31 2015-11-29 18:17:36 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:38 nActualTimespan = 1158415 before bounds 2015-11-29 18:17:38 GetNextWorkRequired RETARGET 2015-11-29 18:17:38 params.nPowTargetTimespan = 1209600 nActualTimespan = 1158415 2015-11-29 18:17:38 Before: 18171a8b 0000000000000000171a8b000000000000000000000000000000000000000000 2015-11-29 18:17:38 After: 18162043 0000000000000000162043e9f4e4a39f8f4e4a39f8f4e4a39f8f4e4a39f8f4e4 2015-11-29 18:17:39 nActualTimespan = 1216710 before bounds 2015-11-29 18:17:39 GetNextWorkRequired RETARGET 2015-11-29 18:17:39 params.nPowTargetTimespan = 1209600 nActualTimespan = 1216710 2015-11-29 18:17:39 Before: 18162043 0000000000000000162043000000000000000000000000000000000000000000 2015-11-29 18:17:39 After: 1816418e 000000000000000016418e5d8138138138138138138138138138138138138138 2015-11-29 18:17:40 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:42 nActualTimespan = 1169948 before bounds 2015-11-29 18:17:42 GetNextWorkRequired RETARGET 2015-11-29 18:17:42 params.nPowTargetTimespan = 1209600 nActualTimespan = 1169948 2015-11-29 18:17:42 Before: 1816418e 000000000000000016418e000000000000000000000000000000000000000000 2015-11-29 18:17:42 After: 181586c8 00000000000000001586c85cbb076c327ee3a9f65b216dd298e54a105cc187d4 2015-11-29 18:17:43 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:44 nActualTimespan = 1181790 before bounds 2015-11-29 18:17:44 GetNextWorkRequired RETARGET 2015-11-29 18:17:44 params.nPowTargetTimespan = 1209600 nActualTimespan = 1181790 2015-11-29 18:17:44 Before: 181586c8 00000000000000001586c8000000000000000000000000000000000000000000 2015-11-29 18:17:44 After: 18150815 00000000000000001508151db6db6db6db6db6db6db6db6db6db6db6db6db6db 2015-11-29 18:17:46 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:47 nActualTimespan = 1199925 before bounds 2015-11-29 18:17:47 GetNextWorkRequired RETARGET 2015-11-29 18:17:47 params.nPowTargetTimespan = 1209600 nActualTimespan = 1199925 2015-11-29 18:17:47 Before: 18150815 0000000000000000150815000000000000000000000000000000000000000000 2015-11-29 18:17:47 After: 1814dd04 000000000000000014dd047379e79e79e79e79e79e79e79e79e79e79e79e79e7 2015-11-29 18:17:47 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:49 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:49 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:50 nActualTimespan = 1174893 before bounds 2015-11-29 18:17:50 GetNextWorkRequired RETARGET 2015-11-29 18:17:50 params.nPowTargetTimespan = 1209600 nActualTimespan = 1174893 2015-11-29 18:17:50 Before: 1814dd04 000000000000000014dd04000000000000000000000000000000000000000000 2015-11-29 18:17:50 After: 181443c4 00000000000000001443c41eebaebaebaebaebaebaebaebaebaebaebaebaebae 2015-11-29 18:17:51 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:52 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:56 nActualTimespan = 1152239 before bounds 2015-11-29 18:17:56 GetNextWorkRequired RETARGET 2015-11-29 18:17:56 params.nPowTargetTimespan = 1209600 nActualTimespan = 1152239 2015-11-29 18:17:56 Before: 181443c4 00000000000000001443c4000000000000000000000000000000000000000000 2015-11-29 18:17:56 After: 18134dc1 0000000000000000134dc113042bfe7ba375f31aed6a9264e209dc598153d0f8 2015-11-29 18:17:56 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:17:58 nActualTimespan = 1161129 before bounds 2015-11-29 18:17:58 GetNextWorkRequired RETARGET 2015-11-29 18:17:58 params.nPowTargetTimespan = 1209600 nActualTimespan = 1161129 2015-11-29 18:17:58 Before: 18134dc1 0000000000000000134dc1000000000000000000000000000000000000000000 2015-11-29 18:17:58 After: 181287ba 00000000000000001287ba72f0123456789abcdf0123456789abcdf012345678 2015-11-29 18:18:01 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:01 nActualTimespan = 1180205 before bounds 2015-11-29 18:18:01 GetNextWorkRequired RETARGET 2015-11-29 18:18:01 params.nPowTargetTimespan = 1209600 nActualTimespan = 1180205 2015-11-29 18:18:01 Before: 181287ba 00000000000000001287ba000000000000000000000000000000000000000000 2015-11-29 18:18:01 After: 18121472 00000000000000001214727fbd5bd5bd5bd5bd5bd5bd5bd5bd5bd5bd5bd5bd5b 2015-11-29 18:18:02 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:02 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:03 nActualTimespan = 1208198 before bounds 2015-11-29 18:18:03 GetNextWorkRequired RETARGET 2015-11-29 18:18:03 params.nPowTargetTimespan = 1209600 nActualTimespan = 1208198 2015-11-29 18:18:03 Before: 18121472 0000000000000000121472000000000000000000000000000000000000000000 2015-11-29 18:18:03 After: 18120f14 0000000000000000120f14a65082e60c3ea1c7fa5d83b6193f71d4fb2d90b6e9 2015-11-29 18:18:05 nActualTimespan = 1182978 before bounds 2015-11-29 18:18:05 GetNextWorkRequired RETARGET 2015-11-29 18:18:05 params.nPowTargetTimespan = 1209600 nActualTimespan = 1182978 2015-11-29 18:18:05 Before: 18120f14 0000000000000000120f14000000000000000000000000000000000000000000 2015-11-29 18:18:05 After: 1811a954 000000000000000011a95441c869536202ecfb9c869536202ecfb9c869536202 2015-11-29 18:18:07 nActualTimespan = 1143575 before bounds 2015-11-29 18:18:07 GetNextWorkRequired RETARGET 2015-11-29 18:18:07 params.nPowTargetTimespan = 1209600 nActualTimespan = 1143575 2015-11-29 18:18:07 Before: 1811a954 000000000000000011a954000000000000000000000000000000000000000000 2015-11-29 18:18:07 After: 1810b289 000000000000000010b28904a28a28a28a28a28a28a28a28a28a28a28a28a28a 2015-11-29 18:18:08 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:09 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:09 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:09 nActualTimespan = 1095256 before bounds 2015-11-29 18:18:09 GetNextWorkRequired RETARGET 2015-11-29 18:18:09 params.nPowTargetTimespan = 1209600 nActualTimespan = 1095256 2015-11-29 18:18:09 Before: 1810b289 000000000000000010b289000000000000000000000000000000000000000000 2015-11-29 18:18:09 After: 180f1e76 00000000000000000f1e762764d42b208fe6dc4ba298075e53c31a0f7ed5cb3a 2015-11-29 18:18:10 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:11 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:14 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:16 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:17 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:23 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:26 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:36 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:36 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:42 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:42 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:47 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:47 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:49 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:50 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:50 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:51 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:54 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:54 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:18:59 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:06 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:06 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:08 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:11 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:11 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:19:12 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:13 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:14 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:17 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:18 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:18 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:25 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:26 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:29 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:30 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:19:30 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:19:34 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:34 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:35 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:35 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:35 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:36 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:37 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:41 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:42 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:19:44 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:19:47 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:48 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:56 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:19:57 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:02 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:07 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:08 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:08 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:19 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:19 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:20 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:20 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:20 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:20 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:21 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:27 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:35 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:42 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:42 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:44 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:47 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:20:47 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:52 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:55 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:56 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:56 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:20:59 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:16 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:16 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:19 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:22 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:23 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:28 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:35 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:42 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:42 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:45 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:45 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:45 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:47 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:21:47 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:21:50 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-29 18:21:50 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:51 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:53 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:56 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:21:57 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:22:02 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:22:16 ERROR: AcceptToMemoryPool: non-final 2015-11-29 18:22:18 ERROR: AcceptToMemoryPool: non-final Title: Re: Bitcoin QT not synching Post by: achow101 on November 29, 2015, 11:56:42 PM Are you trying to mine at the same time that it is trying to sync?
Code: 2015-11-29 18:14:43 params.nPowTargetTimespan = 1209600 nActualTimespan = 1042157 It looks like the problem is that it does not recognize block 271980 as a valid block. BTW, you can ignore all of the AcceptToMemoryPool errors, those are ok and are just saying that the node is rejected a bunch of transaction since they don't match the rules you are enforcing. Usually it is for low fee transactions. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 30, 2015, 12:00:34 AM Thanks Knightdk. Do you know how I can fix this?
EDIT: Just read the first line of your last post. 'Am I trying to mine at the same time I'm trying to sync?' No idea what that means. I'm not trying to use the wallet at all if that's what you mean. And I've just left the computer alone during this time. Title: Re: Bitcoin QT not synching Post by: achow101 on November 30, 2015, 12:04:59 AM Thanks Knightdk. Do you know how I can fix this? Not sure. Are you mining on your node? Do you have a miner pointed at your node? Do have gen=1 in your Bitcoin.conf? Are you starting Bitcoin Core with the -gen option? Did you at any time type setgenerate true into the debug console? Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 30, 2015, 12:08:08 AM Didn't type anything into the console. Don't know what mining the node means.
Title: Re: Bitcoin QT not synching Post by: achow101 on November 30, 2015, 12:21:23 AM I think I know why it isn't validating. For some unknown reason, your node is recalculating the difficulty that it is expecting to find in the next block. Except the difficulty keeps getting higher, above what the next block (271,980) actually is. Because the difficulty of that block is too low than what the node thinks it should be, the block is considered invalid and you are stuck.
What we need to figure out is why it keeps calculating the difficulty. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on November 30, 2015, 12:28:27 AM Ok. Glad one of us knows what he's talking about :) It's after midnight here in the UK, so will check back in in the morning. I appreciate your help.
Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 12:37:49 AM Any ideas yet guys? I've just given up trying to download the blockchain now. It just keeps on sticking, so no point. Any alternatives to being able to transfer to a different wallet?
Title: Re: Bitcoin QT not synching Post by: achow101 on December 01, 2015, 12:41:41 AM Any ideas yet guys? I've just given up trying to download the blockchain now. It just keeps on sticking, so no point. Any alternatives to being able to transfer to a different wallet? Export the private keys and import them into another wallet like Electrum. Install Electrum and then open the Debug Window of Bitcoin Core. Go to the console tab and typeCode: dumprivkey <address> Code: walletpassphrase <passphrase> 120 Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 08:40:36 AM Many thanks. Will try that and get back to you. ;)
Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 08:59:03 AM Ok, have tried dumprivkey <receiving address of bitcoin I bought> and the response comes back "Method not found (code -32601)". Have tried leaving a space after the word dumprivkey, then no space etc. Tried two different addresses that I've used.
Title: Re: Bitcoin QT not synching Post by: ranochigo on December 01, 2015, 09:01:37 AM Ok, have tried dumprivkey <receiving address of bitcoin I bought> and the response comes back "Method not found (code -32601)". Have tried leaving a space after the word dumprivkey, then no space etc. Tried two different addresses that I've used. It should be Code: dumpprivkey [address here] Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 09:22:09 AM thank you. Does it matter what brackets I use or spaces etc?
Title: Re: Bitcoin QT not synching Post by: shorena on December 01, 2015, 09:23:13 AM Maybe the brackets cause confusion?
An example Code: walletpassphrase thisISmySECRETpassword 120 be careful to not show the private key to anyone. Once its imported into electrum you should transfer it to an electrum wallet that is covered by a seed. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 09:29:21 AM Thank you guys! I've got the first private key and am going to try to put it into Electrum. Will keep you posted.
Title: Re: Bitcoin QT not synching Post by: shorena on December 01, 2015, 09:36:46 AM Thank you guys! I've got the first private key and am going to try to put it into Electrum. Will keep you posted. Step by step: #1 File -> New/Restore #2 Enter a name, confirm with "OK" #3 select "Restore a wallet or import keys" and "Standard wallet", confirm with "Next" #4 Enter the private key(s) in the box, confirm with "Next" #5 Set password, confirm with "OK" #6 Let it snyc. Its done when the red dot bottom right turns green. This should only take a few minutes. You can create a new wallet that is covered by the seed while keeping the above temporary wallet open. Steps #1 and #2 are the same, for #3 select "Create new wallet" and and "Standard wallet", confirm with "Next" #4 write down the seed, confirm with "Next" #5 confirm the seed #6 set password #7 let it generate addresses #8 Go to "Receive" and us the address shown to send all your coins from the other wallet to it. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 09:44:57 AM Brilliant. It's worked. My balance is showing up in Electrum now. Just for any newbies who want to know what worked:
1. dumpprivkey [followed by a space then the receiving address you sent your bitcoins to, without any brackets] 2. walletpassphrase [followed by a space then your passphrase, space, then the time you want to be able to access the privat key] 3. then repeat step 1 4. wallet private key for the specific address will appear Will try the new wallet with seed as you suggested Shorena. I'm really grateful to you, ranochigo and knightdk! I had three weeks of stressing for nothing! ::) Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 10:01:36 AM Shorena/ anyone, is there a way to transfer coins to another electrum wallet without paying a transaction fee? Could it be done with the private keys for example?
Title: Re: Bitcoin QT not synching Post by: ranochigo on December 01, 2015, 10:27:26 AM Shorena/ anyone, is there a way to transfer coins to another electrum wallet without paying a transaction fee? Could it be done with the private keys for example? Yes. Have you sweeped it already? If yes, then go to tool, preference and check set transaction fees manually. Go to send and you can select your own fees. I suggest you not to try to do so. It would reject your transaction if does not have enough priority, any of the output is below 0.01BTC or if the size is above 1kb. Pay some fees or you could end up like this: https://blockchain.info/tx/7917f91cedf270a53b6450e6d8165d97175f957005773a4428c42f84ad7d8083.Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 12:47:33 PM Thanks Ranochigo. What is sweeping? I saw that function listed on one of the menus.
I need to read up on how this all works obviously. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 12:56:14 PM Ok, just read about sweeping. No, I put them in the wallet via the private keys. I was looking for a way to transfer them to a seeded wallet without paying a transaction fee.
Title: Re: Bitcoin QT not synching Post by: ranochigo on December 01, 2015, 01:00:45 PM Ok, just read about sweeping. No, I put them in the wallet via the private keys. I was looking for a way to transfer them to a seeded wallet without paying a transaction fee. The lesser the transaction fees you pay, the harder it is for miners to have incentive to confirm it for you. A fee of 0.0001BTC isn't too much right? :) However, you can send one if it has sat in your wallet for a long time and it has a high value.* Would you revealing the address so we can check out the inputs?Edit:* And you don't mind waiting for sometime eg. a few days. Edit edit: Transactions are prioritized according to priority and/or fee. Hence, the higher the priority, the easier it is for miner to confirm your transaction. If the network load is high, the probability decreases. Title: Re: Bitcoin QT not synching Post by: shorena on December 01, 2015, 01:04:36 PM Ok, just read about sweeping. No, I put them in the wallet via the private keys. I was looking for a way to transfer them to a seeded wallet without paying a transaction fee. You can only transfer them to a seeded wallet via the network. It is possible to pay no transaction fee when creating a transaction for the network, but its usually not a good idea. As ranchigo said, you need "priority" to get a transaction without fee confirmed. Bitcoins gain priority over time. Your 0.01 will roughly have the needed priority after 100 days. To avoid that the transaction is "in limbo" its better to pay a fee as electrum suggests. There is a setting called "dynamic fee" you should enable it. It estimates the lowest fee without a risk to get your transaction stuck. If your fee is too low there is a chance that the transaction takes a long time (days) to confirm. E.g. the 10,000 transactions currently waiting for a confirmation. https://i.imgur.com/T7xH0FZ.png Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 01:13:13 PM Thanks. I've done that. Is the seeded wallet only necessary if you want the security of a seed phrase to recover your money in the event of a corrupted wallet? Or does a seeded wallet have other advantages?
Title: Re: Bitcoin QT not synching Post by: ranochigo on December 01, 2015, 01:19:09 PM Thanks. I've done that. Is the seeded wallet only necessary if you want the security of a seed phrase to recover your money in the event of a corrupted wallet? Or does a seeded wallet have other advantages? If you check your wallet to send the coins to a change address, the wallet will send the change to a new address everytime. Clients like Bitcoin Core pregenerate 100 addresses and after the 100 address runs out, you will start using the other 100. However, older backup will never have the new 100 addresses if you only backup them at the start. You need to back them up regularly HD wallets have a seed which allows the client to generate predictable addresses and hence you only need a one time backup.Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 01:29:39 PM Thanks. I've sent the contents of the temp wallet to a new seeded wallet. But the transaction hasn't shown up in the new wallet yet (or the old). I've saved a copy of the transaction. When I open it there's a 'broadcast' button. I haven't pressed that. How do I make sure the transaction has completed properly?
Title: Re: Bitcoin QT not synching Post by: shorena on December 01, 2015, 02:40:11 PM Thanks. I've sent the contents of the temp wallet to a new seeded wallet. But the transaction hasn't shown up in the new wallet yet (or the old). I've saved a copy of the transaction. When I open it there's a 'broadcast' button. I haven't pressed that. How do I make sure the transaction has completed properly? There should be a transaction ID, that looks somewhat like this 224d7baa8f57b5b7f275b671e7d412089b90bf4f061456729aff9ec373dac448 If you go to https://www.blocktrail.com/BTC/ and enter your transaction ID into the search box it should show your transaction (with your addresses). If it does not, the transaction still needs to be broadcasted. If the electrum wallet does not show it, try closing and reopening it. Sometimes this only works once the transaction is confirmed. Title: Re: Bitcoin QT not synching Post by: peonminer on December 01, 2015, 02:42:55 PM 1.Close wallet.
2.Delete your 'blocks' and 'chainstate' folder in your 'C:/User/appdata/roaming/bitcoin/' folder. 3.Open wallet. 4.Profit. ***NOTE*** DO NOT DELETE WALLET.DAT FOLDER. In fact, this is an excellent time to back up that file as it contains all of your addresses and c0ainZ. Title: Re: Bitcoin QT not synching Post by: shorena on December 01, 2015, 02:45:12 PM 1.Close wallet. 2.Delete your 'blocks' and 'chainstate' folder in your 'C:/User/appdata/roaming/bitcoin/' folder. 3.Open wallet. 4.Profit. ***NOTE*** DO NOT DELETE WALLET.DAT FOLDER. In fact, this is an excellent time to back up that file as it contains all of your addresses and c0ainZ. #1 read all the posts #2 think #3 write. Title: Re: Bitcoin QT not synching Post by: ranochigo on December 01, 2015, 02:47:33 PM Thanks. I've sent the contents of the temp wallet to a new seeded wallet. But the transaction hasn't shown up in the new wallet yet (or the old). I've saved a copy of the transaction. When I open it there's a 'broadcast' button. I haven't pressed that. How do I make sure the transaction has completed properly? There should be a transaction ID, that looks somewhat like this 224d7baa8f57b5b7f275b671e7d412089b90bf4f061456729aff9ec373dac448 If you go to https://www.blocktrail.com/BTC/ and enter your transaction ID into the search box it should show your transaction (with your addresses). If it does not, the transaction still needs to be broadcasted. If the electrum wallet does not show it, try closing and reopening it. Sometimes this only works once the transaction is confirmed. Title: Re: Bitcoin QT not synching Post by: peonminer on December 01, 2015, 03:23:23 PM 1.Close wallet. 2.Delete your 'blocks' and 'chainstate' folder in your 'C:/User/appdata/roaming/bitcoin/' folder. 3.Open wallet. 4.Profit. ***NOTE*** DO NOT DELETE WALLET.DAT FOLDER. In fact, this is an excellent time to back up that file as it contains all of your addresses and c0ainZ. #1 read all the posts #2 think #3 write. :D :D :D You got me ;) Was trying to give a quick jump @ it during the btc crash and ultimately didn't read through the thread :P Don't burn me at the stake, please? :D Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 01, 2015, 03:26:57 PM Thanks. I've sent the contents of the temp wallet to a new seeded wallet. But the transaction hasn't shown up in the new wallet yet (or the old). I've saved a copy of the transaction. When I open it there's a 'broadcast' button. I haven't pressed that. How do I make sure the transaction has completed properly? There should be a transaction ID, that looks somewhat like this 224d7baa8f57b5b7f275b671e7d412089b90bf4f061456729aff9ec373dac448 If you go to https://www.blocktrail.com/BTC/ and enter your transaction ID into the search box it should show your transaction (with your addresses). If it does not, the transaction still needs to be broadcasted. If the electrum wallet does not show it, try closing and reopening it. Sometimes this only works once the transaction is confirmed. Thanks once again. I didn't press the broadcast button. Now that I have the transaction is showing as pending in both wallets. Presumably it'll be confirmed soon enough. I'm still trying to get my head around how Bitcoin works. It seems very hit and miss to me at the moment, and risky and a bit stressful as a result. But at least now I have a functional walet that I can make some sense of thanks to all of you! Cheers. Title: Re: Bitcoin QT not synching Post by: shorena on December 01, 2015, 04:37:39 PM -snip- :D :D :D You got me ;) Was trying to give a quick jump @ it during the btc crash and ultimately didn't read through the thread :P Don't burn me at the stake, please? :D Nah, no burnings today. -snip- Thanks once again. I didn't press the broadcast button. Now that I have the transaction is showing as pending in both wallets. Presumably it'll be confirmed soon enough. I'm still trying to get my head around how Bitcoin works. It seems very hit and miss to me at the moment, and risky and a bit stressful as a result. But at least now I have a functional walet that I can make some sense of thanks to all of you! Cheers. It will get easier. If you have questions just ask. Title: Re: Bitcoin QT not synching Post by: Gabriel1918 on December 02, 2015, 10:25:23 AM Appreciated. The transaction confirmed last night. I've made copies of the wallet. Is there anything else I could do for security or is that enough? BTW, who gets paid the transaction fees?
Title: Re: Bitcoin QT not synching Post by: ranochigo on December 02, 2015, 10:31:51 AM Appreciated. The transaction confirmed last night. I've made copies of the wallet. Is there anything else I could do for security or is that enough? BTW, who gets paid the transaction fees? Are you using a HD wallet? If so, just make a few copy of the seed and you're fine. Security wise, try using an antivirus and scan regularly. Of course, that isn't enough, you must ensure that you don't download anything suspicious or go to any suspicious website. If you want it to be extra safe, use an offline computer, download this script: https://github.com/pointbiz/bitaddress.org. And open the html with the browser. You can go to paper wallet, generate a paper wallet and print it. Optionally, you can encrypt it with BIP38, there's an option for that. You can then use a mobile phone with mycelium and use their cold storage feature to spend it in the future.Miners. They are given the incentive to mine your transaction for you. After the block rewards ends, the fee will be their only revenue. And also, they help to prevent network spam by making the cost higher, most miners confirm those with fees first. Title: Re: Bitcoin QT not synching Post by: shorena on December 02, 2015, 10:33:25 AM Appreciated. The transaction confirmed last night. I've made copies of the wallet. Is there anything else I could do for security or is that enough? BTW, who gets paid the transaction fees? To secure an electurm wallet you have to #1 keep the seed safe (preferably offline), #2 have a strong password and #3 keep your machine free from malware. As long as you have your seed you can forget your password, as long as your password is strong enough and you have no keylogger on your system you can risk that the wallet file is stolen. The fee is part of the reward for miners to find a block. Currently they also get a 25 BTC bonus, but over time the bonus will decrease (halfes every 4 years) and fees will be the only incentive for miners to find blocks. Title: Re: Bitcoin QT not synching Post by: BTCBinary on December 04, 2015, 02:09:57 PM Have you tried to export the wallet to the blockchain.info site. If you have tried all that methods to solve and haven't made it, I guess you should't try to export your wallet.dat to the blockchain.
|
