Orivions / Blog / Milestone payments and escrow

Milestone payments and escrow for Web3 service contracts: how to structure them

By Jakub Malarczyk, Founder, Orivions · October 18, 2026

Payment terms are where many Web3 engagements go wrong. Pay everything upfront and you carry all the risk; ask a provider to wait until the end and good teams will decline. Milestones split the risk fairly: the provider is paid as value is delivered, and you never have more money at stake than the next piece of work.

What makes a good milestone

• A concrete deliverable: a document, a deployed program, a working flow, a report. Not "two weeks of development".
• A written acceptance criterion: how you will check it, for example a program at a given devnet address passing listed tests.
• A review window: how many days you have to accept or raise issues, after which it is accepted by default.
• A share of the budget: proportional to the effort, so neither side is far ahead of the other at any point.

An example for a Solana dApp

A typical split for a project with a program, a frontend and an external audit:

• Milestone 1, specification (15%): written specification, account and instruction design, milestone plan. Accepted when you sign off the document.
• Milestone 2, core program (30%): program deployed to devnet, passing the listed tests including failure paths. Accepted after your review.
• Milestone 3, frontend and integrations (25%): all main user flows working on devnet against the deployed program.
• Milestone 4, audit fixes (15%): all audit findings resolved or explicitly accepted, confirmed in the fix review.
• Milestone 5, mainnet launch (15%): deployed from the audited commit with a verifiable build, authorities handed to your multisig, handover documentation delivered.

Deposits and escrow

A deposit for the first milestone, often 10 to 30 percent of it, is reasonable and protects the provider from clients who disappear. Beyond that, escrow can remove the need to trust either side: you deposit the milestone amount with a neutral party, or into a smart contract, and the funds are released when the milestone is accepted.

On-chain escrow works well for clearly defined milestones paid in stablecoins. It still needs an agreed process for disagreements: who decides, how quickly, and what evidence counts. An escrow without a dispute process only moves the argument.

When a milestone is disputed

• Go back to the criterion: most disputes are about vague acceptance criteria. Compare the deliverable with the written criterion, not with expectations.
• Separate defects from scope changes: bugs are fixed within the milestone; new requests are new scope with their own price.
• Use partial acceptance: accept and pay what works, and agree a short timeline for the rest.
• Escalate as agreed: to the escrow agent, an agreed reviewer such as the auditor, or mediation.

Clear milestones start with a clear brief; use our Solana project brief template. And before you pay anyone, run through the red flags when hiring Web3 providers.

← All posts