Stake your Bitcoin address here

[SFR10]

I just signed a message on Coinomi and verified it with itself to see how it works.
Seems that there's a bug on Coinomi. It can't even verify the message signed by itself.

There's indeed a bug on that wallet but AFAICR, it doesn't extend to legacy addresses ^{[only the segwit addresses are affected]}.
^{Note to @palle11: I'm not implying it's safe to use Coinomi with a legacy address!}

[hosemary]

There's indeed a bug on that wallet but AFAICR, it doesn't extend to legacy addresses ^{[only the segwit addresses are affected]}.

I just tested that with signing a message from a legacy address and got the same error.

It's really funny how Coinomi works.
If you sign a message from Coinomi and then verify the same message without closing "Sign/verify message" window, it's verified successfully. It's verified even with a wrong signature.
If you sign a message from Coinomi, close the "Sign/verify message" window and then open it again and verify the message, it can't be verified.

[SFR10]

I just tested that with signing a message from a legacy address and got the same error.
~Snipped~
If you sign a message from Coinomi, close the "Sign/verify message" window and then open it again and verify the message, it can't be verified.

That's strange... I no longer have my spare tablet to personally test it, but @Zlantann had a "different experience" last month with a legacy address and "here's his/her signed message from a legacy address" in Coinomi.
^{- Did you also try verifying the same message with one of the online tools or other wallets?}

It's really funny how Coinomi works.
If you sign a message from Coinomi and then verify the same message without closing "Sign/verify message" window, it's verified successfully. It's verified even with a wrong signature.

Now that's something ^{[Coinomi at its finest]}

[hosemary]

^{- Did you also try verifying the same message with one of the online tools or other wallets?}

I just tried that. I was able to verify the message using other tools like electrum successfully.
So, a message signed by coinomi from a legacy address can be verified by other tools, but it can't be verified by itself.

Edit:
I tried this with a segwit address too and I was again successful in verifying the message using electrum.
It's weird. Because the message signed by palle11 yesterday isn't verifiable even using electrum.

[TheBeardedBaby]

Code:

 -----BEGIN BITCOIN SIGNED MESSAGE-----
Today is 11 Sept, 2022 and this is palle11 of BTT staking this address here as mine.
-----BEGIN SIGNATURE-----
bc1qk77nng4asnsvc4mk4p9nvwr0uev27slcrdqytk
H1sEeUyO5opN1JWESrxb/AUJlJJrbJGtHpQEJqjVTp+nGykjBzzJswoTg7VSCYMPPMloMrbroxdblH2HmcjwI/k=
-----END BITCOIN SIGNED MESSAGE-----

Please someone should quote and verify for me.

There's no way to verify this, at least I didn't find one.
I tried the following >

Electrum
Trezor
brainwalletx.github.io
verifybitcoinmessage.com/
Kenkarlo
MyCelium

So I give up.

[palle11]

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
Today is 13 Sept, 2022 and this is palle11 of BTT staking this address here as mine.
-----BEGIN SIGNATURE-----
17mtDab5mfK9rwup3UDmKCbaeHwuruFZKV
IN5zxE8FOEhF+ZgFSuILjaQxrgz0Wk8dbnJ8TmqqAC2wCt3JmzciX2hDm1DEhVNntMN9gg57TuwwrhREyObi7TQ=
-----END BITCOIN SIGNED MESSAGE-----

I have redone it with a legacy address from the same wallet and verified it on this site and it verified. Somebody should verify again to see if it completely verified.

[CoinEraser]

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
Today is 13 Sept, 2022 and this is palle11 of BTT staking this address here as mine.
-----BEGIN SIGNATURE-----
17mtDab5mfK9rwup3UDmKCbaeHwuruFZKV
IN5zxE8FOEhF+ZgFSuILjaQxrgz0Wk8dbnJ8TmqqAC2wCt3JmzciX2hDm1DEhVNntMN9gg57TuwwrhREyObi7TQ=
-----END BITCOIN SIGNED MESSAGE-----

Quoted and verified

[Mpamaegbu]

~snipped~

There's no way to verify this, at least I didn't find one.
I tried the following >

brainwalletx.github.io
verifybitcoinmessage.com/

So I give up.

So, what could've been the problem from your side because even palle11 verified it from verifybitcoinmessage.com/ and CoinEraser also did from one of the sites you couldn't – brainwalletx.github.io. I've read several complaints about signing from Coinomi wallet and it's worrisome to discover such inconsistency with the app. Is there no way a representative of that company can be subpoena (tagged), that's if there's a account of theirs here, to appear and explain to the community what could be going wrong?

[palle11]

~snipped~

There's no way to verify this, at least I didn't find one.
I tried the following >

brainwalletx.github.io
verifybitcoinmessage.com/

So I give up.

So, what could've been the problem from your side because even palle11 verified it from verifybitcoinmessage.com/ and CoinEraser also did from one of the sites you couldn't – brainwalletx.github.io. I've read several complaints about signing from Coinomi wallet and it's worrisome to discover such inconsistency with the app. Is there no way a representative of that company can be subpoena (tagged), that's if there's a account of theirs here, to appear and explain to the community what could be going wrong?

I think something has to be corrected here or a direction should be followed. In my own case I had to go through the legacy before I got through and I have been trying that through more than 48 hours stressing my out trying to understand what was the issue looking through space or gap as some big guys in the forum was suggesting but I was able to get through going from legacy. I think one member too went through the stress , zlantann Right?

Maybe we should just say those signing message from coinoimi should do that using legacy  

[hosemary]

So, what could've been the problem from your side because even palle11 verified it from verifybitcoinmessage.com/ and CoinEraser also did from one of the sites you couldn't – brainwalletx.github.io.

There was no problem from TheBeardedBaby's side.
palle11 signed a new message from a legacy address which was the one verified by him/her and CoinEraser.
TheBeardedBaby was trying to sign the message signed from the segwit address which can't be verified at all.

Maybe we should just say those signing message from coinoimi should do that using legecy

The best thing anyone can do is to not use coinomi.

[MArsland]

-----BEGIN BITCOIN SIGNED MESSAGE-----
Today 19/9/2022 I would like to sign my wallet from Electrum.
-----BEGIN SIGNATURE-----
bc1qaen0qmpw4j3lu83n7lzg6jncrgry7r7p0eplyl
Hz1Oiy3eXgwdUNsMxSKA/GJdx8XvDkY+4LrAP9k0yVkKb+OQOl/tMpBE7qU95N5rpR6ztGbCuKOBRnYxDGQ1J9k=
-----END BITCOIN SIGNED MESSAGE-----

Anyone can quote and verify my wallet

[LoyceV]

-----BEGIN BITCOIN SIGNED MESSAGE-----
Today 19/9/2022 I would like to sign my wallet from Electrum.
-----BEGIN SIGNATURE-----
bc1qaen0qmpw4j3lu83n7lzg6jncrgry7r7p0eplyl
Hz1Oiy3eXgwdUNsMxSKA/GJdx8XvDkY+4LrAP9k0yVkKb+OQOl/tMpBE7qU95N5rpR6ztGbCuKOBRnYxDGQ1J9k=
-----END BITCOIN SIGNED MESSAGE-----

Anyone can quote and verify my wallet

Verified in Electrum.

[Awaklara]

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
This is Awaklara = 2519096, today is September 22, 2022.
I confirmed the new BTC address 
bc1qvy7df0xtgp8hmd88y3kjkeldg7qgnwr9xas44m
-----BEGIN SIGNATURE-----
bc1q4s3pxwft09d8c3fcqnktz6mp49qcrsykrnv0ps
H3Mo18QWvGR3BiyrERIEFkFbsy69RusQerR/2XOxxvrzFXbqJT67gUJdwWGwReZaDNF1S8xzTuIfnqTludeoAjc=
-----END BITCOIN SIGNED MESSAGE-----

Please quote and verify

[BitcoinGirl.Club]

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
This is Awaklara = 2519096, today is September 22, 2022.
I confirmed the new BTC address 
bc1qvy7df0xtgp8hmd88y3kjkeldg7qgnwr9xas44m
-----BEGIN SIGNATURE-----
bc1q4s3pxwft09d8c3fcqnktz6mp49qcrsykrnv0ps
H3Mo18QWvGR3BiyrERIEFkFbsy69RusQerR/2XOxxvrzFXbqJT67gUJdwWGwReZaDNF1S8xzTuIfnqTludeoAjc=
-----END BITCOIN SIGNED MESSAGE-----

Please quote and verify

I was trying using Electrum but it fails for some reason.
Are you sure you have done everything correctly? This could be even adding or missing a white-space.

[indah rezqi]

I was trying using Electrum but it fails for some reason.
Are you sure you have done everything correctly? This could be even adding or missing a white-space.

Right, there seems to be something wrong with the signed message. I have also done the verification but it failed because the wrong signature. As shown in the image below, it is wrong.



Awaklara, can you repeat it one more time?

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
This is Awaklara = 2519096, today is September 22, 2022.
I confirmed the new BTC address bc1qvy7df0xtgp8hmd88y3kjkeldg7qgnwr9xas44m
-----BEGIN SIGNATURE-----
bc1q4s3pxwft09d8c3fcqnktz6mp49qcrsykrnv0ps
IF02EqDLxG37ILQFcWBuAFFF094EYU4+N3O4/WcIuHiLEw2oGIGN61plud4olARgtgZg4G+kOPqwjTRQCPp+1aE=
-----END BITCOIN SIGNED MESSAGE-----

Quoted and verified.

[Awaklara]

I was trying using Electrum but it fails for some reason.
Are you sure you have done everything correctly? This could be even adding or missing a white-space.

I also don't know what went wrong.
but I tried to do a new one.

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
This is Awaklara = 2519096, today is September 22, 2022.
I confirmed the new BTC address bc1qvy7df0xtgp8hmd88y3kjkeldg7qgnwr9xas44m
-----BEGIN SIGNATURE-----
bc1q4s3pxwft09d8c3fcqnktz6mp49qcrsykrnv0ps
IF02EqDLxG37ILQFcWBuAFFF094EYU4+N3O4/WcIuHiLEw2oGIGN61plud4olARgtgZg4G+kOPqwjTRQCPp+1aE=
-----END BITCOIN SIGNED MESSAGE-----

[BitcoinGirl.Club]

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
This is Awaklara = 2519096, today is September 22, 2022.
I confirmed the new BTC address bc1qvy7df0xtgp8hmd88y3kjkeldg7qgnwr9xas44m
-----BEGIN SIGNATURE-----
bc1q4s3pxwft09d8c3fcqnktz6mp49qcrsykrnv0ps
IF02EqDLxG37ILQFcWBuAFFF094EYU4+N3O4/WcIuHiLEw2oGIGN61plud4olARgtgZg4G+kOPqwjTRQCPp+1aE=
-----END BITCOIN SIGNED MESSAGE-----

I quote and confirm I was able to verify the signature successfully with Electrum.

[ABCbits]

I'm in middle of trying alternative Bitcoin full node software which have function to verify sign message, so i decide to try it with few recent staked address.

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
Today is 13 Sept, 2022 and this is palle11 of BTT staking this address here as mine.
-----BEGIN SIGNATURE-----
17mtDab5mfK9rwup3UDmKCbaeHwuruFZKV
IN5zxE8FOEhF+ZgFSuILjaQxrgz0Wk8dbnJ8TmqqAC2wCt3JmzciX2hDm1DEhVNntMN9gg57TuwwrhREyObi7TQ=
-----END BITCOIN SIGNED MESSAGE-----

I have redone it with a legacy address from the same wallet and verified it on this site and it verified. Somebody should verify again to see if it completely verified.

-----BEGIN BITCOIN SIGNED MESSAGE-----
Today 19/9/2022 I would like to sign my wallet from Electrum.
-----BEGIN SIGNATURE-----
bc1qaen0qmpw4j3lu83n7lzg6jncrgry7r7p0eplyl
Hz1Oiy3eXgwdUNsMxSKA/GJdx8XvDkY+4LrAP9k0yVkKb+OQOl/tMpBE7qU95N5rpR6ztGbCuKOBRnYxDGQ1J9k=
-----END BITCOIN SIGNED MESSAGE-----

Anyone can quote and verify my wallet

Quoted and verified with Bcoin v2.2.0

Code:

$ ./bcoin-cli --api-key=test_bcoin --http-port=48332 rpc verifymessage "17mtDab5mfK9rwup3UDmKCbaeHwuruFZKV" "IN5zxE8FOEhF+ZgFSuILjaQxrgz0Wk8dbnJ8TmqqAC2wCt3JmzciX2hDm1DEhVNntMN9gg57TuwwrhREyObi7TQ=" "Today is 13 Sept, 2022 and this is palle11 of BTT staking this address here as mine."
true
$ ./bcoin-cli --api-key=test_bcoin --http-port=48332 rpc verifymessage "bc1qaen0qmpw4j3lu83n7lzg6jncrgry7r7p0eplyl" "Hz1Oiy3eXgwdUNsMxSKA/GJdx8XvDkY+4LrAP9k0yVkKb+OQOl/tMpBE7qU95N5rpR6ztGbCuKOBRnYxDGQ1J9k=" "Today 19/9/2022 I would like to sign my wallet from Electrum."
true

[hosemary]

I lost this address a couple of weeks ago after I uninstalled the wallet and not being able to recover it since the paper I wrote the seed phrase of it was in a bunch of messy old papers and I disposed of.. This is my new address and signing

Can you sign a message from any of addresses you have used before?
Staking a new address without proving your ownership over the address you have staked before defeats the purpose of staking a bitcoin address.

You can use ninjastic.space to see the addresses you have used before.

[hosemary]

Not really sure but I might be able to prove ownership of certain addresses I used in past which are of exchange's addresses.

Note that for signing a message from a bitcoin address, you need to have full control over the address. This means that you must own the private key of the address.
The deposit address an exchange gives you isn't owned by you. That's owned by the exchange and you can't sign a message from that.