Sablier relies on specific dependencies to source data or manage off-chain flows. All of these are either public or fully open-source, so feel free to roam around and suggest improvements or optimizations where needed.
As an alternative to reading data from the contracts or listening to onchain events, we use a set of subgraphs and indexers. These act as a middleware between the chain and our interfaces and allow for caching, formatting and querying data.
For every The Graph subgraph you will find a dedicated Envio indexer that mirrors its functionality and can be used as a fallback or as a completely alternative query engine.
Read more about The Graph here.
Sablier supports multiple chains for which we've deployed subgraphs at either the Hosted Network level or within the Decentralized Network (see Ethereum, Arbitrum or Polygon's endpoints).
The Protocol subgraph watches over the core functionality of Sablier V2. It handles events such as Create Stream,
Withdraw or Transfer.
Documentation and Endpoints.
The Merkle subgraph watches over the Merkle Lockup functionality from Sablier V2's periphery contracts. It handles
events such as Create Campaign, Claim or Clawback. In the client interfaces it is used to track activity for
Airstreams.
Documentation and Endpoints.
Read more about Envio here.
Warning
The Sablier V2 indexers (Envio) are still under development and are not used in production for now. Feel free to read the docs or preview the implementation while we finish the stable integration.
The Protocol-Envio indexer watches over the core functionality of Sablier V2. It handles events such as
Create Stream, Withdraw or Transfer.
Documentation and Endpoints.
The Merkle-Envio subgraph watches over the Merkle Lockup functionality from Sablier V2's periphery contracts. It
handles events such as Create Campaign, Claim or Clawback. In the client interfaces it is used to track activity
for Airstreams.
Documentation and Endpoints.