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:
Smart contract architecture and ABI
Networks and typical gas costs
How to create, withdraw from and cancel streams
How to create, withdraw from and cancel "compounding" streams
The Sablier protocol codebase is hosted on GitHub and the source code for each contract is verified on Etherscan.
We designed the protocol with simplicity in mind: one monolith smart contract that adheres to the ERC-1620 standard. In our web interfaces, we rely on a few other proxies, but we will not cover those here.
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:
Sablier.json from sablierhq/sablier-abis
Clone sablierhq/sablier and compile the contract yourself
$ git clone firstname.lastname@example.org/sablierhq/sablier.git$ cd ./sablier$ yarn run bootstrap$ cd ./packages/protocol$ truffle compile
Sablier.json artifact should be in the relative
Depending on what Ethereum network you want to use Sablier with, you will need a specific contract address.
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:
Typical Gas Cost
Withdraw from Stream
Create "Compounding" Stream
Withdraw from "Compounding" Stream
Cancel "Compounding" Stream
Our blockchain data can be accessed via our subgraphs, which require you to use a GraphQL client. We recommend Apollo.
If you want to see some example queries, see sablierhq/sablier-subgraph.