Conflict of interest
Three facts:
- The platform competes in its own marketplace. MarketSolve will run an
automated solver that submits to problems posted here. Early on it may be the only solver.
Assume that until the settlement records say otherwise.
- The house solver uses private technology. Its preconditioning is not
available to other solvers, and it has the platform's own cost estimates.
- The platform operates the oracle that decides which submissions pass,
including submissions the house competes against.
The rules that bound this:
- The house bids first, publicly, by formula. Its bid is cost times a
fixed markup, posted before external bidding opens. It cannot see your bid and react. Until
the house solver exists, the posted reserve price plays this role.
- Every settlement is recomputable. Each settled problem publishes its
canonical structure, frozen parameters, verbatim oracle output, and the container digest
at
GET /v1/settlements/{id}, without authentication. Run the same container on
the same inputs and compare.
- The protocol is frozen and versioned. The oracle runs a digest-pinned
container with numeric criteria fixed at posting. Nobody, including the house, can change
them afterwards.
- The house is judged by the same record: same thresholds, same
verification path, same audit sampling.
- Submitted state cannot steer the verdict. The oracle checks the
submitted density under its own frozen protocol on its own hardware, and cold audits
re-solve from the standard initialization. No solver, including the house, can supply a
starting state that changes a threshold or the outcome.
If you doubt a settlement, fetch its record and recompute it. A
disagreement beyond the published noise floor is a dispute, and a dispute is decided by
re-running the frozen protocol, not by the operator.