[00:38:58] <navcoin-bot> <aguycalled> committed patch @A-B
[00:50:17] <navcoin-bot> <aguycalled> replied to the issue with another issue @prole @A-B
[20:29:06] <navcoin-bot> <BitWho> hm.. it will be a while until this might be proven valid. but... https://twitter.com/EI_HJQI/status/1063521371966210048
[20:31:28] <navcoin-bot> <LordNelsson> I don't see anything there
[20:35:47] <navcoin-bot> <BitWho> https://twitter.com/satoshi/status/1063516638870478848
[20:36:04] <navcoin-bot> <BitWho> https://twitter.com/satoshi/status/1063501015385866240
[20:37:19] <navcoin-bot> <LordNelsson> this looks like fud to me tbh
[20:39:52] <navcoin-bot> <BitWho> csw , self a claimed satoshi. used signature from keys of block #9, known to be satoshis, to put in a msg on october. people are trying to validate it. the msg, if true , says what it is posted above.   a lot of people hate csw. so we shall see if he used trickery or actually signed from a satoshi key. which if true would give this claim a lot of validations. Now that is still just a claim. the real attack is still no known and thus
[20:39:53] <navcoin-bot> he still has to deliver it. and that attack will be subject to a lot of analyzing.
[20:41:03] <navcoin-bot> <BitWho> in other words. he incoded that msg on october. just recently he released a method to read that msg. the msg has been decoded.
[20:41:24] <navcoin-bot> <BitWho> drama will come.
[20:41:27] <navcoin-bot> <LordNelsson> hmm yeah
[20:41:31] <navcoin-bot> <LordNelsson> I don't know
[20:41:34] <navcoin-bot> <LordNelsson> we'll see
[21:14:30] <navcoin-bot> <BitWho> shit. so i was wrong. thats not the msg. it is a flaw on segwit. but the content of the msg is not known and that msg is way wrong.
[21:15:52] <navcoin-bot> <BitWho> so all it is know so far. is that satoshi keys signed an encoded msg on october. and csw only proved to show he has a set of sig that can confirm he wrote the msg. and the actual content of the msg are unknown, but he has said its related to a flaw of segwit and mal