Practical overview
When it fits
Use it when developing Solidity contracts that need on-chain ERC-20 vesting with a cliff and gradual release, and when the documented Forge or Hardhat development workflow fits your project.
Who it is for
- Solidity developers adding on-chain ERC-20 vesting to a project.
- Teams that need gradual token release with a cliff and vesting period.
- Developers who want an optional owner-controlled revocation design.
Documented uses
- Structure gradual ERC-20 token release in a smart contract.
- Include a cliff and vesting period in the release schedule.
- Choose an owner-revocable schedule design.
- Compile, test, and generate contract documentation using Forge and Hardhat.
Requirements & limits
The repository is public and released under the Apache-2.0 license.
- The vesting design includes both a cliff and a vesting period.
- Revocation is optional and controlled by the owner.
- Hardhat use depends on running Forge installation and build steps first.
- The README documents compilation, tests, ABI and documentation generation, coverage, and contract-source verification.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and compile the contracts with Forge
Install the repository dependencies and compile the contracts using Forge.
Before you start
- A local checkout of the repository
- Forge
Steps
Run
forge installto install dependencies.Run
forge buildto compile.
Expected outcome
The repository dependencies are installed and the contracts are compiled with Forge.
Guide limitations
- The instructions document installation and compilation, not deployment or schedule creation.
Compile and generate contract documentation with Hardhat
Use the documented Forge and Hardhat sequence to compile contracts and generate their documentation.
Before you start
- A local checkout of the repository
- Forge
- Yarn
Steps
Run
forge install.Run
forge buildbefore using Hardhat.Run
yarnto install the Hardhat dependencies.Run
yarn compileto compile contracts and generate the documented outputs.
Expected outcome
Hardhat compiles the contracts, exports ABI files to `build/abi`, and generates documentation in `docs`.
Guide limitations
- The README says Forge must be installed and built first so Hardhat can load dependency contracts.
- This procedure does not deploy contracts or configure a vesting schedule.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- AbdelStark/token-vesting-contracts · Official homepage title · retained in its source language

