How a deal works
Redeal is a neutral referee for splitting things. The whole system is one promise kept by mathematics: nobody can see your input before everyone's is locked in, and nobody can change the outcome after, including us.
Four steps
-
COMMIT
Everyone seals their input
Each party sends a hash of their input: the input and a random salt, run through SHA-256. A hash is a one-way fingerprint, so the server stores fingerprints, not values. Nobody can see anyone's numbers, and no one can wait to see others before deciding their own.
-
REVEAL
Everyone opens at once
Once every commitment is in, each party sends their actual input and salt. The server checks them against the stored hashes. A mismatched input is rejected, so what was sealed is what gets used. Changing your answer after seeing the field is impossible; the hash pins you to your first answer.
-
COMPUTE
A published algorithm runs
The engine executes the chosen algorithm exactly as its public spec describes: integer arithmetic only, no floating point, no external data, no randomness we control. The same inputs always produce the same output, so anyone can re-run it and check.
-
CERTIFY
Everyone gets the same receipt
Each party receives an identical certificate: the algorithm, the result, the timing, a fingerprint of the inputs, and our signature. The certificate is also appended to a public transparency log. Any party, or any skeptic, can verify it without asking us.
Two freelancers, one invoice
Ada and Ben delivered a £1,000 job together and need to split the fee. Ada creates a deal on Redeal; Ben joins through his private link.
| Moment | What happens |
|---|---|
| commit | Ada seals "my work was worth 620 of the 1000". Ben seals "my work was worth 450". The server stores sha256:8d14… and sha256:22b0…. Nothing else. |
| reveal | Both inputs open and match their hashes. Ada cannot now shade her number toward Ben's; the hash won't allow it. |
| compute | split.v1 (adjusted winner) runs on (620, 450). It assigns each party the share of work they valued and settles the difference in cash: Ada £612.50 · Ben £387.50. |
| certify | Both receive certificate c_9f2c41aa…. It shows the split, the algorithm, and the proof. It does not show 620 or 450. |
If Ben had gone silent, the deal would have been voided and a non-participation certificate would name his commitment hash. Silence has a receipt too.
Every deal, one of these paths
We attest agreement, not truth
A Redeal certificate says: these parties sealed these inputs, this published algorithm ran, this result came out. It does not say the inputs were honest, and it cannot make anyone pay. If the numbers going in are disputed, that dispute belongs to the parties, not to us.
Enforcement is a different layer: escrow, contracts, reputation systems. We slot underneath them as the part everyone can check.
Skeptical? Why you don't have to trust us ↗