Rabet

Rabet is useful to developers who want to keep application requests separate from wallet approval. After installation, a website can detect window.rabet. Its connection button should call rabet.connect only after a user action and remain disabled while the request is pending.

A confirmed connection returns the active public key. Rabet’s privacy setting affects this step: if privacy mode is disabled, the key can be returned without a separate approval prompt. Receiving an address is not permission to move its assets.

For signing, the application supplies an encoded Stellar transaction, called XDR, and explicitly selects mainnet or testnet. Rabet decodes the request for review. If the user approves, it returns the signed transaction; the application must then submit that result to the network. Calling the signing method before connecting produces a not-connected error.

The distinction matters when debugging an apparent failure. Check whether the application obtained an address, received a signature or actually submitted the signed result. These are separate stages. Rabet’s disconnect method ends the application connection, requiring a new connection request for later interaction.

The extension repository is licensed under GPL version 3. This gives developers a published basis for inspecting and adapting the code. It does not make a connected trading application or its assets safe; a signed transaction can have financial consequences, and tokens can lose value. Rabet’s privacy policy also requires parental consent or supervision for users below their jurisdiction’s age of majority.