Practical overview
When it fits
Use it when your work requires repository-level Solidity contracts and development workflows for Ethereum DeFi, especially fork-based testing or the documented Hardhat deployment and verification tasks.
Who it is for
- Solidity developers working on Ethereum DeFi contracts
- Teams prototyping or extending DeFi smart-contract systems
- Developers who need fork-based testing or documented contract deployment tasks
Documented uses
- Study or reuse contracts related to the Defi Saver ecosystem
- Compile and test Solidity contracts with Foundry or Hardhat
- Run tests against a forked Ethereum mainnet state
- Flatten, verify and deploy selected contracts through Hardhat tasks
- Deploy selected contracts to a Tenderly fork
Requirements & limits
The repository is public and specifies an MIT license. Fork-based workflows require environment configuration and a mainnet RPC URL; Tenderly fork deployment requires a Tenderly fork ID.
- It is a developer repository, not a documented end-user DeFi interface.
- It supports both Foundry and Hardhat workflows.
- Tests use forked mainnet state and may depend on the selected fork block.
- Deployment and verification are exposed through custom Hardhat tasks.
- The repository uses Solidity and targets Ethereum-related DeFi development.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Run the repository’s fork-based Foundry tests
Set up the repository and run its Foundry tests against a forked Ethereum mainnet state.
Before you start
- Foundry installed
- A mainnet RPC URL
- A repository .env file based on .env.example
- Repository dependencies installed with Yarn and Foundry dependencies
Steps
Run yarn in the repository folder and create .env from .env.example.
Set ETHEREUM_NODE in .env to a mainnet RPC URL.
Install Foundry dependencies with forge install foundry-rs/forge-std dapphub/ds-test.
Run forge test; select a fork block in test-sol/config/config.json when needed.
Expected outcome
The repository’s Foundry test suite is invoked against a forked mainnet state.
Guide limitations
- The README notes that tests run from a forked mainnet state, so an RPC URL and environment configuration are required.
- Changing the fork block can affect test behavior.
Deploy selected contracts on a Tenderly fork
Use the documented Hardhat task to deploy specified contracts to a Tenderly fork.
Before you start
- Repository dependencies and environment configuration
- A Tenderly fork ID entered in .env
- The required Hardhat setup
Steps
Prepare the repository and its .env configuration.
Add the Tenderly fork ID to .env.
Run npx hardhat deployOnFork followed by the selected contract names.
Expected outcome
The selected contracts are submitted through the repository’s Tenderly-fork deployment task.
Guide limitations
- The README requires a Tenderly fork ID and environment configuration.
- The source documents the task but does not establish deployment success for a particular environment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- defisaver/defisaver-v3-contracts · Official homepage title · retained in its source language