Public repo for Yellowstone-Fumarole
cargo install yellowstone-fumarole-cliSee yellowstone fumarole cli documentation
We offer a simple fumarole Rust client crate in crates/yellowstone-fumarole-client.
An example can be found in examples/rust/client.rs.
See rust example README for more details.
Unlike Dragonsmouth, you can consume data at your own pace, since Fumarole uses a polling approach at its core.
However, it is important you don't over commit to the amount of data you want to subcribe to.
Fumarole does not store data forever and if you are too slow to make progress in your subscriber session, your TCP connection will be interrupt because of staleness.
See examples/rust folder.
Here's a comparison table between the Two
| gRPC | Persisted | Stateful | |
|---|---|---|---|
| Fumarole | ✅ | ✅ | ✅ |
| Dragonsmouth | ✅ | ❌ | ❌ |
Wallet Apps, dApps, indexer.
Fumarole puts more emphasis on reliability and availability. Compare to yellowstone-grpc, slot latency will be higher.
We are aiming at three (3) slot behind on avg for Fumarole as its main purpose is to provide more reliable and forgiving geyser data source.
NOTE: slot latency exclude client side latency to download and process the whole slot. slot latency refers to the difference between the chain-tip and what Fumarole has register internally so-far.