Overview

Connect your dapp to Freighter Mobile using the WalletConnect v2 protocol. All methods follow the standard JSON-RPC 2.0 request/response format over a WalletConnect session.

Supported Chains

Network	Chain ID
Mainnet (PUBLIC)	stellar:pubnet
Testnet	stellar:testnet

API Reference

Method	Description
stellar_signXDR	Sign a transaction and return the signed XDR
stellar_signAndSubmitXDR	Sign and submit a transaction to Horizon
stellar_signMessage	Sign an arbitrary UTF-8 message (SEP-53)
stellar_signAuthEntry	Sign a Soroban authorization entry preimage (as defined in SEP-43)

Error Handling

All error responses use JSON-RPC 2.0 format with code 5000:

{
  "id": 1234567890,
  "jsonrpc": "2.0",
  "error": {
    "code": 5000,
    "message": "User rejected the request"
  }
}

Freighter Mobile validates that the chainId in the request matches the wallet's active network. If the user is on the wrong network, the request is rejected. Always specify chainId as a separate argument to provider.request(), not inside params.

Security

Freighter Mobile uses Blockaid scanning to protect users:

Scan type	When it runs
Site scan	Once during WalletConnect session connection
Transaction scan	For stellar_signXDR and stellar_signAndSubmitXDR requests

stellar_signMessage and stellar_signAuthEntry do not trigger additional scans — the site was already scanned during connection.

See also

• WalletConnect v2 Docs
• Stellar Smart Contracts Auth
• SEP-53: Message Signing
• SEP-43: Auth Entry Signing