This is a technical account on how to integrate Sablier into your own application. If you have questions, please join the #development channel in the Sablier Discord server; our team, and members of the community, look forward to helping you.‌

What we will cover:‌

1. Smart contract architecture and ABI.

2. Networks and typical gas costs.

3. How to create, withdraw from and cancel streams.

Codebase

The Sablier protocol codebase is hosted on GitHub and the source code for each contract is verified on Etherscan.

Application Binary Interface

Depending on what web3 library you're using, you may need to get hold of the Sablier ABI (Application Binary Interface). The ABI acts as an interface between two program modules, one of which is the smart contract and the other the machine code.‌

There are two ways to obtain it:‌

1. Copy Sablier.json from sablierhq/sablier-abis.​

2. Clone sablierhq/sablier and compile the contract yourself‌.

Here's an example for how to do step 2 with yarn and truffle:

$ git clone [email protected]/sablierhq/sablier.git
$ cd ./sablier
$ yarn bootstrap
$ cd ./packages/protocol
$ truffle compile

The Sablier.json artifact should be generated in the relative build/contracts folder.‌

Networks

Depending on what Ethereum network you want to use Sablier with, you will need a different contract address. Sablier runs on top of one single master contract that manages all streams.

Testnet Tokens

If you want to use the Sablier interfaces on a testnet, you need to get some testnet DAI first. To do this, you have to go to the Etherscan page of the associated token, tap the "Write Contract" tab, connect your Ethereum wallet and call the mint method. Note that the token has 18 decimals, so you may want to use a unit converter.

Gas Costs

The gas usage of the Sablier protocol is not deterministic and varies by user. Calls to third-party contracts, such as ERC-20 tokens, may use an arbitrary amount of gas. We provide the table below for guidance:

Data

Our blockchain data can be accessed via our subgraphs, which you interact with via a GraphQL client. We recommend Apollo.

If you want to see some example queries, see the README at sablierhq/sablier-subgraph.