How the record works
The front page makes the claim. This page is the machinery: what a finished job writes, what a public ledger actually is, how a stranger checks your record without asking us — and exactly what our keys can and cannot do.
01 — The write
What a finished job writes
A job here ends with a sign-off: the person who posted the work confirms it is done and rates it. That sign-off writes one line — the work's name, the hours, the date, the rating. You do not type the line and neither do we. It comes from what happened on the job, countersigned by the person who paid for it.
The work gets its real name. Mowing lawns is recorded as Lawn and Grounds Maintenance, which is what it is. Never inflated into something you did not do.
The line lands on your record inside the app first. Publishing the record beyond the app is a separate step, and it is your choice — nothing is published until you say so. When you do, your record is written out to a public ledger as an entry in your name, and from that moment, reading it no longer requires us.
02 — The ledger
What a public ledger is, concretely
A ledger is a numbered list of entries. Every entry carries the exact time it was written, and the list only grows — new entries are added, old ones stay. The ledger we write to is called Hedera. It is operated by a council of independent companies, not by us. We could not rewrite its history if we wanted to, because we do not run it.
Your published record is one entry in that list: a collection number, an entry number, a timestamp — and the address of the record document itself, which is stored on a public file network called IPFS. The document is what a checker actually reads. Reading any of this is free and needs no account, anywhere.
On the public copy: your name, your trade and skills, your tier, the counts — finished jobs and volunteer hours — and the record card.
Never on it: your email — the entry carries only a one-way scramble of it that cannot be turned back into an address — your phone, your home address, your precise location, payout details, messages. The full accounting is on the privacy page.
One beta fact, before you rely on any of this. While OMM is in beta, entries are written to the ledger's test network: same machinery, same public reads, but the test network can be reset with notice, and a reset clears its history. The move to the main network — where entries stay for good — is already built. This page changes the day it ships.
03 — The check
How someone checks it
You send one link
Your record card in the app prints the collection number, your entry number, and the link that carries both. Text it, mail it, put it on a business card.
They open it in any browser
The link lands on a public viewer of the ledger called HashScan. No account, nothing to install, no permission from us.
They read the entry
The date it was first written. The account that holds it. Every update since, each with its own timestamp. And the address of the record document — open that, and the record itself loads: name, trade, tier, the counts, the card.
Notice whose name is missing
Nothing on that screen is served by OMM. The viewer, the ledger and the file network answer on their own. If our website went down tomorrow, the link would still answer.
The shape of the link
hashscan.io/token/collection#/entry#
04 — Our keys
What our keys can do, and what they cannot
OMM holds two keys on this record system. One issues new entries. One updates what an existing entry carries. We say this plainly because the update key is not a loophole — it is how your record grows: after a finished job, your entry is re-pointed to a fresh document with the new line on it, and that re-pointing is itself a public, timestamped event in the entry's history.
Here is what the keys cannot do: work quietly. Every use of either key becomes part of the entry's public history, written there by the ledger's operators, not by us. We can add to the trail. We cannot erase it, and we cannot touch a record without the touch showing.
An earlier draft of these pages said nobody could delete a record, us included. We checked that claim against the keys we actually hold, and it was not true — so it is gone. The true statement is narrower and worth more: nothing about your record can be changed quietly, by us or by anyone. Do not take our word for it. The check is the history on the entry, and anyone can read it.
05 — The tier
The pay tier is a count, not a judgement
Your tier is decided by one comparison: the number of jobs you have finished, against a printed threshold. Cross the threshold and the tier is yours. The whole schedule:
What does not move it: money — there is no purchase path in the code, we looked. Seniority — days on the app count for nothing. Anyone's opinion — no review board sits between you and the threshold. And the count that promotes you is the same finished-jobs count printed on your record, so the arithmetic can be re-run by anyone you hand the link to.
Ranges are what jobs post at, not a promise of earnings.
06 — Volunteer badges
Volunteer hours, on the same record
Volunteer lines sit beside paid lines — an hour is an hour whether or not money changed hands. Volunteer hours also earn badges, on a schedule as fixed as the pay tiers:
No badge can be bought. The hours are the whole test.
07 — The 25 percent
The 25 percent, and what it is not
Finished work also writes time tokens onto the record. The per-hour figure scales with the job's tier:
Unpaid work earns the premium. Community service and token-only jobs write 25 percent more tokens per hour than the same hour paid. A 4-hour food-bank shift at entry rates writes 5 tokens; the same 4 hours paid write 4. That is deliberate. Everywhere else, unpaid hours vanish. Here they are counted at a premium.
Time tokens are not cash yet. There is no way to turn tokens into money today; that part is still being built. So "25 percent more" means more on the record — not more in your pocket. When cash-out ships, this page will say so.
Everything above was checked against the running system before it was written. Where something is not live yet, this page says so instead of rounding it up.
Back to the front page