Software work intake.
Files stay in this browser until you choose to upload them through a private form. Delivery checks read the public Arbitrum One record.
01 / Define the work
What should the files do?
The checker verifies properties of files. It cannot run tests, builds, or the worker’s code. Describe the file properties that would make the result acceptable.
First orders are prepaid by invoice in CAD or USD, and no wallet is needed. Use this page only if you have asked in writing to settle in USDC on chain.
Approve an exact compiled job
The operator’s check summary is written by the operator. It is not derived or certified by this page. Review it and the compiled job, then approve its exact fingerprint through the private approval form.
02 / Prepare the delivery
Make the work ready to check.
Keep the full package.
Save the exact submission receipt.
This preview is not the pre-check. The operator runs the agreed check, returns feedback tied to your submission receipt, and freezes the passing submission before activation.
Keep a full local copy before activation. Upload work only through the private worker form. The buyer receives it after completion. Work can go unpaid if the buyer cancels before activation; after activation, missing the deadline loses the full 10 USDC bond. The pilot terms describe Northset’s backstop for a timeout caused by its prover. A new upload does not replace a frozen submission without operator confirmation.
03 / Match the record
Check the files you received.
Your approved job.
Your transaction. The delivered files.
Preview pasted result values
Pasted values have no authenticated record. This preview can never produce a verified delivery.
The precise claim for an accepted result
Task-authorized deterministic evaluation succeeded. The committed change set was applied to the task-authorized canonical base tree, and every task-authorized integer-only WebAssembly verification module returned zero under SOFTWARE_WORK_WASM_V1. The result is bound to this task’s activation tuple. It does not prove remote repository origin, conventional operating-system command execution, natural-language requirement satisfaction, or when the work was created.