Skip to content

Releases

Signet 0.9.19: AirGap Vault, remote signers, Domains and help in the app

Choose a tag to compare

@drchrispinnock drchrispinnock released this 18 Nov 17:12

What's new in 0.9.19

Two new places to keep keys away from this Mac, AirGap Vault and remote signers, plus a Domains tab, help inside the app and fixes for Etherlink governance.

AirGap Vault

  • Add an account from AirGap Vault. In Vault, open the Tezos account and choose Pair Account (QR Code V3), then use Scan QR code… in Signet. Animated codes are read in any order. Signet works out the address from the public key itself and adds the account with an "AirGap" tag, like a Ledger account. The secret key stays on the phone.
  • Sign with Vault. When an AirGap account sends, stakes, transfers NFTs or approves a dApp operation, Signet shows the operation as a QR code (animated when long). Scan it with Vault, check and approve it on the phone, then hold Vault's signed reply up to the Mac's camera, or paste a screenshot. Signet uses the signature only if the reply answers that request, signs exactly the bytes it sent, and is valid for the account's key.
  • Tested live on Shadownet, including the first operation of a new account, which carries its reveal.
  • Vault signs operations only, so message signing (dApp sign requests, multisig proposals, Mt Pelerin's address check) is not available for Vault accounts.

Remote signers

  • Connect Remote Signer… (burger and Operations menus, and the welcome screen) adds an account whose key is held by a remote signer: octez-signer, Signatory, Russignol or anything else speaking the same protocol.
  • HTTP, HTTPS or TCP, starting from the usual ports (6732, 443 and 7732), and any port can be typed. Signet asks the signer for the key's public key and adds the account only if that key belongs to the address. The account is saved in octez-client's own form (tcp://host:7732/tz1…), so octez-client can use it too, and remote-signer accounts octez-client already had now sign in Signet.
  • Every signature the signer returns is checked against the account's key before anything is sent to the network. When a signer refuses, Signet says which signer, which request and which key, and quotes the signer's reason.
  • Limits: signers that require authenticated requests are not supported yet. Plain HTTP only reaches this Mac or the local network; use HTTPS or TCP for a signer elsewhere. tz4 keys need a signer that makes the BLS signatures the chain accepts today (for octez-signer, version 23 or later).

Dashboard

  • Activity. "Recent transactions" is now "Activity". A delegation from someone else reads " delegated", which is also right for an account you only watch.
  • Domains tab (Mainnet). Lists the Tezos Domains names the account owns or that point at it. Its primary name (the reverse record) comes first, and each name shows where it points, who owns it and when it expires (orange within 30 days, red once expired). Right-click a name to copy it or open it on Tezos Domains.
  • Account tags on the address line. "Watch only", "Ledger", "AirGap", "Remote signer" and the other tags now sit next to the address, so a long account name no longer squeezes them into a column.

Etherlink governance

  • Voting keys are found reliably. With Layer 2 on, Signet checks at launch which of your accounts are a baker's Etherlink voting key. Before, a failed balance or history read could hide Governance….
  • "Voting rights contract" setting in Networks, under the governance contracts. Mainnet starts with KT1Ut6kfrTV9tK967tDYgQPMvy9t578iN7iH; empty uses the contract the governance contracts name.
  • A voting key that is not a baker now gets Etherlink governance alone in the Governance sheet.

Help

  • Help > Getting Started opens the book's Getting Started chapter, with its screenshots, in a Signet window. It works offline and matches your version of Signet; links to other chapters open the book on Leanpub.
  • Help > Signet Website opens signetwallet.org.

Changes

Signet 0.9.18: Shadownet (Previewnet) for testing Etherlink 8

Choose a tag to compare

@drchrispinnock drchrispinnock released this 17 Nov 19:23

What's new in 0.9.18

A small release to make it easier to test Etherlink 8 on Shadownet Previewnet. Nothing changes on Mainnet or on the other networks.

Shadownet (Previewnet)

  • A new network, "Shadownet (Previewnet)". Tezos X Previewnet is a second Etherlink-style rollup running on Shadownet, where Etherlink 8 and other Tezos X features arrive first. The new entry is Shadownet on layer 1 with the Previewnet rollup as its Layer 2, in place of Etherlink.
  • Where to find it. Turn on "Enable Layer 2" for Shadownet in Networks…; "Shadownet (Previewnet)" then appears in the network badge and in Networks, under Shadownet.
  • Layer 1 is Shadownet itself. The same node, accounts, balances, faucet, history and shielded pool. dApps working on layer 1 Shadownet keep connecting to plain Shadownet.
  • Layer 2 is Previewnet, switched on from the start. The dashboard shows a "Previewnet" row under tez for tz1, tz2 and tz3 accounts. Bridge… deposits tez from Shadownet into Previewnet through Previewnet's own bridge contract, and Send can send on Previewnet. Signet checks that the node really serves Previewnet's chain (NetXY2oPPzkxUW1) before estimating or signing anything there.
  • Previewnet details. Michelson node michelson.previewnet.tezosx.nomadic-labs.com, rollup sr1BvTT7tVNneG2TeP18sixq57TxsZELebLu, bridge KT1DUaf49SNALJRSB8R45TvEtgVi2xZnCh8B, TzKT previewnet.tezosx.tzkt.io. The node can be replaced in Networks like any other Layer 2 node.

Known limits

  • dApps on Previewnet's Layer 2 can connect only by naming its node as a custom network, since Octez Connect has no network name for Previewnet yet.
  • Previewnet is reset from time to time. A reset changes the rollup address, so Signet will need an update after the next one.
  • Etherlink → Tezos withdrawals remain unavailable, as on Etherlink.

Under the hood

  • The QR scanning and recovery sheet code builds in the portable (non-Mac) version of Signet's core; nothing changes on the Mac.

Changes

Signet 0.9.17: QR code scanning, recovery sheets, NFTs by account

Choose a tag to compare

@drchrispinnock drchrispinnock released this 16 Nov 16:36

What's new in 0.9.17

Signet can now read QR codes with the Mac's camera, print a recovery sheet for an account and read that sheet back in, and files downloaded NFT artwork by account.

Scan QR code

  • A new "Scan QR code…" item in the burger and Operations menus opens the camera and reads a code held up to it. The item appears only while a camera is attached, and comes and goes as cameras do; an iPhone used as a Continuity Camera counts, and there is a camera picker when the Mac has several.
  • What a code does depends on what it is.
    • A dApp's Octez Connect or Beacon pairing code (the "pair wallet on another device" QR) opens dApps and pairs, exactly as a pasted code does. The dApp's permission request still has to be approved.
    • An address, or a public key (whose address is worked out locally), is shown with a choice of Add to Address Book… or Send….
    • A secret key or a recovery phrase opens Import account with it already filled in.
  • Clipboard and image files too. A camera cannot see a code on the Mac's own screen, so the sheet also has "Paste from Clipboard" (Cmd-V), which reads a screenshot of a code or a copied code, and "Choose Image…".
  • Nothing is acted on from the scan alone. Every code is handed to the sheet that already deals with that kind of thing. The scanner keeps and logs nothing, and the only scanned content it ever displays is an address.
  • macOS asks for camera access the first time; it can be changed later in System Settings under Privacy & Security.

Import accounts by QR code

  • "Import from QR code" on the welcome screen, when a camera is attached, is a new way in beside creating an account, importing a key and connecting a Ledger.
  • A scanned key goes through Import account, never straight in. The key arrives masked, and the name, whether to encrypt it with a password and whether to keep it only until Signet quits are chosen there as for a pasted key. An octez-encrypted key (edesk…) keeps its password, which is asked for.

Recovery sheets

  • "Recovery Sheet…" in Export secret key prints a one-page sheet for the account: the Signet logo and title, the account's name and the date, a QR code of the secret key, and the address, public key and secret key in full.
  • A password-protected key stays protected on paper. The sheet carries the encrypted key, not the clear one, and an empty box to write the password in by hand; the password is never printed. A key without a password gets a plain warning instead that the sheet alone controls the account.
  • Recovering is a scan. "Scan QR code…" reads the sheet and opens Import account with the key filled in. The code holds the key as text, so the printed key can also be typed into Signet or octez-client.
  • tz5 (post-quantum) keys print as several codes. A tz5 secret key is far too long for one QR code, so its sheet runs to four pages: the first as usual, two pages of eight numbered codes, and the key in full as numbered text. The scanner reads the codes in any order, several at a time if they are in view, says which parts it still needs, and accepts the result only when the parts belong together and the key's checksum holds. The multi-code format is Signet's own.
  • Signet sends the sheet to the system print panel and writes no file itself. Choosing "Save as PDF" there puts the key in a file on disk.

NFTs

  • Downloads are filed by account. Artwork saved with Download… now goes into a folder named after the account's address, inside the wallet directory's nfts folder, so collections of different accounts no longer mix.
  • A new "Arrange NFTs by address" switch in Settings, on by default, turns this off for those who prefer everything in nfts together. Files downloaded before this release stay where they are.

Under the hood

  • The camera and microphone permission prompts now describe scanning and speak of crypto exchanges rather than one provider.
  • The app is signed with the camera entitlement that the hardened runtime needs for scanning.

Changes

Signet 0.9.16: octez.js, Octez Connect 5.0.5

Choose a tag to compare

@drchrispinnock drchrispinnock released this 14 Nov 21:02

What's new in 0.9.16

Signet now talks to the chain through octez.js, Trilitech's fork of Taquito, with Octez Connect 5.0.5 for dApps. Receive no longer offers the Etherlink EVM-side address, ahead of the change Etherlink 8.0 makes to it.

Etherlink

  • Receive shows the Tezos address only. With Layer 2 on, Receive used to offer the account's address on Etherlink's EVM side and a "Link to Etherlink" step. Etherlink 8.0 replaces the way that address is derived, so an address shown or linked today would not be the account's after the upgrade, and tez sent to it could be stranded. The chain picker and the link step are gone until the new derivation is implemented. Bridge, Send on Etherlink, the Etherlink balance and Etherlink governance are unchanged.

Chain library

  • octez.js in place of Taquito. The bridge is built on @tezos-x/octez.js 25.1.0-rc.1, which has the same API as Taquito under other package names. This is a release candidate, pinned exactly; Signet moves to 25.1.0 when it ships. Nothing changes in what Signet shows or signs.
  • Injection is still never retried behind your back. octez.js's HTTP client retries a failed request once by itself, operation injection included. Signet switches that off, so a lost reply from the node remains an unknown outcome that Signet watches for and lets you resend as the same bytes, rather than something the library retries silently. The offline test for this now fails if an injection call never settles.

dApps

  • Octez Connect 5.0.5. Upstream tightens pairing and session handling (pairing replies must answer an issued request, senders must match the decrypting key, only the active wallet can change or end a session) and fixes a disconnect started by the dApp breaking the next connection.

Under the hood

  • The wallet folder and a few tests are arranged so the same sources build for Signet Go on iOS; nothing changes on the Mac.

Changes

Signet 0.9.15: dApp support on the Michelson Tezos X rollup

Choose a tag to compare

@drchrispinnock drchrispinnock released this 10 Nov 12:50

What's new in 0.9.15

dApp support on the Michelson Tezos X rollup: dApps that run on Etherlink's Michelson interface can now have their operations approved in Signet.

dApps on Layer 2

  • Tezos X networks are understood. Octez Connect names the Michelson interface of the rollup tezosx-mainnet and tezosx-shadownet. Signet could pair with a dApp on those networks, but an operation request ended in "The dApp wants the "tezosx-shadownet" network, which Signet does not have" and could not be approved. Such requests now go to the network's Layer 2 Michelson node with the rollup's chain id pinned: the batch is simulated, shown with its fee and effects, signed and watched into a block there, exactly as on layer 1.
  • Layer 2 must be turned on. Signet works with a dApp on a Tezos X network only while "Enable Layer 2" is on for that network in Networks, and uses the Layer 2 node set there. With it off, the request says which network's Layer 2 to turn on and offers only OK: there is nothing to connect or approve.
  • A dApp connected on both layers works on both. A dApp that had been granted the same account on a network and on its Layer 2 was refused with "Permission Not Granted" on whichever it connected to second, because only the first grant was checked. An operation is now checked against every grant the dApp holds for the account.

Under the hood

  • Each network carries the names dApps use for it and for its Layer 2, so another network that gains a Layer 2 needs only its identifier and node.
  • The release workflow passes the Developer ID and notary secrets to its scripts through the environment.

Changes

Signet 0.9.14: audit and bug fixes

Choose a tag to compare

@drchrispinnock drchrispinnock released this 07 Nov 15:40

What's new in 0.9.14

An audit and bug fix release: no new features. It answers the audit of 5 November 2026 (recorded in audit/AUDIT_20261105.md) and fixes a Send recovery bug. Shielded transactions remain HIGHLY EXPERIMENTAL, off by default and for test tez only.

Bug fixes

  • Send no longer gets stuck on an old operation. When a node's reply was lost, Signet keeps the signed operation until it sees it in a block. On a rolling node it could never find a block from weeks earlier, so Send reopened on "Not confirmed by the node" every time and the account could not sign anything new. Signet now forgets such a record once it can never be applied: the account's counter has moved past it, or its branch has expired. A record it cannot check is still kept.
  • dApps: "Send reply again" works. The dApp SDK dropped the pending request before the reply was delivered, so a retry after the relay failed could never succeed. The request is now kept until the reply is delivered.

Security (audit of 5 November 2026)

  • Logs. The bridge log now scrubs objects before writing them and redacts UUID seeds and keys written as decimal bytes, so dApp SDK log lines can no longer carry its communication key.
  • Shielded wallet file. It is now locked against other processes as well as other threads, so two copies of Signet cannot spend the same one-time key. It is read and written under one size limit, so it is never replaced by a file Signet could not read back, and backups read it under the same limit.
  • Shielded unshields and transfers. The record, with its exact payload, is saved before the operator is contacted and kept when the outcome is unknown, so the notes it spends stay reserved. The sheets offer Submit again to resend the same payload; only the operator's own refusal frees the notes. A timeout or rate limit (408, 409, 425, 429) no longer counts as a refusal.
  • Shielded keys are backed up at once, after a new wallet, address, deposit pool or record, rather than at the next launch.
  • Rollup figures are checked. Levels must be in range and sums over figures from the rollup report overflow instead of trapping.
  • Plainer warnings. The Shield, Shielded address and Shielded settings sheets say that the shielded master key is stored unencrypted, that the proving service sees the witness, and when the operator or rollup node is reached over plain HTTP.

Under the hood

  • The portable core builds on FreeBSD as well as Linux; nothing changes on macOS.
  • Test fixes: the live shield test expects a proof for withdrawals that are already cemented, and the tz5 send test runs on Quantumnet only.

Changes

Signet 0.9.13: NFT transfer, burn and download

Choose a tag to compare

@drchrispinnock drchrispinnock released this 02 Nov 12:32

What's new in 0.9.13

The NFTs tab learns to do things with your tokens: right-click one, or a selection, to transfer, burn or download them. Nothing about shielded transactions changed: they remain HIGHLY EXPERIMENTAL, off by default and for test tez only.

NFTs

  • Select tiles like files. Click a tile to select it, Cmd-click to add or remove one, Shift-click for a range, click the background to clear. The right-click menu acts on the clicked tile, or on the whole selection when the tile is part of it.
  • Transfer… sends one or many NFTs to an address, a .tez name or one of your own accounts, with the same recipient lookup as Send. Tokens held in several editions get a stepper for how many to send. Everything goes in one operation with one FA2 transfer call per contract, and the fee, gas and storage that were estimated are exactly what is sent. On Etherlink the recipient must be a tz1, tz2 or tz3 account; a selection cannot span Tezos and Etherlink.
  • Burn… is a transfer to the conventional burn address tz1burnburnburnburnburnburnburjAYjjX, behind an "I understand" switch, since FA2 has no standard burn entrypoint and the tokens are gone for good.
  • Download… saves the full artwork of one or many tokens, the video, sound or full-size image rather than the tile's thumbnail, into the nfts folder of the wallet directory (~/.signet/nfts by default), named after the token, its contract and its id. A sheet shows each download's progress with a Show in Finder button.
  • Links and copies. A single token's menu also offers Open in Explorer, Open on objkt.com (mainnet), View Artwork, Copy Contract Address and Copy Token ID.
  • Soulbound tokens (TZIP-21 isTransferable false, such as attendance proofs) cannot be transferred or burnt and the menu says so; the same goes for accounts Signet cannot sign for.

Staking

  • The delegate row says "This baker accepts staking" rather than "stakers".

Under the hood

  • The models, services and view models now build on Linux and the BSDs, and the wallet, backup and octez-client directories follow $HOME off the Mac, groundwork for a command-line version. Nothing changes on macOS.

Changes

Signet 0.9.12: Etherlink governance (beta), NFT ordering

Choose a tag to compare

@drchrispinnock drchrispinnock released this 29 Oct 16:42

What's new in 0.9.12

Etherlink governance arrives as a beta, and the NFTs tab gets two small improvements. Nothing about shielded transactions changed: they remain HIGHLY EXPERIMENTAL, off by default and for test tez only.

Etherlink governance (beta)

  • Vote on Etherlink kernel upgrades from the Governance sheet. Etherlink's upgrades are decided by Tezos bakers through governance contracts on layer 1, one for slow upgrades and one for fast. With Layer 2 on, the Governance sheet gains a Tezos / Etherlink picker. The Etherlink tab shows the current period of each process, its proposals and tallies and your voting power, and lets a baker, or an account a baker has delegated its Etherlink vote to, submit or upvote a kernel hash in a proposal period and vote yea, nay or pass in a promotion period. Each vote goes through the usual fee estimate and confirmation. Mainnet's current governance contracts are built in; the Networks sheet lets you point at others.
  • Why beta. Reading the contracts is checked live against mainnet, but no vote has been sent through Signet yet: there is no testnet deployment of these contracts, so the first real vote will be the first exercise of the sending path. If you are a baker, check the operation in the explorer after voting and please report what you see.

NFTs

  • Newest first, across both layers. The NFTs tab orders tiles by when each holding last changed, so with Layer 2 on an NFT minted on Etherlink's Michelson interface takes its place by date instead of trailing the Tezos ones.
  • Videos and sounds are marked. A token whose artwork is a video or a sound only has a still to show, often a marketplace's generic placeholder such as hic et nunc's black disc. Such tiles now carry a play (or speaker) badge, with a tooltip saying what the tile is.

About

  • The credits list the icon and audit on their own line.

Changes

Signet 0.9.11: tokens without indexer metadata

Choose a tag to compare

@drchrispinnock drchrispinnock released this 29 Oct 15:57

What's new in 0.9.11

One fix, for tokens the indexer has not described yet. Nothing about shielded transactions changed: they remain HIGHLY EXPERIMENTAL, off by default and for test tez only.

Assets and NFTs

  • A token whose metadata the indexer has not resolved now appears. Signet sorts an account's tokens into the Assets and NFTs tabs from the metadata TzKT reports (decimal places for an asset, an image for an NFT), so a token TzKT listed without any metadata was shown on neither. Mainnet's TzKT resolves a freshly minted token's metadata within minutes, but Etherlink's TzKT resolves none at all, so an NFT minted on Etherlink's Michelson interface never showed. For such a token Signet now reads the metadata itself: the contract's on-chain token_metadata entry through the same indexer, then the TZIP-21 document it names from the IPFS gateways or a public HTTPS address, with the same size limits and address checks as artwork. Fields the contract states directly on chain override the document. A dozen such tokens are resolved per refresh and the results are remembered for the session. This also covers a mainnet token in the minutes after its mint.

Changes

Signet 0.9.10: Etherlink activity on the dashboard, NFT artwork fix

Choose a tag to compare

@drchrispinnock drchrispinnock released this 29 Oct 14:26

What's new in 0.9.10

A small release for Etherlink and for NFT artwork. Nothing about shielded transactions changed: they remain HIGHLY EXPERIMENTAL, off by default and for test tez only.

Etherlink

  • Etherlink operations appear in Recent transactions. With Layer 2 turned on for the network (Networks… in the menu), the account's operations on Etherlink's Michelson interface are read from Etherlink's indexer and merged into the Recent transactions list with the layer 1 ones, newest first. An Etherlink row carries a small Etherlink logo beside its amount, its tooltip starts with "On Etherlink", and clicking it opens Etherlink's explorer rather than the Tezos one. If Etherlink's indexer cannot be reached, the layer 1 list is shown alone. An account the rollup does not accept (tz4, tz5) has no Etherlink history.
  • Assets and NFTs do the same. Tokens and NFTs the account holds on Etherlink's Michelson interface join the Assets and NFTs tabs, marked with the same logo (beside a token's amount, at the top left of an NFT tile), and "View in explorer" on such a token opens Etherlink's explorer. Etherlink's indexer lists no tokens on the Michelson side as of this release, so in practice these tabs show only Tezos holdings for now; the wiring is in place for when contracts appear there.
  • Tezos and Etherlink toggles. While Layer 2 is on, two logo buttons sit to the right of the Recent transactions / Assets / NFTs picker. Both are on by default; turning one off hides that chain's rows on all three tabs, and an emptied tab says which chain has nothing. The buttons are absent while Layer 2 is off.

NFTs

  • Some NFT tiles showed a black disc instead of the artwork. Marketplaces such as hic et nunc give thousands of tokens one generic thumbnail, a black disc. Once any token had put that thumbnail in the artwork cache, every later token carrying it got the disc from the cache before its own display render was ever fetched. The cache is now consulted image by image in the same order as the download, so a cached placeholder no longer stands in for a render that was never requested. Affected tiles correct themselves on the next launch.

Changes