August 2026: more than thirty patent applications, Verus and the Confrmo platform
August 2026: I filed more than thirty UK patent applications, began building Verus private messaging and shipped escrow, attendance and ledger work on Confrmo.
August was the busiest month of the year. I filed more than thirty UK patent applications, built the first versions of Verus private messaging and calls. I also shipped a run of products on the Confrmo platform. It was also the month my products started working for each other.
More than thirty patent applications
Across August I filed more than thirty applications with the UK Intellectual Property Office. They cover identity checks and what a verified person is allowed to reveal, private messaging servers that can prove what they do not keep, verified email, attendance, a multi-party business platform and a mechanical door handle for safety in buildings. The full list, with plain-English descriptions, is on my patents page.
Confrmo: escrow, attendance, names and items
On the Confrmo platform I shipped four things people can use. Confrmo Escrow now tells every party as a deal moves from one stage to the next, because in anything involving money, silence makes people nervous. I'm Here, Confrmo's attendance service, refuses a clock-in outright when the location check fails, rather than flagging it for someone to review later. Confrmo Names gives people a personal web address. I made sure an address is never shown until it actually works. Every item registered on Confrmo now gets its own VCode straight away, so anyone can scan it to check its status.
Confrmo working for Veridium
The Confrmo Ledger certifies Veridium carbon credits. On 10 August I set up a Veridium node that Confrmo runs itself, so the Ledger confirms a credit has settled by checking the chain directly rather than relying on someone else's website. The node holds no keys, so it cannot move anybody's coins. The work on Confrmo made Veridium stronger.
Verus: private messaging and calls
On 18 August I started building Verus, a messenger that is private first: no phone number needed and a server designed to hold as little as possible. By the end of the month it had calls that ring on every platform, a Mac app signed for distribution, one identity across a phone and a computer, plus purchase codes that work in every app already in people's hands. Calls between iPhone and Android agree their audio at the start, so Apple devices keep their best quality while calls with Android simply work.
VCode, Couri and WhoozGot
I rebuilt the VCode decoder for the newest Android phones and made it a quarter of the size, then taught the scanner to prefer waiting over guessing, because for identity a wrong read is worse than no read. Couri gained sign-in with a verified Confrmo identity, so every sender behind an address is a real person. WhoozGot, a going-out guide, learned to read pub menus by their layout as well as their words.
Every choice from August 2026
-
Confrmo Escrow: everyone told at every step
Every party to a Confrmo Escrow deal is now told as the deal moves from one stage to the next.
-
I'm Here: clocking in only when you are really there
I'm Here, Confrmo's attendance service: a clock-in is refused unless the location check passes, with an optional live face check per workplace.
-
Confrmo checks carbon settlement against its own Veridium node
Confrmo now runs its own Veridium node, so the Confrmo Ledger confirms a carbon credit has settled by checking the chain itself.
-
Confrmo Names: an address is never shown before it works
A Confrmo Name now gets its security certificate when it is published. It is never advertised until it actually loads.
-
Couri: signing in with a verified identity
Couri now signs people in with Confrmo, so every sender behind an address is a verified person. The operator console uses the same sign-in.
-
Confrmo: every registered item gets its own VCode
When an item is registered on Confrmo it now gets its own VCode straight away, which anyone can scan to check the item's status.
-
Giving every essay its own identity on a custom WordPress route
Why each essay on this site carries its own canonical address and metadata, rather than inheriting the homepage's.
-
Screenshot protection designed around the owner
Verus keeps messages out of screenshots. Why I designed that protection to fall back to readable rather than hidden.
-
Health checks that prove the product works
Why a Couri deploy now proves the product can do its job before it is allowed to finish, not just that its services are running.
-
A Verus ringtone on every platform
Why Verus calls ring with their own sound on iPhone and the Mac. Why the ringer follows the call itself.
-
Choosing the moment to ask for notifications
Android asks people before an app may notify them. Why Verus waits until after registration to ask, rather than asking on first launch.
-
Shipping the Verus Mac app the way a stranger's Mac expects
Why the Verus Mac download is signed, notarised and stapled for distribution. Plus the certificate choice that gives it the longest life.
-
One person, one identity, on every device
How I brought Verus device linking to Android, so someone using a phone and a Mac stays one identity rather than two.
-
Setting the sitemap status where WordPress sets it
How I made the verusapp.co.uk sitemap answer correctly for search engines, by setting its status at the point WordPress does.
-
One door for gifts and purchases
How I made Verus purchase codes work in every app already in people's hands, without shipping an app update.
-
Scoping cross-site access for the Couri certified badge
Why the Couri badge is open to other websites while the rest of the API keeps strict browser security.
-
Keeping Confrmo sessions alive on Android
Why Confrmo on Android renews sessions with its own serialisation settings. The kotlinx.serialization behaviour that makes it matter.
-
Reading drinks menus as geometry, not text
Why WhoozGot reads each drinks menu by its layout as well as its words, keeping whichever reading suits that document best.
-
Keeping a headless browser healthy on a small server
How WhoozGot keeps its headless browser healthy on a small server. Why it records how every page was read.
-
Reading prices the way menus draw them
Some menus draw a single price as separate pieces of text. How WhoozGot reads them as one. Why every price is checked against its source.
-
Anonymous sending that survives a week away
Verus sends messages without the server knowing who sent them. Why the apps now look after their own anonymous credentials before they lapse.
-
Verifying a Confrmo Ledger record by dropping in its VCode
How I connected the VCode decoder to the Confrmo Ledger verify page, so a record can be checked by dropping in its image.
-
Rebuilding a decoder for 16 KB memory pages
Android 15 lays memory out in 16 KB pages. How I rebuilt the VCode decoder from source for it and made it a quarter of the size.
-
Reading VCodes anywhere in the frame
Why the VCode reader now searches the whole camera frame. What I made sure of before letting it look right up to the edges.
-
Why the VCode scanner would rather wait than guess
For identity, a wrong read is worse than no read. How I measured the scanner's false-read rate on a real phone and designed it to wait for certainty.
-
Benchmarking a rebuilt decoder honestly
I timed the rebuilt VCode decoder against the old one on the same phone. Same speed per frame; the gains were size, reach and compatibility.
-
Letting people choose when a photo holds several VCodes
Why the VCode web scanner lists every code in a photo and lets the person pick one, instead of acting on the first it finds.
-
Holding a sign-in request safely behind the face check
How Confrmo holds a Verify with Confrmo request from another app until the face check is passed.
-
Telling a chain's national menu from one pub's own
How WhoozGot recognises a chain's national menu page shared across branches and keeps it apart from each pub's own price list.
-
Letting two devices agree how a call should sound
Why Verus calls negotiate their audio at the start, so Apple devices keep their best quality and calls with Android still just work.
-
Keeping call audio in step between two threads
Why the Verus Android call engine guards its audio buffer. Plus the test I required to fail without the guard before accepting it.
-
Measuring what the microphone hears, not what the pipeline reports
Why Verus on the Mac takes a different audio path from the iPhone, found by measuring the sound itself rather than trusting the counters.