Milestone escrow

Every payment
has a clear next step.

Agree on the work first. In the planned flow, a smart contract holds the project funds and releases each milestone after approval.

Not live: No contract has been deployed, audited or connected to this site. Do not send funds.

Hands typing on a keyboard at a shared desk
CONTRACT ESCROWIn designFunds stay on-chain after launch
The proposed flow

Know where the money is
before work begins.

  1. 01

    Agree on scope

    Client and freelancer set deliverables, review windows, payment asset and a release amount for each milestone.

    Before funding
  2. 02

    Fund contract escrow

    The client approves the transaction in their wallet. Funds move to the contract on the selected EVM network, not into ValeDeFi's custody.

    Wallet approval
  3. 03

    Submit and review

    The freelancer delivers the agreed milestone. The client approves it or opens a dispute under the contract's published rules.

    Milestone by milestone
  4. 04

    Release or resolve

    An approval releases that milestone. A dispute would follow the timelocked, arbitrator-voted process after its contracts are independently reviewed.

    On-chain outcome
For your first on-chain project

Crypto terms,
in plain language.

A wallet is an app that lets you approve blockchain actions. A stablecoin is a token designed to track a currency such as the US dollar. A transaction needs your approval, and once confirmed it may not be reversible.

What happens if a milestone is not approved?

The planned contract will define a review window and a dispute path. Until those rules are published and audited, the site must not accept funds or promise an outcome.

Can ValeDeFi reverse a payment?

No. The design goal is non-custodial settlement; ValeDeFi would not hold funds off-chain or unilaterally reverse a confirmed transaction.

Transaction state examplesUI preview
○
Waiting for wallet approvalShown before a future on-chain transaction
Idle
◌
Transaction pendingShow the network confirmation state
Pending
!
Transaction failedExplain the error and let the user retry
Failed

These are interface states, not live wallet transactions.

Before launch

Security is a sequence,
not a badge.

These are next steps for a safe launch plan, not completed integrations.

01 / Contracts

Build and test

Define release, refund, cancellation and timelocked dispute rules. Add reentrancy protection, pause controls and restricted roles.

02 / Testnet

Exercise every path

Deploy to a selected EVM L2 testnet, verify wallet prompts, and index events for milestones, approvals, refunds and failures.

03 / Independent review

Audit before mainnet

Complete external security review and remediate findings before any production funding is enabled.

04 / Operations

Plan the wider launch

Evaluate KYC options, fiat on/off-ramps, arbitration staking and $VALE governance after legal, security and user research.

Audit readiness note: a test suite and contract source do not exist in this static site yet. Production readiness requires reviewed contract code, tested upgrade and pause procedures, and a completed independent audit.