tenby10Verified proof of work

Sample. This is a demo of what a client sees. Real links show a freelancer's own verified hours.

Invoice INV-2026-07-04

12h 30m of verified active time

Worked by Alex Rivera · Jul 1–4, 2026

Verified

Every interval below was signed on the freelancer’s machine at the time and hash-chained to the one before it. These hours cannot have been changed since.

Active time
12h 30m
Days worked
4
Active intervals
75 / 81
Avg. focus
80%

75 of 81 logged 10-minute intervals cleared the focus bar and count as active time. Lower-focus time is shown in the log below but isn’t counted.

What was worked on

Jul 1

Built the core ingestion endpoints and refactored the ledger validation logic.

Jul 2

Wrote unit tests for the signature verification and reviewed two pull requests.

Jul 3

Traced a rounding bug in the invoice totals and fixed the day-boundary handling.

Corrected after it was first written

Written by AI on Alex's own machine, from their active time, using this exact prompt:Summarize the developer's work from window titles into concise, professional notes. Do not infer beyond the evidence.

Verified activity log

Jun 29Jul 5
4 days worked
12h 30m
Active this week

All dates and times are shown in UTC — the time zone these hours were worked in. Green and amber intervals cleared the focus bar and count as active time; red is time that was logged but not counted.

How each hour was scored

The exact rules that decided what counts as productive. They're locked into every signed hour, so they can't be changed after the fact.

Counted as productive
VSCode, Terminal, GitHub, Figma
Counted as meetings
Zoom, Google Meet, Slack Huddle
Counted as distracting
youtube.com, twitter.com, reddit.com
Fake-activity detection
On
The prompt that scored each interval
Classify each minute of window titles as productive, meeting, distracting or idle. Judge only what the titles show.
Technical verification

The cryptographic fingerprints behind this page. Every hour is signed and hash-chained; editing any entry breaks the chain and this page would show as failed. The client that produced this is source-available and independently auditable.

Ledger record head
0x3f8a21e9
Prompt fingerprint
0x8f4c2
Rules fingerprint
0x8f4c2a1b
Signatures
All valid

Per-interval ledger hashes

2026-07-01
9:00 AM0x840a17
9:10 AM0x857ce9
9:20 AM0x86efbb
9:30 AM0x88628d
9:40 AM0x89d55f
9:50 AM0x8b4831
10:00 AM0x8cbb03
10:10 AM0x8e2dd5
10:20 AM0x8fa0a7
10:30 AM0x911379
10:40 AM0x92864b
10:50 AM0x93f91d
11:00 AM0x956bef
11:10 AM0x96dec1
11:20 AM0x985193
11:30 AM0x99c465
11:40 AM0x9b3738
11:50 AM0x9caa0a
12:00 PM0x9e1cdc
12:10 PM0x9f8fae
12:20 PM0xa10280
2026-07-02
9:20 AM0x5785de
9:30 AM0x58f8b0
9:40 AM0x5a6b82
9:50 AM0x5bde54
10:00 AM0x5d5126
10:10 AM0x5ec3f8
10:20 AM0x6036ca
10:30 AM0x61a99c
10:40 AM0x631c6e
10:50 AM0x648f40
11:00 AM0x660212
11:10 AM0x6774e4
1:00 PM0x7763eb
1:10 PM0x78d6bd
1:20 PM0x7a498f
2:00 PM0x8014d7
2:10 PM0x8187a9
2:20 PM0x82fa7b
2:30 PM0x846d4d
2:40 PM0x85e01f
2:50 PM0x8752f1
2026-07-03
8:40 AM0x2250b9
8:50 AM0x23c38b
9:00 AM0x25365d
9:10 AM0x26a92f
9:20 AM0x281c01
9:30 AM0x298ed3
9:40 AM0x2b01a5
9:50 AM0x2c7477
10:00 AM0x2de749
10:10 AM0x2f5a1b
10:20 AM0x30cced
11:30 AM0x3af0ab
11:40 AM0x3c637d
11:50 AM0x3dd64f
12:00 PM0x3f4921
12:10 PM0x40bbf3
12:20 PM0x422ec5
1:30 PM0x4c5284
1:40 PM0x4dc556
1:50 PM0x4f3828
2:00 PM0x50aafa
2:10 PM0x521dcc
2:20 PM0x53909e
2026-07-04
10:00 AM0xfe7d6c
10:10 AM0xfff03e
10:20 AM0x016310
10:30 AM0x02d5e2
10:40 AM0x0448b4
10:50 AM0x05bb86
11:00 AM0x072e58
11:10 AM0x08a12a
11:20 AM0x0a13fc
11:30 AM0x0b86ce
11:40 AM0x0cf9a0
11:50 AM0x0e6c72
12:00 PM0x0fdf44
12:10 PM0x115216
12:20 PM0x12c4e8
12:30 PM0x1437ba

How do I know this is real?

It can’t be edited
Every hour is cryptographically signed and chained. Changing a single entry after the fact breaks the chain, and this page would show as invalid.
No screens are shared
Unlike surveillance trackers, tenby10 never includes screenshots or typed content in what you receive. What the agent sees stays on the worker’s machine, under their control. You get proof of the hours without seeing anyone’s private screen.
Anyone can check it
The software that produced this is source-available and independently auditable. Read the audit.
Who runs this page
tenby10 (PivotalPoint OÜ) hosts this page as a neutral verification service, not Alex and not their client. The hours and scoring rules arrive cryptographically signed from Alex's own machine.
Link status
This is a sample link. Real links are shared by a freelancer and stay live until they revoke them, with no expiry.
Your privacy as a viewer
No account needed to view this page. We use only anonymous, consent-gated analytics, so decline the cookie banner and nothing is set. Alex can see that this link was opened and when, the same as any shared document, but not who opened it, where from, or anything else about you. No cookie, no IP address, and no record of you is kept. Privacy Policy.
What “verified” does and doesn't claim
It attests that these records were signed at the time on the freelancer's enrolled device and have not been altered since: proof of the hours and the rules, not proof that a specific person did the work. It replaces forgeable screenshots and timesheets, not your judgment. More on what a link proves.
Get verified hours from your contractors →

Want proof like this from your own contractors? No account needed to view this page.