Practical overview
When it fits
Use it when the task involves the contract layer behind OUSD or OETH, Foundry-based development, or local DeFi integration testing against an Anvil mainnet fork.
Who it is for
- Smart-contract developers working with Solidity and EVM-based DeFi.
- Teams inspecting or adapting yield-accruing stablecoin contract architecture.
- Developers testing integrations with the repository’s named DeFi venues.
Documented uses
- Develop and inspect OUSD and OETH smart contracts.
- Build, test and deploy contracts with Foundry.
- Run documented operational commands through the project CLI.
- Develop against a local fork containing mainnet DeFi contract state.
Requirements & limits
The repository is public and described as open source. Local setup requires Node.js 16 through 18, with Node.js 18 recommended, a valid MAINNET_PROVIDER_URL and a Web3 wallet such as MetaMask.
- The codebase is Solidity-focused and uses Foundry for builds, tests and deployments.
- The local environment relies on Anvil forked state rather than recreating mainnet integrations.
- The README names Uniswap, Curve and SushiSwap as third-party contract integrations.
- The repository provides a pnpm ops CLI for operational commands.
- Replacing the named DeFi venues requires modification; compatibility with a specific replacement is not demonstrated.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a pinned local Anvil fork
Prepare the repository for local development against a selected mainnet state.
Before you start
- Node.js 16 through 18; Node.js 18 is recommended.
- A valid MAINNET_PROVIDER_URL.
- The repository cloned locally.
- pnpm installed for the documented dependency commands.
Steps
Clone the origin-dollar repository and enter its directory.
Rename contracts/dev.env to .env and set MAINNET_PROVIDER_URL.
Set BLOCK_NUMBER if the fork should use a pinned mainnet block.
Enter contracts/, install dependencies with pnpm i, and run pnpm run node in a separate terminal.
Expected outcome
A local forked EVM node is started for development against the configured mainnet state.
Guide limitations
- The instructions document starting the local node, not successful execution of a particular contract interaction.
- The README warns not to run pnpm approve-builds.
- A valid provider endpoint is required.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- OriginProtocol/origin-dollar · Official homepage title · retained in its source language

