Quote from: Vova1234 on October 20, 2018, 05:13:12 AM

Quote from: ohashi3d on October 20, 2018, 02:55:09 AM

I've just tried synchronizing with v1.3.1 daemon and the backup block data at May 25th.

...
2018-10-20 01:31:54 UpdateTip: new best=00000007876142530eaeca32e71d38179480cbebc45fe964fbe0c3e84b012493 height=248957 log2_work=45.519688 tx=1106206 date=2018-10-15 17:10:23 progress=0.997061
2018-10-20 01:31:54 ProcessBlock: ACCEPTED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 267, prev=00000025418b7351588bbcbb9c957a6c3a581bd10b433952aef3d694edc68763
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 268, prev=000000374b9231b2bae0534cd3d4e35924f32a81184aac6eef209697330e2123
2018-10-20 01:31:54 ERROR: CheckTransaction() : duplicate inputs
2018-10-20 01:31:54 ERROR: CheckBlock() : CheckTransaction failed
2018-10-20 01:31:54 ERROR: ProcessBlock() : CheckBlock FAILED
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 269, prev=0000002593846bb0d8716c00fbf30132c497b42e70315a0f65404ed129fc2e4a
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 270, prev=0000002390e6be74008db3fd88a144657de442cf03f72e9f8a2e446fd6f304f1
2018-10-20 01:31:54 ProcessBlock: ORPHAN BLOCK 271, prev=000000356605da7b259ec6893892b320bfd305d68edddc92e71fb64da1ba6f50
...

After block 248957, "duplicate inputs" message emerged, so sure enough, there was attacks, I think.

Interestingly, v1.3.1 daemon didn't stop synchronizing after block 248958.
It processed 300+ orphan blocks, and recorded hash values below:
height=248958: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67
height=248959: 00000013b54daf77086e740d4e0d7721afd933614c84321c54d2f4d85e553d42
These are same as the values on the Yenten Explorer https://ytn.overemo.com/

So...now, the Yenten blockchain became quite unhealthy...we will get different hash value from different version nodes.
CVE-2018-17144-fixed wallet may be useless in this situation...

And "duplicate inputs" messages still continue emerging on debug.log...it looks hopeless for me, unfortunately.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Edited:

I've deleted my CVE-2018-17144-fixed Windows binaries:
https://github.com/ohashi3d/yenten/releases/tag/2.0.1fix_CVE-2018-17144

Though I may still try running Yenten daemon for my technical interest,
Good bye Yenten, for a while, or eternally...

I have also downloaded the blockchain since May 20 and nothing has stuck with me.

https://i.13.yt/2018/10/20/1540012589-9293.png

But the problem is that when receiving new blocks, the wallet checks the blockchain and API RPC begins to respond to the request for a long time.

Code:

2018-10-20 05:04:18 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000022193d53b1aa17ac7b86fce2ceecbaba36f0e6d2a0a483c227d7aa4d67, bad-version(0x00000002), rejected nVersion=0x00000002 block (code 17)
2018-10-20 05:04:18 ERROR: invalid header received

Interesting. I've just taken a look at a 1.3.1 node that has been running for about 6 months in a pretty much forgotten about state. It claims to be at block 250640 (which is ahead of https://ytn.overemo.com/ ??).

Code:

UpdateTip: new best=000029414a8b9de4db77a05642d151b599ddca8699e880e4a49e19ca195f0060 height=250640 log2_work=45.519709 tx=1108289 date=2018-10-20 08:09:06 progress=1.000000
ProcessBlock: ACCEPTED

Seems to the running OK as far as i can tell. Just tons of entries like this popping up:

Code:

ProcessBlock: ORPHAN BLOCK 751, prev=00000014df02f9c0a9040ca6877927ae046057f78eb3a8909ecb41d5c4753c6e
ERROR: CheckTransaction() : duplicate inputs
ERROR: CheckBlock() : CheckTransaction failed

Code:

ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

Edit: I haven't really followed this so is 1.3.1 not affected by this bug and what is the advantage of running 2.0.1 anyways?