Releases / 0.2.3

Release 006

Release 006 · VEX 0.2.3

Your launches carry the mark.

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.

This page summarizes the work merged since 0.2.2.

Creator signature attribution · Verified live on mainnet

196

Milliseconds between the launch confirming and the VEX mark appearing on the token at Trench Express.

The VEX mark inside an attestation bracket

01 · Attribution

Proved, not claimed.

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, whether a refused signature, a network drop, or a provider error, is logged and retried later without being able to fail, delay, or reorder the launch. A badge is cosmetic and 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, with the badge granted 196 ms after confirmation.

02 · Image Locker

Stranded attempts stopped holding 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 that can therefore never sign, while genuinely in flight launches still protect their image. When a delete is refused, the locker tells you which launch is holding the image and why.

03 · Before you update

Upgrade notes.

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