Quote from: SMFeasy on August 10, 2018, 07:33:25 AM

{
  "address": "0x5c5f76f154539fff7a20695f3bbc32715c077c51",
  "msg": "My account smithAwesson has been hacked/lost. Please reset the email to mebelendadmn@gmail.com . The current date is 24.05.2018",
  "sig": "0xcb522e450a9a9bc7bd9cdccb3416d6dba5591519ff4ccdc5e59ae77c3f27e0261fc4d6a9f07c5 2093c8bd06e882d36795d6b50334781e91e43de346c07a85c501c",
  "version": "3",
  "signer": "web3"
}

https://etherscan.io/verifySig/1150

Here is the unedited post where I posted that address:
https://bitcointalk.org/index.php?topic=1861465.msg19047910#msg19047910
https://bitcointalk.org/index.php?topic=2046450.msg21337890#msg21337890
https://bitcointalk.org/index.php?topic=1819566.msg18850369#msg18850369

I had a hard time to verify this message... There is a whitespace in between 5 and 2 (bold and red below) on the signature hash
0xcb522e450a9a9bc7bd9cdccb3416d6dba5591519ff4ccdc5e59ae77c3f27e0261fc4d6a9f07c5 2093c8bd06e882d36795d6b50334781e91e43de346c07a85c501c

Anyway the signature has been verified successfully eventually.

PS: Better practice is to use a signature in-between the [code][/code] tag. i.e:

Code:

{
  "address": "0x5c5f76f154539fff7a20695f3bbc32715c077c51",
  "msg": "My account smithAwesson has been hacked/lost. Please reset the email to mebelendadmn@gmail.com . The current date is 24.05.2018",
  "sig": "0xcb522e450a9a9bc7bd9cdccb3416d6dba5591519ff4ccdc5e59ae77c3f27e0261fc4d6a9f07c52093c8bd06e882d36795d6b50334781e91e43de346c07a85c501c",
  "version": "3",
  "signer": "web3"
}