Skip to content
KeyProof
Home / Wallet how-tos / Rabby

Sign a message with Rabby

Rabby supports personal_sign requests from websites. It shows the message and the requesting site, and it refuses the dangerous legacy eth_sign method. As with MetaMask, you sign through an app's connect flow or KeyProof's local signer.

Your keys never leave your wallet. Never paste your recovery words anywhere, including KeyProof. Signing a message is not a transaction.

Chains: Ethereum and EVM chains
Signature format: personal_sign (EIP-191). It produces a 0x-prefixed, 65-byte hex signature.

Sign with KeyProof's local signer[1]

These steps use KeyProof's browser-wallet signer (personal_sign). Rabby supports personal_sign in its open-source provider controller; on-screen labels in Rabby may differ by version.

  1. Open KeyProof's Verify page and paste the exchange's exact message.
  2. Click "Sign with browser wallet" and approve the connection in Rabby.
  3. Rabby shows a "Sign Text" request. Check the site and the message, then sign.
  4. KeyProof verifies the signature locally and fills in the proof record.

Tips

Check my signature in the verifier

Sources

Last checked 2026-10-27. Numbers in brackets [n] in the text refer to this list.

  1. Rabby source: provider controller (personal_sign handling) (official)

KeyProof is not affiliated with Rabby. Wallet interfaces change, so follow your wallet's current documentation. Not legal or financial advice.