Home / Articles / The user keeps the meter / Versions / v1.4.0
The user keeps the meter: what changed in v1.4.0
From v1.3.0 (2026-10-21, 66d2d429f) to v1.4.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 95 unchanged. About 0 words added and 71 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot um-parties.webp | images/ | The proposed design.design: Thea user's browser appends its activity, and adds credit when it pays, to a billing vault, signed by the user. The admin vault reads it, reads payments fromvault, Stripe, and commits validations back, signed by the admin. The upload server checks the validated credit through a small credits API beforeand itthe acceptsupload an upload.server. | narrow | architecture
37 unchanged paragraphs, under In short {#in-short}, The old problem {#problem}, What we already have {#have}…
!shot um-topup.webp | images/ | A top-up, step by step.step: The user pays through athe payment link, comes back, and their browser adds the credit straight away with a signed claim. Later,claim, the admin's browser reads recent payments from Stripe, matches the claim, and commits a signed validation. The upload server reads that validation and checksthe it.upload server's check. | architecture
56 unchanged paragraphs, under Credit now, validated later {#when}, Who are we defending against? {#threat}, A vault shared by two parties {#shared}…