Skip to main content

Governance

Comptroller

The Sablier Protocol uses a Comptroller smart contract architecture for governance. The Comptroller acts as an intermediary that has exclusive access to specific protocol functions. This design provides a more flexible and centralized accross all protocols access control model while maintaining security.

ChainAddress
Abstract0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Arbitrum0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Avalanche0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Base0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Berachain0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Blast0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
BNB Chain0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Chiliz0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Core Dao0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Ethereum0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Gnosis0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
HyperEVM0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Lightlink0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Linea Mainnet0xF21b304A08993f98A79C7Eb841f812CCeab49B8b
Mode0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Morph0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
OP Mainnet0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Polygon0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Scroll0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Sei Network0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Sonic0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Superseed0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
Unichain0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
XDC0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399
ZKsync Era0x0000008ABbFf7a84a2fE09f9A9b74D3BC2072399

Lockup

Comptroller has the following permissions on each chain where Lockup is deployed:

PermissionFunction
Allow to HookallowToHook
Recoverrecover
Set Native TokensetNativeToken
Set NFT DescriptorsetNFTDescriptor

TODO: Add links when reference pages are created

MerkleFactory

Comptroller has the following permission on each chain where the factories are deployed:

PermissionFunction
Set Native TokensetNativeToken

TODO: Add links when reference pages are created

Flow

Comptroller has the following permissions on each chain where Flow is deployed:

PermissionFunction
Recoverrecover
Set Native TokensetNativeToken
Set NFT DescriptorsetNFTDescriptor

TODO: Add links when reference pages are created

Admin Addresses

Before the introduction of the Comptroller architecture, we used a direct "Admin" role for governance. These admin accounts had the same authority as the current Comptroller contract, with direct access to specific protocol functions. More concretely, the Admin is a collection of multisig wallets and EOAs currently in control of Sablier Labs.

ChainAddress
Abstract0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Arbitrum0xF34E41a6f6Ce5A45559B1D3Ee92E141a3De96376
Avalanche0x4735517616373c5137dE8bcCDc887637B8ac85Ce
Base0x83A6fA8c04420B3F9C7A4CF1c040b63Fbbc89B66
Berachain0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Blast0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
BNB Chain0x6666cA940D2f4B65883b454b7Bc7EEB039f64fa3
Chiliz0x74A234DcAdFCB395b37C8c2B3Edf7A13Be78c935
Core Dao0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Ethereum0x79Fb3e81aAc012c08501f41296CCC145a1E15844
Gnosis0x72ACB57fa6a8fa768bE44Db453B1CDBa8B12A399
HyperEVM0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Lightlink0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Linea Mainnet0x72dCfa0483d5Ef91562817C6f20E8Ce07A81319D
Mode0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Morph0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
OP Mainnet0x43c76FE8Aec91F63EbEfb4f5d2a4ba88ef880350
Polygon0x40A518C5B9c1d3D6d62Ba789501CE4D526C9d9C6
Scroll0x0F7Ad835235Ede685180A5c611111610813457a9
Sei Network0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Sonic0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Sophon0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Superseed0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Tangle0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
Unichain0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
XDC0xb1bEF51ebCA01EB12001a639bDBbFF6eEcA12B9F
ZKsync Era0xaFeA787Ef04E280ad5Bb907363f214E4BAB9e288

PR NOTE: I didn't add functions for the previous versions, since we won't have contract references for them.

Trustlessness

Despite having an admin, the Sablier Protocol remains trustless. Here's why:

  1. The protocol is permissionless, i.e. it can be freely accessed by anyone with an Internet connection.
  2. The protocol is persistent, i.e. the admin cannot pause it.
  3. The streaming logic is non-upgradeable, i.e. the admin cannot tamper with the streams created by users.
  4. There are no escape hatches that allow the admin to claim user funds.
  5. There is a hard-coded upper limit of 10% to the fees that the admin can charge.

Timelocks

The parameter changes that can be effected are NOT subject to a timelock. This means that the admin can execute any of the functions listed above at any time.

Governance

As a startup, Sablier has to deal with uncertainty regarding:

  1. Protocol-market fit
  2. Smart contract security

Attaining success in these areas is no easy feat, and as such, decentralizing the protocol's governance will not be an initial priority.

Nonetheless, we believe that progressive decentralization is the most effective approach to scaling a smart contract protocol. As the protocol matures, we will decentralize its governance incrementally.