What I built and why I built it that way.
Month by month since February 2026, across every product I am building. Each entry sets out what I tried first, what I chose instead and where the work helped another product. It explains how, in plain English. It does not publish code.
- February 2026
February was the month Veridium Carbon went live. It is a blockchain built for one job: carrying certified carbon credits so they can be bought, settled and checked without paper trails, manual processing or the same credit being counted twice.
Read February 2026 in full-
Veridium Carbon goes live on rules I designed
The Veridium Carbon blockchain went live on the issuance rules I designed, with every new block signed by the network before it is accepted.
- March 2026
March was about openness. A ledger that asks people to trust it with real value should let them read the rules for themselves, so on 3 March the Veridium Carbon code went into a public repository.
Read March 2026 in full-
Veridium Carbon: the code published in the open
The Veridium Carbon blockchain code went up in a public repository, so anyone can inspect the rules the carbon ledger runs on.
- May 2026
May was a founding month. On 7 May I incorporated Confrmo Ltd, the company behind the identity platform that most of my later work runs on. In the same weeks I started building two of its core products.
Read May 2026 in full-
Couri: the platform foundations
The foundations of Couri, verified email: the core services, the database and the build that everything since runs on.
-
Confrmo: a live person, bound to the account
The Confrmo app now checks that a real, live person is in front of the camera and ties their face to the signed-in account.
- June 2026
June was about making Confrmo safe to use in ordinary life, where phones get shared, borrowed and handed round.
Read June 2026 in full-
Confrmo: each person's data kept apart
The Confrmo app moved to confrmo.com. Each person's profile and photo are now kept strictly apart, with everything cleared on sign-out.
- July 2026
July was the month Confrmo reached the public. On 21 July the Confrmo app went live on the App Store, so anyone with an iPhone can now prove who they are with it.
Read July 2026 in full- August 2026
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.
Read August 2026 in full-
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.
- September 2026
September was the month the work reached people's phones. Confrmo and Verus both arrived on Google Play, I filed more than twenty more patent applications and I turned a shelf of retired radio hotspots into part of a live network.
Read September 2026 in full-
Forward secrecy from the very first message
Why Verus keeps a steady supply of single-use keys, so every new conversation starts with forward secrecy however many people you meet.
-
A fail-closed trust list for passport readers
Why Confrmo only accepts passport evidence from reader software it has been told to trust. How the iPhone reader joined Android's.
-
One certificate that renews for every Confrmo address
How I set up the server so the shared certificate behind every Confrmo personal address can always renew.
-
A Verus call that reaches a sleeping phone
How Verus rings a locked, dozing Android phone without keeping the app running all the time. Tested in real conditions.
-
Pairing a new device without losing a single chat
Linking a device used to start it empty. I made Verus pairing carry chats, contacts and groups across, sealed inside the pairing itself.
-
Verus Relay boxes that talk to each other by radio
I brought up the LoRa radio inside two Verus Relay boxes. Each now announces its name over the air every minute, with no internet in the path.
-
Verus Relay boxes that set themselves up wherever they are plugged in
More Verus Relay boxes, built from spare hardware, that configure themselves and tell the network where they are, ready to hand out.
- October 2026
-
A white paper for turning idle hardware into Verus Relays
I wrote and published the Verus Relay white paper: which boxes can run a relay, how to convert one, the full specification and measured results.
-
Verus for Android: one call, whichever phone is at the other end
A new Android release of Verus in which calls between Android and iPhone carry sound both ways, end cleanly for both people and can be rated afterwards.
-
One source of truth for the Verus Relay map
The public Verus Relay map and the operator console now draw from the same live data and update themselves as relays come and go.
-
A setup guide for people hosting a Verus Relay
A public page that takes somebody from an unopened Verus Relay box to a working relay in six steps, with no settings and no passwords.
-
Verus shows what it carries, live, without showing who
The verusapp.co.uk homepage now shows a live running total of message deliveries to devices, updating as it happens, using totals only.
-
A Trust Centre on every site, generated from the policies themselves
Every company website in the group now has a Trust Centre showing its security policy set and an honest certification status, built from the same documents the policies live in.
-
The policy pack, released under an NDA signed online
A buyer can now ask for the full security policy pack from any group website, sign a mutual NDA online and receive the pack once the request has been checked.
-
Analytics that waits to be asked
Group websites now load analytics only after a visitor accepts, with declining as easy as accepting and a way to change the choice on every page.
-
News sections on three sites, opening with Web Summit
confrmo.com, verusapp.co.uk and louisjamesdavis.com each gained a news section, with Web Summit Lisbon as the first announcement.
-
Every patent number links to its official record
Every pending application on louisjamesdavis.com and verusapp.co.uk now links to its public record on the UK IPO register, including the newest Verus filing.
Institutional, investment and partnership enquiries.
Four kinds of enquiry reach Louis-James Davis at the same address. Say which one you are in the first line and it is answered faster.
- Investors What you invest in and the stage you come in at.
- Partners What you would want to build or integrate.
- Press Your outlet and your deadline in the first line.
- Working together What you have built. Working code beats a CV.