⚖️ Dispute Resolver
In some cases, disagreements arise between funders and recipients. A milestone is submitted, but the payout provider disagrees with the evidence. Rejections may repeat, and, even if it´s not desired, conflicts may begin to arise.
That’s why GrantFox works as a built-in Dispute Resolver - a neutral third-party mediator that steps in when engagements reach a critical point of disagreement.
🛑 When Does a Dispute Happen?
A dispute is triggered when the following occurs:
The Grantee submits milestone evidence.
The Payout Provider gives feedback for the submission because it didn´t meet the criteria.
The Grantee resubmits new versions.
The Payout Provider replies with additional feedback.
After multiple rounds of discussion, the two parties fail to reach an agreement.
The Payout Provider formally rejects the milestone.
Before a milestone is rejected, both parties are free to exchange as much feedback and discussion as needed - including multiple revisions, clarifications, and negotiation.
Once the milestone is officially rejected, it enters a dispute state, and GrantFox steps in as the Dispute Resolver to examine the case in detail.
🧠 What Is a Dispute Resolver?
A Dispute Resolver is an entity responsible for reviewing rejected milestones and deciding whether:
The Grantee has met the milestone requirements.
The Payout Provider’s rejections are valid.
A resolution (payment, revision, or cancellation) is fair and warranted.
In GrantFox, the platform itself (our core team) acts as the Dispute Resolver in these scenarios. Our role is to protect both parties, preserve fairness, and resolve issues transparently.
🧰 What Does GrantFox Do as Dispute Resolver?
Once a milestone enters a dispute:
We open a review window and notify both parties.
We request all context and communications, including off-platform clarifications if needed.
We evaluate the milestone description, submitted evidence, and funder comments.
We issue a binding resolution, which may include:
Requesting final revisions.
Approving the milestone and releasing funds to the grantee.
Cancelling the milestone and refunding the remaining balance to the payout provider.
Splitting the balance between the two parties, either equally or with different balances.
📌 The goal is not arbitration, but fast, neutral conflict resolution - in line with the original agreement.
💼 Example: Dispute in a $100 Bug Bounty
A developer submits a fix for a Stellar bug bounty. The fix does not meet the criteria by the funder for lack of test coverage. The dev adds tests and resubmits, but receives a rejection.
🔄 The milestone enters a dispute.
As GrantFox, we:
Review the bounty criteria.
Analyze the PR and tests.
Speak with the funder if needed.
Decide whether the submission meets the conditions.
If yes, funds are released. If not, a clear revision path is offered or the milestone is closed with refund.
🔒 Neutral, Transparent, and Case-by-Case
We never take sides by default.
We rely on milestone definitions and the evidence submitted.
Our decision process is documented and communicated.
🧩 Summary
Dispute Resolver is a role triggered when a milestone is rejected.
GrantFox acts as the default resolver, stepping in as a neutral party.
We review, decide, and help ensure fair outcomes for both funders and recipients.
Disputes are rare - but when they happen, they’re handled with care, clarity, and speed.
If a milestone gets stuck - we’re here to unblock it.
Last updated