Quote from: nullius on December 02, 2017, 12:07:21 AM

I am curious as to how difficult it will be to get this verified with a signature from my Segwit P2WPKH-in-P2SH address. A few of the online tools linked in this thread seem to choke on it.

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
2017-12-01: I, nullius (bitcointalk.org #976210), hereby certify
36finjay27E5XPDtSdLEsPR1RypfhNW8D8 as my Bitcoin address and PGP key
0xC2E91CD74A4C57A105F6C21B5A00591B2F307E0C as my master trust anchor.
-----BEGIN SIGNATURE-----
36finjay27E5XPDtSdLEsPR1RypfhNW8D8
H7sJIPP41AO1A86NG4RhWL+gTq4wxG9Sp0+Q+0BfgmPAMlnF83coNFLp2R7/bq2tdmEvQOKZF4h96l7OOxPXaEk=
-----END BITCOIN SIGNED MESSAGE-----

Cross-certification with PGP key:

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Date: 2017-12-01
Bitcointalk.org login: nullius (976210)
Bitcoin address: 36finjay27E5XPDtSdLEsPR1RypfhNW8D8
E-mail: nullius@nym.zone

PGP fingerprints:

* Ed25519: 0xC2E91CD74A4C57A105F6C21B5A00591B2F307E0C
* RSA: 0xA232750664CC39D61CE5D61536EBB4AB699A10EE

I declare that my aforestated PGP Ed25519 Certification key is
the peremptory trust anchor for my online identity at this time,
and unless/until that key signs a statement declaring otherwise.
Unless this statement be revoked or modified by a statement bearing
authentication rooted in that key, I declare that aforestated Bitcoin
address may issue signatures controlling the aforestated Bitcointalk
account.
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSNOMR84IlYpr/EF5vEJ5MVn575SQUCWiHpvgAKCRDEJ5MVn575
SXTBAP0VUpfJ+gSzqv9vZlT1lKn0BeAhNEDuQqlh78bWSD2apwD/ab23Gb5nnOKX
mdiEIsMEUZ7DbhdScTgos6Jzl9NgGAo=
=7yj+
-----END PGP SIGNATURE-----

Please verify and quote!

Verified on keybase