Version 0.35.0

Your wallet address now links to the public chain record.

Whether anything has ever left your wallet is not a question you should have to take our word for. The address now carries a link to a public block explorer, where every transaction it has signed is listed by someone who is not us. A new wallet has no transactions, so this shows nothing on day one; the proof that works immediately is different, and it is already on the screen that opens the wallet — the same account code opens the same address on any device, which you can check for yourself right now.

NMTS no longer has anywhere to paste a private key.

The wallet screen used to offer, behind a disclosure, a box for pasting an external Sui private key. The key never left your device — but 「paste your private key here」 is the shape of every crypto phishing page, and while that shape existed anywhere in NMTS we could not say the sentence that actually protects people: NMTS never asks for your private key. Now we can, and if you already imported a key on this device nothing is taken away — you can still use it, switch back to your account-code wallet, and delete the stored copy. An extension wallet does the same job and our code never touches its key.

The account screen now shows the value you can actually compare.

Two opaque strings used to sit side by side: the account identifier and its fingerprint. They answer the same question, and only one of them can be checked by eye — the fingerprint, which is sixteen characters in groups of four. That one stays. The account identifier is a pointer to the row on our server, which is a fact about us rather than something for you to do, so it moved behind developer mode; both are still written into your recovery kit.

Locked down which certificate authorities may issue certificates for nmts.me.

Until now any certificate authority in the world could issue a certificate for this domain, and one mis-issued certificate is what lets somebody sit between you and this site while your browser still shows a padlock. A CAA record now names the only authorities allowed to issue, and every other one is refused at the authority itself. Nobody was affected — this closes a door rather than fixing a break. The browser is also told, from now on, to refuse plain http for this domain from a person's very first visit.