Prepare Escrow documents
Terms, work evidence and dispute evidence each contain a public URI and a nonzero SHA-256 digest. Agree on the exact file before committing it. The contract stores the reference; it does not download, decrypt or judge the document.
1. Choose the bytes and their location
Publish the agreed file at a URI the other parties can read, or use a small embedded document supported by the editor. The viewer does not upload a file for you. Escrow limits the complete URI to 512 UTF-8 bytes, including an embedded document's encoding; larger content needs an external location.
For sensitive material, encrypt first and hash the exact published encrypted bytes. Arrange decryption-key delivery separately. Do not put secrets in URLs or agreement fields: the contract reference is public.
2. Calculate or enter SHA-256
| Method | What it establishes |
|---|---|
| Enter a digest | Paste 0x plus 64 hexadecimal characters from your own exact-byte calculation. The form does not retrieve anything. |
| Calculate from file | Hashes the selected local file without uploading it. This does not check the URI. |
| Calculate from URL | Explicitly downloads and hashes the response. HTTP(S) requires browser access; IPFS uses the selected gateway. Download scope applies to the original remote URI. |
| Calculate from embedded document | Decodes the supplied data URI and hashes its bytes locally, without a network request. |
The field does not fetch while you type. Calculation is bounded to 8 MiB and 15 seconds. Remote requests need browser CORS access, send no credentials or referrer, and reject redirects. For IPFS, select an admitted gateway first. A failed remote read does not silently switch methods.
For an external calculation on Linux:
sha256sum "terms.txt"Paste 0x followed by the hash, not the filename. Hash the file's bytes, not its URI text. Changing whitespace, encoding or JSON formatting changes the commitment. A larger document can use a separately calculated digest even though the browser calculator will not read it.
3. Review the URI and digest together
A successful calculation replaces the digest. Failure or cancellation preserves it. Changing the URI also preserves the digest but clears its earlier source association and invalidates pending work. Check both values before preparing the transaction; an old hash beside a new URI is not a verified pair.
Calculation produces a new digest. It does not compare downloaded bytes with an existing expected commitment. To verify stored evidence, retrieve the intended bytes independently, hash them and compare with the digest recorded on the contract. A URL calculation describes today's response, not a promise that a mutable URL will keep serving it.
The contract checks a nonempty URI within its byte limit and a nonzero digest, not document truth or availability. The parties remain responsible for retaining and checking the agreed content. Return to create and fund, submit work or open a dispute.
Source: calculation transports and limits, field controls, and contract document validation.