Well, here then:
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
I am AaronJonk from Bitcoin Forum « bitcointalk.org »
As the implementation of BIP 0173 demands, I'm adopting Bech32 as segwit address format and the following bitcoin address will be used by me for signing purposes (authenticity, integrity, non-repudiation):
1786ygFBX2tFUJCXvkwxXG3Kqua19QMdfu
Today is Monday, November 4th, 2019 18:51 (UTC).
-----BEGIN SIGNATURE-----
HwSwn7tGVxrv0kN9h5j9xa4/EkmwXBu+I6lFPeI1iJLQPBeX5Mw06PzIDViIJtvYSVIfA3l3t1pYPiszQUQcqQo=
-----END BITCOIN SIGNED MESSAGE-----
I am AaronJonk from Bitcoin Forum « bitcointalk.org »
As the implementation of BIP 0173 demands, I'm adopting Bech32 as segwit address format and the following bitcoin address will be used by me for signing purposes (authenticity, integrity, non-repudiation):
1786ygFBX2tFUJCXvkwxXG3Kqua19QMdfu
Today is Monday, November 4th, 2019 18:51 (UTC).
-----BEGIN SIGNATURE-----
HwSwn7tGVxrv0kN9h5j9xa4/EkmwXBu+I6lFPeI1iJLQPBeX5Mw06PzIDViIJtvYSVIfA3l3t1pYPiszQUQcqQo=
-----END BITCOIN SIGNED MESSAGE-----
Quoted and verified
However, I would like to point out that your message is actually factually incorrect and somewhat misleading. That is NOT a SegWit address. It is a legacy address
Not sure where you got that signed message template from... or why you chose to use it if you're not actually going to use a bech32 segwit address as per BIP173
I basically went to a random page of this topic, and copied a template there ¯\_(ツ)_/¯
I'm sorry if it's misleading..