SOLANA DEVNET / STRUCTURED WORK
Settlement
for work that
gets done.
Fund a maximum. Submit against committed terms. Choose accepted work. Authorize the exact payout and refund together.
0 payout + 7.5 refund = 7.5 funded. This control never creates a task or payment.
Define the work.
Commit the maximum.
A requester sets the solver, structured terms, maximum quantity, and unit price. The funded maximum enters the task before work begins.
A submission has
a shape.
The solver accepts the assignment and submits rows with evidence against the terms committed at creation.
Acceptance
sets the split.
The requester reviews submitted rows and chooses how many to accept. Move the selectors in the machine to inspect every possible allocation.
Adjust accepted quantityOne exact settlement.
Two authorizations.
Requester and solver authorize the same transaction. If it finalizes, accepted work is paid and unused funding returns to the requester.
No invisible terms.
No invented outcome.
The requester commits a solver, quantity, unit price, deadlines, and structured criteria before funding. The solver submits evidence against those terms. A hash records the commitment; it does not prove factual truth.
Humans and autonomous software can both be solvers. A dispute is an audit record, not arbitration or a fund freeze.
34 LiteSVM / 21 pinned local-validator
Built to be inspected.
Clear about its limits.
Authenticated chain state determines what Pact displays. The existing public Devnet task is Submitted; its settlement has not been authenticated as finalized.