Token cliff

Description: A Liftoff Program member has requested a way for a token cliff feature. This feature enables a Sender to decide when a Recipient begins to receive vested tokens. This is common in token equity deals and certain forms of payments. There are different scenarios for when/if a Sender can cancel a contract and who can transfer the contract's tokens after the cliff is met.

Story ROI: This feature supports Web3 Treasury management via Alberto that was requested by a customer and is valuable to Lifted internally as well.

As a company, I want the Recipient to start receiving tokens at a certain data and time so that incentives are aligned.

• Should be achievable via many-rs.
• Should be able to set a cliff date and time for when the tokens begin vesting.
• Should be able to input the token that will be transferred.
• Should be able to input the number of tokens that will be vested on the cliff date and time.
• Should be able to input the Recipient's address that will receive of the tokens.
• Should be able to transact tokens after they are received by the Recipient unless "locked" or frozen.
• Should be able to input a Contract Title.
• Should be able to cancel the Contract by the Sender.
• Should be deployed to dev.
• Should be able to be demoed.

Questions:

• Should we allow the Recipient to be able to transfer the contract?

Example from https://streamflow.finance/:

Review the token-cliff requirements and the unresolved question about whether the Recipient can transfer the contract; no implementation files or tests are identified. Start by defining the cancellation, transfer, locking, and vesting rules, then scope the dev deployment and demo checks.