tenby10Verified proof of work

Sample. This is a demo of what your client opens: one person’s verified hours.

Start a pilot →

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 Alex’s machine at the time and hash-chained to the one before it. tenby10 checked every signature again when this page opened, so these hours cannot have been changed since.

Active time
12h 30m
Days worked
4
Active intervals
75 / 81

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 29 – Jul 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, and tenby10 checked each one as it arrived and refused any that did not verify. Every signature is checked again each time this page opens. The client that produced this is source-available and independently auditable.

Ledger record head
0x1c9cea0f
Prompt fingerprint
0xffac6eb1
Rules fingerprint
0x160e8937
Signatures
All valid, re-checked now

Per-interval ledger hashes

2026-07-01
9:00 AM0xe2c8d4
9:10 AM0xa5c841
9:20 AM0x754da6
9:30 AM0x3c8501
9:40 AM0x018ee7
9:50 AM0xfc6fcf
10:00 AM0x79c87c
10:10 AM0x8d41ff
10:20 AM0x70d613
10:30 AM0xed9095
10:40 AM0xc437a0
10:50 AM0x653d5f
11:00 AM0x29bf4f
11:10 AM0xca5f19
11:20 AM0x456f4e
11:30 AM0x341377
11:40 AM0xf2b13b
11:50 AM0xd6f0f6
12:00 PM0x19c306
12:10 PM0xaa3082
12:20 PM0x056945
2026-07-02
9:20 AM0xf39f72
9:30 AM0x3229fe
9:40 AM0x38d409
9:50 AM0xafe3cb
10:00 AM0xb7984b
10:10 AM0xdc12ac
10:20 AM0x9efbd1
10:30 AM0x08e659
10:40 AM0x07f791
10:50 AM0xe298f9
11:00 AM0x041d34
11:10 AM0x3b9e0c
1:00 PM0x370390
1:10 PM0x507ebc
1:20 PM0x0456d5
2:00 PM0xf6e7e0
2:10 PM0x25fcc2
2:20 PM0xad02bd
2:30 PM0x50483b
2:40 PM0xc27ed5
2:50 PM0x6e4fc3
2026-07-03
8:40 AM0x780340
8:50 AM0x826a48
9:00 AM0x33daab
9:10 AM0x787f8d
9:20 AM0x5f777e
9:30 AM0x25eb7d
9:40 AM0xb9f081
9:50 AM0x8f9403
10:00 AM0xdc3d37
10:10 AM0x0378e8
10:20 AM0x3a020b
11:30 AM0x50bb2a
11:40 AM0x273d8e
11:50 AM0x555ae1
12:00 PM0x898382
12:10 PM0x343f7f
12:20 PM0x288faf
1:30 PM0x45afef
1:40 PM0x18d98c
1:50 PM0xb8145d
2:00 PM0xd4685f
2:10 PM0x796579
2:20 PM0x7ef0ff
2026-07-04
10:00 AM0xdeb8bd
10:10 AM0x02a9c0
10:20 AM0x4e3ef4
10:30 AM0x32fc66
10:40 AM0x750eb7
10:50 AM0x56180c
11:00 AM0x550497
11:10 AM0x4d4f4b
11:20 AM0x9f7a2e
11:30 AM0xff6f09
11:40 AM0x3bc8b3
11:50 AM0x89b41b
12:00 PM0x0b6ee1
12:10 PM0xd3d8a4
12:20 PM0x314002
12:30 PM0x1c9cea

How do I know this is real?

It can’t be edited
Every hour is cryptographically signed and chained on the machine that recorded it. tenby10 checks each hour as it arrives and refuses any changed copy of an hour it already holds. It checks every signature again each time this page opens, so a changed record would show here as failed.
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 the person whose hours they are, 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 Alex'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.

This is a demo of what a client opens. Run it with your team, free for the first teams, or read how checking one works if you are the one paying.