Hi everyone 
Summary
As announced in the Global R&D of January 2025, DFINITY is working on a Solana RPC canister that will leverage HTTPs outcalls to interact with the Solana blockchain. This canister will be managed as a service (under NNS control) and will extend the Chain Fusion capabilities of ICP. Together with the already available support for threshold EdDSA signatures, the Helium milestone will be complete.
What to expect
You can expect a similar experience in terms of features and API as offered by the EVM RPC canister for EVM chains. In particular:
- The canister will be under NNS control, where API keys will be managed by DFINITY.
- Developers can pay for their requests with cycles and do not need to manage API keys or JSON RPC providers.
- No single point of failure: by default, multiple providers are queried and their responses aggregated.
- To make it easy to use, we plan on building a client to facilitate the interaction with the SOL RPC canister and also provide various examples.
Supported RPC methods
The list of methods that we plan to support at launch is not set in stone but would currently include the following:
- getAccountInfo
- getBlock
getLatestBlockhash: currently cannot be supported directly with HTTPs outcalls due to fast changing responses, which would often result in consensus errors. There are some workarounds as mentioned here.- getRecentPrioritizationFees
- getSignatureForAddress
- getSignatureStatuses
- getSlot
- getTokenAccountBalance
- getTransaction
- sendTransaction
Remarks:
- Do chime in
if you have a use case in your dapp for a method that is not in the list. As for the EVM RPC canister, we also plan to have a generic method to forward any JSON payload so that the lack of support for some specific method at launch does not constitute a blocker.
Related projects
Special thanks 
to ic-solana which paved the way to interact with Solana via HTTPs outcalls. As far as we are aware of, the developers of that project do not intend to run it as a service. How much code will be shared between both canisters is yet to be defined, but it should not impact users of the SOL RPC canister (this is a pure implementation detail).