The fix. A launch with any prebuy refused with the launch cost changed since you were shown it, and pressing review new price produced the same refusal forever. The preview's identifier carries the creation fee read at a specific block, but the submit check was comparing it against the full amount to send, which is the fee plus your prebuy. Those two numbers are equal only when the prebuy is zero, which is why every zero prebuy launch worked and every other one was impossible. The check now compares the fee, as the identifier always intended.

The gap behind it. No test had ever driven a real preview into a real submit. One suite hand wrote an identifier of one shape while another asserted the opposite shape, and the two never met. That end to end path is now covered with a nonzero prebuy, so this class of mismatch cannot come back silently.

What it does not do. This release makes both sides agree on the fee. It does not yet bind the exact form you previewed to the one you submit, because the app keeps no record of the quote it issued. That work is designed and comes next.

Every image looked broken, and did not. The dry run reported a digest mismatch for every staged image, fell back to simulating an empty one, and told you the launch would refuse. The launch would not have refused. Two parts of the app spelled the same hash differently, and the comparison now accounts for that, so the gas estimate reflects the image you actually staged, which is several times higher than an empty image estimate.

The preview can price a prebuy. Pass one and the simulation, the gas estimate, the fee, and the totals all include it, instead of leaving the arithmetic to be done by hand. The affordability verdict now states which scenario it priced.

A launched token appears in your balances. VEX pins it for you when the launch confirms, so you no longer have to add it by hand to see what you just paid for.

The agent's own instructions stay out of your chat. In one session the model printed parts of its operator instructions into the conversation, including wallet addresses. The instruction blocks are now explicitly delimited, with a stated rule never to repeat them, and text pulled in from documents or memory cannot forge those delimiters.

One definition for the metadata limits. Name, symbol, description, and link limits now live in one place shared by every part of the app that checks them, so they cannot drift apart.