Skip to main content
Glider supports different wallet providers. This example uses a Privy EVM EOA and the default ECDSA enrollment path.

Prepare enrollment on the backend

Keep the Glider API key out of the browser:
Return only prepared.message.raw to the client.

Sign with Privy

Use the EIP-1193 provider for the selected Privy wallet. Request the personal_sign operation:
Do not UTF-8 encode, hash, or otherwise transform message.raw.

Complete enrollment on the backend

Use Privy to fund the applicable smart account. The B2B API does not have a deposit-builder route. See Fund a portfolio. For ERC-1271 or Solana enrollment, follow Two-stage enrollment instead of adapting this ECDSA example.
Do not send the Glider API key to Privy, a browser, or a wallet provider. Send only the exact signable payload to the client. The client can also receive onchain transactions that the user must review.