Lantern
Yellowstone gRPC Support
Overview
Lantern supports Yellowstone gRPC as well. By default, you can access this feature on port 8090.
You can use any standard Yellowstone gRPC client to connect. We support subscribing to accounts, slots, transactions, blocks, and owners. What you can subscribe to depends on what you have configured Lantern to cache. For example, you won't be able to subscribe to blocks unless Lantern is caching blocks. Subscribing to transactions requires that Lantern is caching full blocks.
Why Use Lantern with Yellowstone?
One reason to do this instead of using Yellowstone directly with FluxRPC is that the protocol Lantern uses to stay up-to-date with FluxRPC consumes less bandwidth. Another is when you have several applications that need similar data from yellowstone, and want to avoid paying for the bandwidth costs multiple times for the same data.
In other words, using Lantern + FluxRPC as the source for your Yellowstone data will use less bandwidth than connecting your Yellowstone client directly to FluxRPC.
Lower Bandwidth
Lantern's sync protocol uses less bandwidth than direct Yellowstone connections
Local Caching
Benefit from Lantern's local cache while using Yellowstone protocol
Connection Details
Connect your Yellowstone gRPC client to:
localhost:8090Or the appropriate host if running Lantern remotely. Make sure port 8090 is accessible to your client application.
Supported Features
Lantern's Yellowstone implementation currently supports:
- Subscribing to accounts
- Subscribing to owners (program accounts)
- Subscribing to blocks (if Lantern is caching blocks)
- Subscribing to transactions (if Lantern is caching full blocks)
- Subscribing to slots (if Lantern is caching slots)
- Standard filters