Skip to main content

Price oracle

At its core, Lido on Solana (“Solido” for short) enables converting SOL into stSOL and back. This conversion involves an exchange rate. The exchange rate used by Solido is stored on-chain in the Solido instance itself. This page explains how to access it. To understand how the exchange rate is set, see the internals page about the exchange rate.

On-chain​

note

The details in this section are based on v1.0.0 of the Solido program. Please confirm that this information is still up to date before building on it. The source code is always the source of truth. For v1.0.0, the relevant field is Lido::exchange_rate.

Solido stores two values that together determine the exchange rate:

  • The amount of stSOL in existence, st_sol_supply.
  • The amount of SOL managed, sol_balance.

Both are represented as a little-endian u64 that holds the number of lamports. st_sol_supply is stored in in the Solido account data at byte 73..81, and sol_balance is stored at byte 81..89. The address of the official Solido instance is listed on the deployments page.

Byte 0 of the Solido account data is a version byte. If we make changes to the data layout of the Solido account, we will bump the value of this byte. You can use this to block transactions after we update Solido, to prevent reading garbage data.

To extract the on-chain data, you can use the following libraries:

  • Rust: The solido crate
  • Typescript: A library is in progress, follow this issue for details.
  • If you are interested in other ways to extract the on-chain data, feel free to open an issue and we might be able to help you out.

HTTP API​

At the moment we do not expose a stable http API for requesting the current exchange rate, but we might support one if there is demand for it. Feel free to open an issue if you are interested.

Prometheus​

The maintenance daemon exposes details about the Solido instance at a Prometheus /metrics endpoint. These metrics include Solido’s current exchange rate. You will need to run an instance of the maintenance daemon yourself to access these metrics; the endpoint is not intended to be exposed to the public internet.