Airdrops Endpoints
Merkle API
Sablier Airdrops rely on pre-configured Merkle trees to hold the list of recipients and their individual claim details. To build the Merkle tree and generate recipient proofs, we use a web2 API.
For full details about the Merkle API, check out the next section. You can also explore the source code on GitHub:
Indexers
The following indexers (Envio, The Graph) track the events emitted by the Sablier Airdrops contracts, specifically the ones in charge of Merkle distributions. It deals with airdrops-specific actions like the factory creating an airstream campaign, admin clawbacks, or users claiming stream NFTs as defined in the attached Merkle tree.
Airdrops work in tandem with our Vesting feature since some Merkle distributions will produce new Lockup streams.
Envio
Source Code
Endpoints
| Chain | Endpoint |
|---|---|
| All Chains | https://indexer.hyperindex.xyz/508d217/v1/graphql |
"All Chains" means most of the chains supported by Sablier, e.g., Ethereum Mainnet, Optimism, Polygon. The full list can be found here.
The endpoint is meant to be plugged into a query client. Use Hasura's online explorer to view the entities and query API.
As you can see, Envio offers a single API endpoint that aggregates data across all chains. This approach differs from other indexers like The Graph, which require separate subgraphs for each chain where Sablier is deploye
The Graph
Source Code
Endpoints
The Decentralized Network subgraphs operate on The Graph Network, so the links in the table below contain a placeholder for an API key. Here's an example:
https://gateway.thegraph.com/api/API_KEY/subgraphs/id/AvDAMYYHGaEwn9F9585uqq6MM5CfvRtYcb7KjK7LKPCt
You have to replace the API_KEY placeholder with your own API key. To create your API key, check out
this guide.
If you don't see your chain in this table, it means that there is no subgraph available for it. You can use the Envio indexer instead.