Skip to content

v0.2.3 - Chronos

Choose a tag to compare

@github-actions github-actions released this 05 Aug 18:30
· 279 commits to main since this release

Release 006 · August 5, 2026 · Current
VEX 0.2.3
Your launches now carry the VEX mark on Trench Express.

A fast, focused release shipped hours after 0.2.2. Two things: tokens launched through Vex are now attributed on trench.express with a VEX badge, and a stuck corner of the Image Locker got unstuck.

01 · VEX badge on Trench Express

When a launch confirms, Vex now proves to Trench Express that it was the creator - cryptographically, with no shared secrets and no middleman.

01 Creator-signature attribution. The moment the create transaction confirms, the same wallet that signed it signs a short attestation naming the new token, and Vex sends that proof to Trench Express. Their site then shows the VEX mark on the token. Nothing about the launch itself changes: you stay the creator, your keys never leave your machine, and the attestation is a local signature over a fixed string - not a transaction, not an approval, not a fee.

02 It can never touch your launch. The attribution step runs after the launch and its fee are fully settled, and every failure path - a refused signature, a network drop, a provider error - is logged and retried later without being able to fail, delay or reorder the launch. A badge is cosmetic; a launch is real money, and the code treats them accordingly.

03 Durable retries, honest gaps. A background sweep retries unclaimed badges every two minutes from the stored signature. Tokens launched before this release have no stored signature, so the sweep names them as a gap instead of pretending; the whole flow was verified live on mainnet before shipping (badge granted 196 ms after confirmation).

02 · Image Locker fix

01 Stranded launch attempts no longer hold images hostage. A failed or abandoned launch attempt could leave its draft in a state that blocked deleting the attached image forever, even after a later launch with the same image succeeded. The delete guard now ignores attempts whose authorization window has lapsed and can never sign, while genuinely in-flight launches still protect their image. When a delete is refused, the locker now tells you which launch is holding the image and why.

03 · Before you update

One new database migration ships in this release (attribution columns on the launched-tokens table). It runs automatically on first start. No manual action is required.