Supported RPC methods

All RPC Methods are Supported

Lantern will respond to all Solana RPC methods. If it's not able to answer from local cache, or if the cache could be out of date, it will simply forward the request to FluxRPC and you will receive a response normally.

If you send many identical requests, Lantern will avoid making duplicate RPC calls where possible.

RPC Calls Served from Cache

Lantern's main advantage is being able to quickly answer RPC calls using its local cache. Right now, it will answer the following RPC calls from local cache if possible:

getAccountInfo getMultipleAccounts getProgramAccounts getBalance

We are continually working to extend this list to include more methods.

Lantern can cache the SYSVAR program. This would let you keep data like current slot, block, and recent blockhashes cached. You can then query this info with getAccountInfo.

Sending Transactions with Lantern

Lantern is capable of sending your transactions directly to validators. This is faster than using an RPC to send your transaction — in that case, your request would have to be transmitted and processed twice: one to your RPC provider, and again to the correct validator.

To use this feature, simply make a valid sendTransaction RPC call to Lantern.

This feature is in beta, requiring at least Lantern version v0.0.4-beta. Please reach out if you experience any issues.

One important thing to remember is that we only send the transaction — choosing the correct priority fees and verifying that it made it's way on-chain is up to your application.