Stake your Bitcoin address here

[pina_pino]

-----BEGIN BITCOIN SIGNED MESSAGE-----
I am @pina_pino on asktom.cf and this address is mine.

Date: 2025-12-18.
hereby certify bc1qnwyrfupr80q4vmdqw7c6ahx3pjjh3f7ncmul9a as my Bitcoin address.
-----BEGIN SIGNATURE-----
bc1qnwyrfupr80q4vmdqw7c6ahx3pjjh3f7ncmul9a
IG9P2pR8FE9R9WzwxFTu5PMyG/jvLdsA7uyEGfqgeEMeR3Zy7AkBQ0VNYpvXr6lIcPtk6s4eqFBpiSULDLgZNcY=
-----END BITCOIN SIGNED MESSAGE-----

I change my address to Legacy address, this is my new address. Thanks

-----BEGIN BITCOIN SIGNED MESSAGE-----
I am @pina_pino on asktom.cf and this address is mine.

Date: 2025-12-19.
hereby certify 13zFpADAkn62aQcK3tshgkB93qtgMkW2Ww as my Bitcoin address.
-----BEGIN SIGNATURE-----
13zFpADAkn62aQcK3tshgkB93qtgMkW2Ww
IANgGZ3peSNk3p0LFC7GyGG6s/CADI0NAA+bSQqJtB8DC6G5U6fcLOH6z6Pm4yvTTnZ+o7qzW/IO6GQ5pJ5b2EU=
-----END BITCOIN SIGNED MESSAGE-----

[Charles-Tim]

-----BEGIN BITCOIN SIGNED MESSAGE-----
I am @pina_pino on asktom.cf and this address is mine.

Date: 2025-12-18.
hereby certify bc1qnwyrfupr80q4vmdqw7c6ahx3pjjh3f7ncmul9a as my Bitcoin address.
-----BEGIN SIGNATURE-----
bc1qnwyrfupr80q4vmdqw7c6ahx3pjjh3f7ncmul9a
IG9P2pR8FE9R9WzwxFTu5PMyG/jvLdsA7uyEGfqgeEMeR3Zy7AkBQ0VNYpvXr6lIcPtk6s4eqFBpiSULDLgZNcY=
-----END BITCOIN SIGNED MESSAGE-----

I change my address to Legacy address, this is my new address. Thanks

-----BEGIN BITCOIN SIGNED MESSAGE-----
I am @pina_pino on asktom.cf and this address is mine.

Date: 2025-12-19.
hereby certify 13zFpADAkn62aQcK3tshgkB93qtgMkW2Ww as my Bitcoin address.
-----BEGIN SIGNATURE-----
13zFpADAkn62aQcK3tshgkB93qtgMkW2Ww
IANgGZ3peSNk3p0LFC7GyGG6s/CADI0NAA+bSQqJtB8DC6G5U6fcLOH6z6Pm4yvTTnZ+o7qzW/IO6GQ5pJ5b2EU=
-----END BITCOIN SIGNED MESSAGE-----

Verification successful.

[odolvlobo]

I change my address to Legacy address, this is my new address. Thanks
...

The best way to change your address is to sign a message containing the new address using the old address. This proves that you are changing the address and not somebody else.

Otherwise, there is no way to know if somebody accessed your account and posted the message. As it stands, we can not be sure that the person now in control of pina_pino is the same person as before.

[LoyceV]

As it stands, we can not be sure that the person now in control of pina_pino is the same person as before.

There's less than 3 hours between his posts, pina_pino should just delete his first post.

[pina_pino]

The best way to change your address is to sign a message containing the new address using the old address. This proves that you are changing the address and not somebody else.

Otherwise, there is no way to know if somebody accessed your account and posted the message. As it stands, we can not be sure that the person now in control of pina_pino is the same person as before.

I change my address because with segwit not all can verified my sign, so that's why i change my address to legacy.

There's less than 3 hours between his posts, pina_pino should just delete his first post.

Yes I should delete my first post, thanks anyway

[Charles-Tim]

Yes I should delete my first post, thanks anyway

Who tell you this? There are many wallets that can be used to verify your signed message which you used your bitcoin address to sign. You do not need to worry of any address that you used for the signed message, we can always sign it on this forum.

[Husna QA]

Yes I should delete my first post, thanks anyway

Who tell you this? There are many wallets that can be used to verify your signed message which you used your bitcoin address to sign. You do not need to worry of any address that you used for the signed message, we can always sign it on this forum.

I created a challenge thread on the Indonesian local board to educate users about the importance of staking a Bitcoin address for account recovery.

One of the requirements was to use a Legacy BTC address (explained below*) and not to edit the signed message after posting.

However, @pina-pino submitted a signed message using a SegWit address, which does not meet the challenge requirements.

Instead of leaving the original post as it was, he created a new signed message and quoted his previous post, but that quoted post was later deleted. In my view, this was unnecessary.

-----

*
While using Bitcoin Core, I encountered an error when trying to create a signed message using a SegWit address and asked about it here:
https://asktom.cf/index.php?topic=5204167.msg53946225#msg53946225

Here is achow101's reply:

Previously I managed to make a signature on Console of the Bitcoin Core using the Legacy Address, but when trying with the SegWit Address the following message appears:

Code:

Address does not refer to key (code -3)

Please explain and the solution.
Thanks.

There is no solution and you cannot sign a message with a segwit address. This has been the case since segwit was introduced. See https://github.com/bitcoin/bitcoin/issues/10542

Based on that, not all wallets support signing/verifying Segwit addresses, including Bitcoin Core.