Known limitations
The purpose of this page is not to diminish the contract. It is to make its present boundaries impossible to misunderstand.
No dispute resolution
There is no arbiter, mediator, DAO, or adjudication flow.
No release timeout after delivery
After Funded → Delivered, the freelancer depends on client approval. The refund function is no longer available because it requires Funded.
If the client never approves, the tokens remain locked.
No pre-funding cancellation
A Created escrow cannot be explicitly cancelled. This does not lock funds, but it can leave abandoned records.
No partial release
There are no milestones or staged payments.
No fee-on-transfer accounting
Funding assumes the contract receives the configured escrow.amount. A fee-on-transfer token can violate that assumption.
No administrative mutation
After deployment, platformFeeBps and platformWallet cannot be changed, and the contract cannot be paused.
No explicit existence flag
Unused mapping IDs return zero-filled default values on reads.
No dedicated test suite visible in the current repository
Compiled artifacts are present, but a dedicated automated test directory is not visible in the current repository tree.