Flowvest
Flowvest Litepaper
Lock funds once, release them over time, and let recipients claim transparently on-chain.
Instead of relying on reminders, trust, or manual transfers, Flowvest lets users lock funds into a vesting schedule and release them gradually over time. It is designed for practical payment agreements that need to be simple, transparent, and predictable.
What is Flowvest
Flowvest is a simple on-chain protocol for scheduled stablecoin payments.
Two primitives
Flowvest provides two primitives:
  • Vest: programmable transfer over time
  • Saving: programmable self-restriction over time
Saving (Self-Locked Vesting)
Saving is a simplified form of vesting where the sender and recipient are the same address.
It allows users to lock their own USDC and release it over time according to a predefined schedule, enforced entirely by smart contracts.
Unlike traditional savings accounts or custodial products, funds are:
  • Non-custodial
  • Fully on-chain
  • Immutable once created
This makes Saving a tool for self-discipline, not yield.
Key Characteristics
  • Self-directed — The creator and beneficiary are the same wallet.
  • Time-locked — Funds cannot be withdrawn before the release schedule.
  • No admin control — No entity (including Flowvest) can override or unlock funds.
  • Deterministic release — USDC becomes claimable strictly according to time.
Use Cases
  • Personal savings commitment
  • Preventing impulsive selling
  • Long-term capital allocation
  • Behavioral finance (forcing delayed gratification)
Design Philosophy
Saving is intentionally restrictive.
It removes optionality in order to create certainty: once locked, funds follow code — not emotion.
Why Flowvest
Many real-world payment arrangements are repetitive but informal.
Family support
Freelancer retainers
Milestone-based payouts
Personal financial agreements
These arrangements often depend on trust and manual execution. Flowvest replaces that with on-chain payment schedules.
How it works
1. Lock funds
The sender deposits USDC into a vest schedule.
2. Define the schedule
The sender sets: period amount, duration, and recipient.
3. Release over time
Funds unlock by period according to the schedule.
4. Claim anytime
The recipient claims released funds when available.
Core principles
Funds are locked upfront
Release follows fixed intervals
All vest data is on-chain
No hidden custody
No off-chain enforcement needed
The goal is not to create a complex financial system. The goal is to make recurring payments programmable and transparent.
Fee Model
V1.1
Flowvest V1.1 currently operates without protocol fees.
The protocol is designed to remain simple, transparent, and predictable during its initial phase.
As Flowvest evolves, a fee model is planned to support long-term sustainability, including:
  • Indexer infrastructure
  • Explorer services
  • Automation (keepers)
  • Protocol maintenance
V2 — Planned Fee Model
The initial fee model for Flowvest V2 is proposed as follows:
Create Vest
0.5% of principal
Recipient Change
First change free, then 2 USDC
Claim / Release
Free
Terminate
Free
Time Model

Flowvest uses fixed-duration periods from the vest's start timestamp, not calendar months or local month boundaries.

In V1.1 you choose a plan at creation; each vest keeps one fixed period length for its whole life. Examples: a Monthly plan uses 30 days per period (2,592,000 seconds) with 3 releases; a Biweekly plan uses 14 days per period (1,209,600 seconds) with 6 releases.

Unlocked amounts become claimable at period boundaries—the end of each interval—counted forward from start time, in discrete steps rather than a smooth stream.

That yields predictable, fully verifiable on-chain behavior, independent of month length, leap years, or timezone differences.

Security and transparency
All logic is executed by smart contracts, without trusting third parties. All vest schedules are visible on-chain. Users can verify vest parameters, claim history, termination history, and recipient changes. Flowvest Explorer provides a simple interface for viewing these records.
Access Control

The core logic of the protocol cannot be altered.

Multi-signature can only adjust risk parameters (such as TVL caps and ranges), it cannot access user funds or modify existing vests.

As the protocol matures, control permissions may be gradually reduced or completely removed.

Use cases
Family support payments
Freelancer agreements
Long-term service arrangements
Personal financial commitments
Over time, it may also support DAO compensation, grant distribution, team vesting, and subscription-style payment flows.
Current status
V1.1
Network · Base
Token · USDC
Version · V1
Closing
Flowvest is designed to be simple, understandable, and on-chain. Not a bank. Not a payroll platform. Just a minimal protocol for scheduled stablecoin payments.
Ready to explore?
Open the app to create or claim vests, or view public vest history on the explorer.