What’s the Vesting Scheduler?

The Vesting Scheduler smart contract allows you to set up a vesting schedule of tokens for a specific recipient. The Vesting Scheduler contract is non-custodial, it does not hold any tokens, rather it uses permissions to move them from your wallet (or Safe).

The Vesting Scheduler comes with the option to add a cliff date (and amount), after which it vests tokens linearly sending them to the recipient via a by-the-second Superfluid stream (the receiver does not need to claim as these tokens will appear directly in their wallet).

Setting up vesting schedules via the Vesting Scheduled contract will soon be possible directly on the Superfluid Dashboard, however you can already do so by interacting with the contract directly in conjunction with off-chain automations (detailed in documentation here).

Why Automate Vesting with Superfluid?

Superfluid Protocol allows you to set up a linear vesting schedule with (or without) a cliff while keeping all the to-be-vested tokens in your wallet or Safe (to limit any exposure to our protocol smart contracts).

In a nutshell:

• Set up linear vesting with (or without a cliff)
• Specify both a custom cliff date/time and a custom cliff amount
• Specify your custom total vesting amount and its time framework
• Keep all tokens in your wallet (or Safe) until they are sent directly to the recipient
• I.e. “I’d like to set up a 4 years vesting schedule, that sends 4000 AMZNx linearly with a cliff of 1 year for 1000 AMZNx”

Example:

1. It’s January 1st. You are essentially looking to vest 400 AMZNx to Alice from February 1st to June 1st, with linear vesting and a one month cliff.

   To do so, you schedule vesting for an employee with the below details:

   1. To: Alice’s account
   2. Start Date: February 1st
   3. Cliff Date: March 1st
   4. End Date: June 1st
   5. Cliff Amount: 100 AMZNx
   6. Flow Rate: 100 AMZNx/mo.

1. It’s March 1st and the cliff amount is transferred to Alice and the vesting stream begins

Note: there were no actions to be taken on the Feb. 1st start date as a cliff date was provided