A tutorial on how to use Privy with the Glider API
The Glider API is wallet agnostic. This means that as long as you can get an EIP-191 signature from the EOA that will own the portfolio, you can use the Glider API.
If you’ve followed along with the Quickstart guide you will notice there’s two cases where your wallet architecture will need to interface with Glider. The first is when you’re creating a portfolio, and the second is when you’re funding a portfolio.
During the Portfolio Creation process, an EIP-191 signature is required to authenticate ownership of the portfolio and provide Glider access to manage the assets within the portfolio.
Fetch the data to be signed by calling the https://api.glider.fi/v1/portfolio/create/signature
endpoint.
Sign the message with the owner’s wallet. Privy provides a tutorial on signing a message through their SDKs.
This will likely require end user interaction to complete the signature.
Funding a portfolio is done by sending funds to a portfolio’s vault address. Follow along with Privy’s docs on sending a transaction for your specific situation.
Fetch the portfolio’s vault address by calling the https://api.glider.fi/v1/portfolio/{portfolioId}
endpoint.
Privy provides support for EVM smart wallets. However, smart wallets as owners of portfolios are not yet supported by Glider.
An alternative to using Privy’s SDKs is to use Viem for funding and message signing. Privy provides a tutorial on interfacing with Viem. By creating a Wallet Client you’ll be able to sign messages and send transactions for the portfolio owner.
A tutorial on how to use Privy with the Glider API
The Glider API is wallet agnostic. This means that as long as you can get an EIP-191 signature from the EOA that will own the portfolio, you can use the Glider API.
If you’ve followed along with the Quickstart guide you will notice there’s two cases where your wallet architecture will need to interface with Glider. The first is when you’re creating a portfolio, and the second is when you’re funding a portfolio.
During the Portfolio Creation process, an EIP-191 signature is required to authenticate ownership of the portfolio and provide Glider access to manage the assets within the portfolio.
Fetch the data to be signed by calling the https://api.glider.fi/v1/portfolio/create/signature
endpoint.
Sign the message with the owner’s wallet. Privy provides a tutorial on signing a message through their SDKs.
This will likely require end user interaction to complete the signature.
Funding a portfolio is done by sending funds to a portfolio’s vault address. Follow along with Privy’s docs on sending a transaction for your specific situation.
Fetch the portfolio’s vault address by calling the https://api.glider.fi/v1/portfolio/{portfolioId}
endpoint.
Privy provides support for EVM smart wallets. However, smart wallets as owners of portfolios are not yet supported by Glider.
An alternative to using Privy’s SDKs is to use Viem for funding and message signing. Privy provides a tutorial on interfacing with Viem. By creating a Wallet Client you’ll be able to sign messages and send transactions for the portfolio owner.