@sablier/deployments

Sablier Deployments

This repository keeps track of Sablier deployment bundles, each of which includes:

• Contract artifacts and ABIs.
• The broadcast directories generated by Foundry upon running the deploy scripts.

The deployments are indexed by:

• Repository ("lockup" or "flow")
• Version name (e.g. "v1.0.0")
• Artifacts
• Broadcasts, which in turn are indexed by chain name.

If you need the deployment addresses, you can find them in the docs.

Background

Sablier Protocols have been built, tested, formatted, and deployed with the Foundry smart contract development toolchain.

To learn more about Foundry, see the Foundry Book.

To learn more about Sablier, see the Sablier Docs.

Addresses

To view the deployment addresses, use the links below.

• Airdrops deployment addresses
• Lockup deployment addresses
• Flow deployment addresses

Packages

The contract artifacts and the ABIs are published as NPM packages:

• @sablier/airdrops
• @sablier/lockup
• @sablier/flow

Older versions of Lockup (before v2.0.0) and Airdrops (before v1.3.0) have been published through these packages:

• @sablier/v2-core
• @sablier/v2-periphery

Scripts

The contracts have been deployed using these scripts:

• airdrops/script
• lockup/script
• flow/script

Specifically, with the "DeployDeterministic" scripts, which rely upon this CREATE2 factory:

• https://github.com/Arachnid/deterministic-deployment-proxy

Differentiation

The rationale for using CREATE2 is not to generate deterministic deployment addresses - quite the opposite. The goal is to have different addresses on each chain. By using CREATE2, we can systematically differentiate the contract addresses by passing a salt, whereas if we had used CREATE, the deployer's nonce would have impacted the resulting deployment address.

License

This repo is licensed under GPL 3-0 or later.

Sablier Deployments UI

This repository includes a UI for exploring the Sablier Protocol deployments built with Next.js and TailwindCSS.

Setup and Usage

The UI is located in the ui directory. To get started:

• Run the script to copy data from the source to the UI:

chmod +x scripts/copy-to-ui.sh
./scripts/copy-to-ui.sh

• Install dependencies and start the development server:

cd ui
bun install
bun dev

• Open http://localhost:3000 to view the UI in your browser.

See the README in the ui directory for more detailed instructions.