Skip to main content

Configure Your Local Environment

In this guide, we will go through the steps to set up a local development environment for building onchain integrations with Flow. We will use Foundry to install Flow as a dependency, and run a few simple tests.

At the end, you’ll have a development environment set up that you can use to build the rest of the examples under "Guides", or start your own integration project.

Pre-requisites

You will need the following software on your machine:

In addition, familiarity with Ethereum and Solidity is requisite.

Quick start

We put together a template repository that you can use to get started quickly. This repository features a basic project structure, pre-configured Flow imports, and a selection of sample contracts and tests.

tip

Make sure you are using the latest version of Foundry by running foundryup.

To install the template, simply execute the following commands:

$ mkdir sablier-integration-template
$ cd sablier-integration-template
$ forge init --template sablier-labs/sablier-integration-template
$ bun install

Then, hop to the Run a Fork Test section to complete your set up and start developing.

Start from scratch

Foundry is a popular development toolkit for Ethereum projects, which we have used to build the Sablier Protocols. For the purposes of this guide, Foundry will provide us with the tooling needed to compile and test our contracts.

Let's use this command to spin up a new Foundry project:

$ forge init my-project
$ cd my-project
note

You might notice that the CLI is forge rather than foundry. This is because Foundry is a toolkit, and forge is just one of the tools that comes with it.

Once the initialization completes, take a look around at what got set up:

├── foundry.toml
├── script
├── src
└── test

The folder structure should be intuitive:

  • src is where you'll write Solidity contracts
  • test is where you'll write tests (also in Solidity)
  • script is where you'll write scripts to perform actions like deploying contracts (you guessed it, in Solidity)
  • foundry.toml is where you can configure your Foundry settings, which we will leave as is in this guide

Let's install the FLow Node.js packages using Bun:

$ bun add @sablier/flow

Bun will download the Flow contracts, along with their dependencies, and put them in the node_modules directory.

Let's remap the package names to point to the installed contracts. This step is required so that the Solidity compiler can find the Flow contracts when you import them:

$ echo "@sablier/flow=node_modules/@sablier/flow/" >> remappings.txt
$ echo "@openzeppelin/contracts/=node_modules/@openzeppelin/contracts/" >> remappings.txt
$ echo "@prb/math/=node_modules/@prb/math/" >> remappings.txt

That's it! You should now have a functional development environment to start building onchain Flow integrations. Let's run a quick test to confirm everything is set up properly.

Sample contract

Delete the src/Counter.sol and test/Counter.t.sol files generated by Forge, and create a new file: src/FlowStreamCreator.sol.

Paste the following code into src/FlowStreamCreator.sol.

Flow Stream Creator
loading...

Let's use Forge to compile this contract:

$ forge build

If the contract was compiled correctly, you should see this message:

[⠢] Compiling...
[⠰] Compiling { number } files with { compiler }
[⠒] Solc { compiler } finished in { time }
Compiler run successful
info

The minimum Solidity version supported by the Flow contracts is v0.8.13.

Next steps

Congratulations! Your environment is now configured, and you are prepared to start building. Explore the guides section to discover various Flow features available for integration.

As far as Foundry is concerned, there is much more to uncover. If you want to learn more about it, check out the Foundry Book, which contains numerous examples and tutorials. A deep understanding of Foundry will enable you to create more sophisticated integrations with Flow.