Skip to main content

Errors

Background​

Sablier protocols handle errors with the convenient and gas-efficient custom error syntax introduced in Solidity v0.8.4.

The error data encoding is identical to the ABI encoding used for functions, e.g.:

error SablierV2Lockup_Unauthorized(address caller, uint256 streamId);

Yields the following 4-byte selector in the contract's ABI:

bytes4(keccak256(bytes("SablierV2Lockup_Unauthorized(address,uint256)")))
// 0xe10e8f6f

Naming Pattern​

With the exception of a few generics, all errors in Lockup protocols adhere to the naming pattern SablierV2<ContractName>_<ErrorName> whereas in Flow protocol, they adhere to SablierFlow_<ErrorName>.

Incorporating the contract name as a prefix offers context, making it easier for end users to pinpoint the contract responsible for a reverted transaction. This approach is particularly helpful for complex transactions involving multiple contracts.

Lockup Error List​

Core​

Click here to see the full error list in Lockup Core.

Periphery​

Click here to see the full error list in Lockup Periphery.

Flow Error List​

Coming soon.

Resources​