Dashboard
On this page

Disputes

When to open a dispute on a contract milestone, what each side adds, and how a DevNet moderator decides where the held money goes.

Opening a dispute

Either side can open a dispute on a milestone that's funded or delivered: use Open a dispute on the milestone. Pick what the problem is:

  • The work wasn’t delivered
  • The work isn’t what was agreed
  • The other side stopped answering
  • The work is done but payment is being withheld
  • Something else

Explain what happened and add links as evidence: the delivery, chat screenshots, a video. The other side is notified and can add their side, with their own links, once.

While the dispute is open the money is frozen: nothing is released or refunded automatically. Whoever opened it can withdraw it; the milestone then goes back to where it was and its clock starts again.

How a moderator decides

A DevNet moderator reads both sides, the contract's scope and terms, the timeline and the payments, then decides:

  • Release: the developer is paid, minus the fee.
  • Refund: the client gets all of it back.
  • Split: part to the developer (the fee comes out of that part) and the rest back to the client.

The decision comes with a note that both sides see on the contract. It settles where the held money goes; it isn't a legal ruling, and DevNet isn't a court or a law firm.

Avoiding disputes

  • Write a clear scope and terms: what counts as done, deadlines, file formats, who owns the work.
  • Use smaller milestones. Less is at stake in each one.
  • Keep talking on DevNet. Messages and the timeline are what a moderator can see.
  • Never pay or get paid outside the contract. DevNet can only help with money it holds.

Still stuck? Ask in the support channel on the DevNet Discord, or see how support works on your plan.