Skip to content

Releases

NUTCADE v1.24.0

Choose a tag to compare

@Random21m Random21m released this 22 Nov 04:19
56ff7a9

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.24.0: optional mint reliability (MintRadar)

  • Settings > Privacy > Show mint reliability (OFF by default). When you switch it on, NUTCADE downloads MintRadar's whole public list of mint health (one request, about every 5 minutes at most) and compares it on your phone. MintRadar sees your phone's internet address, but never learns which mints you use, because NUTCADE never asks about a single mint.
  • Labels on your mints and in Add mint: a small symbol and word: Reliable, Shaky or Mint down. A mint that is not online counts as down, because its score is then old.
  • Suggested mints (up to five) when you add a mint: online, a Reliability Score of 80 or more, sats, and the standard mint and melt features.
  • A notice if a mint where you hold sats is reported down. Nothing moves by itself.
  • It is an operational health signal only. It is not a statement that a mint holds your sats or is safe to deposit into. It never blocks, moves or chooses anything for you. If MintRadar is offline, rate-limited or answers with garbage, NUTCADE shows no label and no error. The setting is not part of a backup file.
  • Also includes the polish from v1.23.1.

Known issues

The earlier known issues in the README still apply.

  • GitHub's code scanning still shows one alert on the phone-backup record line from v1.23.0 (public, signed "remove my copy" messages only, no key or secret).
  • Back up with my phone has been tested with a stand-in passkey, not yet on a real iPhone or Android phone.

Checks

  • One independent review: no rule violations; its small findings (a duplicate-request race, a stalled-download timeout, name spoofing characters, Add-mint layout shift) were fixed.
  • All 16 GitHub test jobs passed on this code (one flaky Maze replay check failed once, then passed on its one re-run). Local: radar 76, trust 380, backup 117, polish 210.
  • Sonnet built this release (non-money).

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

cc13e2094a71f03bbd0e64cbbe2b0e23243af126db688cb3a942f7394fd09e7b  index.html
74a5f56ef158ceb2b43e3b6635006ace64ff3ed883339e61adb2b0718a878a12  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.23.1

Choose a tag to compare

@Random21m Random21m released this 22 Nov 02:31
da047f4

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.23.1: polish (no new features)

  • Very big balances (over 9,999,999 SAT) now fit on a small 320 px screen.
  • "NO PLAYS YET" no longer shows next to the waiting-deposit line.
  • Back up with my phone: cancelling the passkey step now removes the unused passkey it made; backup copies with the same timestamp are handled.
  • Tests only: one flaky backup test line was fixed.

Known issues

The earlier known issues in the README still apply.

  • Back up with my phone has been tested with a stand-in passkey, not yet on a real iPhone or Android phone.
  • GitHub's code scanning still shows one alert on the line that saves the phone-backup record. It holds only public, signed "remove my copy" messages, no key or secret.

Checks

  • One independent review of this release: no money problem.
  • All 15 GitHub test jobs passed on this exact code (commit da047f4) before the site updated.

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

f6b06df0dcbd7bd64065943297aeea793889ea34b4724b39673d0a79877a683b  index.html
38b84a4708959ee8460f6b7a466df55f2829883ecffe1669aa084ebe71a03278  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.23.0

Choose a tag to compare

@Random21m Random21m released this 22 Nov 01:18
7d79a1f

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.23.0: better backup file, Back up with my phone

  • Password on the backup file (optional): Settings > Backup > Download backup can lock the file with a password (PBKDF2 and AES-256-GCM). Import asks for it; a wrong password changes nothing. Old plain backup files still import.
  • More in the backup file: contacts, settings, trophies and arcade progress now travel with it. Everything from a file is checked before it is used, so a changed file cannot add a payee that pays someone else.
  • Back up with my phone (optional, new): a passkey (Face ID or fingerprint) locks your 12 words and the locked copy is kept on Nostr relays. On a new phone, Restore with my phone brings them back. No server of ours is involved. The 12 words stay your main backup. The option is hidden where the phone or browser cannot do it. The duress wallet is never backed up this way.

Known issues

The earlier known issues in the README still apply.

  • Back up with my phone has been tested with a stand-in passkey, not yet on a real iPhone or Android phone. Where it cannot work it says so and saves nothing.
  • Resetting the wallet deletes the phone backup (the Reset screen says so). A reset through Forgot PIN cannot, because the wallet is locked; a relay that is down or ignores deletions can also keep the locked copy.
  • GitHub's code scanning shows one alert on the line that saves the phone-backup record. It holds only public, signed "remove my copy" messages, no key or secret.

Checks

  • Three independent Opus reviews. The first found a hostile backup file could add a contact that pays someone else; the second found the Reset screen did not say it also deletes the phone backup; the third found a fast relay holding an old copy could win over newer ones. All three were fixed, and the last review found no money problem.
  • All 15 GitHub test jobs passed on the same code before the site updated (the run on commit 7d79a1f, which is what main now holds: the 1.23.0 code of commit eac1876 plus one tests-only fix; the app files are identical to eac1876). Local: backup 116, trust 380, pinguard 237, storage 79, polish 210, r8 328 of 329 (a PIN-timing check that passed on GitHub).

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

1da99a0c600caae8ead68d6859c56a0b3c04d4f63d54046e6103ad63388a9d5d  index.html
f6034b77204157139a4e74b66ad9968e7ca33de2e28c62b090809e28ea6b59a9  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.22.3

Choose a tag to compare

@Random21m Random21m released this 21 Nov 14:21
5692ed2

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.22.3: unpaid receive note hidden, price chart link

  • On-chain receive: the note made when Receive > on-chain shows an address (the down arrow with WAIT) is hidden from Recent and Notes until a payment arrives. The record is kept and shows as soon as it is paid. A small line "Waiting for an on-chain deposit · Show address" on the home screen is the way back to the address and to Stop watching.
  • Price chart: the "turn off in Settings" link now opens Settings at Privacy > Show Bitcoin price.

Known issues

The earlier known issues in the README still apply.

Checks

  • Two independent Opus reviews of the change: no money problem. The first found that hiding the note removed the way back to the address, which is now fixed. The second found no real bugs.
  • All test suites passed on GitHub before the site updated: yes (the run on the same code as the release). Local: trust 380/0 and polish 0 failures.
  • The first deploy hit GitHub's Pages hiccup (artifact metadata) and passed on one rerun of the same commit.

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

d028b748f16fe7c968546034ae666d07a11d18372247b349dd2539d084cac35e  index.html
a6e2a1ac5535d24ac15dc2fdf837ab835c4131f31e6887729e94c1ee186faf36  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.22.2

Choose a tag to compare

@Random21m Random21m released this 21 Nov 12:34
19b5eab

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.22.2: security tidy-up

Nothing you use changes. This release touches the backup import and the treasure-hunt lists (money-adjacent code), so it had an independent check.

  • Imported backups: text in a backup file (transaction, request and contact ids, hunt keys) is now escaped when drawn, and imported hunts and clue entries must have a 64-hex key and real numbers, so a hand-edited backup can no longer put script on the screen.
  • Treasure hunts: the clue-card list has no prototype and is read with an own-key check.
  • Random numbers: the pretend coins used only to estimate Send all fees, and the random padding of the decoy vault, now use the secure random generator.
  • Initials are cleaned again when a high score is saved.

Known issues

The earlier known issues in the README still apply. A few GitHub code-scanning alerts stay open on purpose: they are in test code or are false positives (every value drawn into a sheet goes through the escape helper); they are dismissed on GitHub with reasons.

Checks

  • Two independent Opus reviews of the diff and an audit of every place text could reach the page unescaped: one real path found (imported backups) and fixed, one follow-up number check found and fixed.
  • All test suites passed on GitHub before the site updated: yes (the run on the same code as the release). Local suites on this release did not finish cleanly in the review container; GitHub's run is the test result.

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

9d56af19a2afd33bb22fa2db5949e42c849b1026e7df8a67690ef8ab1386f2ab  index.html
9447953f48681587aff5f964e5a3461ed18981e5842c0606a9aef9e007c87460  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.22.1

Choose a tag to compare

@Random21m Random21m released this 21 Nov 10:55
930d429

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.22.1: new support address

This release touches the address the tip button pays (money-adjacent). Nothing else changed.

  • New support address: npub1qh7gzgypv0zjf6txpg679nwye2ue405cxp5ktt3ftw8kmdgnh83qpsdq60@npubx.cash. The Support screen, its QR code and LNURL, the tip button and the README all use it. The old address is no longer shown. Check that the address on the Support screen matches the README before you send anything.
  • Privacy: the tip button now asks npubx.cash for the invoice, so npubx.cash is named in the Privacy list and in Help (npub.cash is still used only for your own Lightning address).

Known issues

The earlier known issues in the README still apply.

Checks

  • Test payment: the owner sent 100 sats to the new address before any change and reported it paid.
  • QR: the new code reads back as the LNURL of the new address (two separate readers).
  • One independent Opus check: no money problem found.
  • Local suites: trust (after one test limit fix), games_smoke and tokens passed; all test suites passed on GitHub before the site updated: yes, all jobs (the first deploy try failed on a GitHub Pages error, not on code; a rerun from the Actions page deployed the same commit).

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

fbd065b862be0f8d05507db9b21c375b464300f1a4f466ae7b3fb68146747dff  index.html
b687f9419e8e96c73373209ed4527e01d9be9221cd81810573f6528e26d6a1bc  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.22.0

Choose a tag to compare

@Random21m Random21m released this 21 Nov 04:16
f24db6f

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.22.0: Send all

This release touches how payments are made (money code).

  • Send all. A "Send all" link next to the amount when you send ecash, pay a Lightning address or LNURL, or send on-chain. It uses everything held at the active mint, less the fees. The confirm screen shows the real amount and the real fee before anything is sent; Cancel changes nothing.
  • Ecash: the biggest token that fits your balance after the token's own fee. A sat or two can stay at the mint when one more sat would cost more in fees; the confirm screen says so.
  • Lightning address / LNURL: the amount is your balance minus the fee from the quote. A Lightning invoice with a fixed amount has no Send all. A few sats can come back as change because unused fee reserve is returned.
  • On-chain: the amount and fee are worked out again for each fee speed the mint offers.
  • Safe by design. The spending limit, PIN and piggy bank apply as for any payment. If your balance changes between the confirm screen and the send, nothing is sent. Fees as big as the balance, or an amount below the mint's or address's minimum, are refused with a clear message. A failed payment leaves every coin.

Known issues

The earlier known issues in the README still apply. Not in this release: Send all on the contact pay screen and on zaps; a mint that accepts only a few coins per request can make ecash Send all fail without sending anything; a successful on-chain Send all could only be tested against faked mint answers.

Checks

  • One independent Opus check: no money problem found.
  • Local suites: sendall 60/60 (grid test: zero fee, input fees, fee as big as the balance, dust, several mints, changed quotes, limit and PIN, failed payments), trust 378/378, r7 209/209, storage 79/79, r8, tokens and polish (1007 checks, 0 failed); all test suites passed on GitHub before the site updated: yes, all jobs (the one Neon Road replay check failed once and passed on rerun).

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

329aa75fe58bf266cc857b49e97e780c1a7e34fded1c131804e14c42288ed330  index.html
c69239e42ac64b864a84448a90b79598dfe27bdcc384b6dc636794f231599d81  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.21.0

Choose a tag to compare

@Random21m Random21m released this 21 Nov 01:03
1681dd2

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.21.0: Storage safety

This release touches how the wallet is saved (money code).

  • No more silent save failures. If the browser can't save your wallet (storage full), NUTCADE says so in red on the wallet screen, with Try again, Download backup and a pointer to Find lost ecash. It clears itself when saving works again. While a save is failing, Lock and Reload wait so nothing only held in memory is thrown away, and nothing new is asked of a mint until the counters are saved.
  • A warning before it fails. Settings, Backup shows how much storage NUTCADE uses; the wallet screen warns at 70% and 90% full.
  • iPhone Home Screen reminder. In Safari as a website, with sats in the wallet, the wallet screen reminds you to add NUTCADE to your Home Screen (Safari can delete a website's data). Steps sheet included; also shown during setup.
  • A failed save no longer lets older saved data be read back over coins you just received.

Known issues

The earlier known issues in the README still apply. Not in this release: a way to trim old history when storage is full; a messy history line after an "already signed" answer from a mint; a pending deposit quote that waits up to 14 days (closing it sooner could lose a deposit).

Checks

  • One independent Opus check found one money problem (an unrelated write could clear the "can't save" warning early); fixed, then a fresh independent Opus recheck of the fix: clean for money.
  • Local suites: wallet 51/51, pin 28/28, pinguard 237/0, r8 329/0, trust 378/0, storage 79/79; all test suites passed on GitHub before the site updated: yes, all jobs.

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

f3497b75637e5a4e99622f8d06336b4267d33fe2b05265a12cc33cc0b0fc8efd  index.html
ef9fadd68408b03cb43db41c52b06711d3d4288105f2d18b05d603f096c1854d  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.20.2

Choose a tag to compare

@Random21m Random21m released this 20 Nov 20:59
0dbf1ad

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.20.2: two small wording fixes

Nothing in this release touches money.

  • A deposit that was finished again after an interrupted answer now says "+X received", like any other arrival (it used to say "Recovered").
  • Saved ecash claimed after you come back online no longer shows a "Back online" toast next to its own arrival notice.

Known issues

The earlier known issues in the README still apply.

Checks

  • One independent check of the change: clean (no balance or book code touched).
  • Trust suite 378/0 and arrive suite passed locally; all test suites passed on GitHub before the site updated.

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

757f8c1cab89ffa790ca18364076721dfd88e7c9e6cc130a4136db3b7ebcb8e6  index.html
91119fd344b979cb84db67a642a5d6e58cf966f961264cf2a08e40ff8a25838e  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm

NUTCADE v1.17.0

Choose a tag to compare

@Random21m Random21m released this 20 Nov 04:04
dcc6a7d

Play it: https://random21m.github.io/nutcade/ · Add it to your home screen: steps for every device

New in v1.17.0: trust and help (no money code changed)

  • Help & FAQ: Settings → Help. Short answers in plain words, offline, in five languages: what ecash and a mint are, what your 12 words are, what to do on a new phone, fees, the PIN, updates, and a Privacy answer that lists every service NUTCADE contacts and why. It also tells you how to report a problem, privately if you prefer.
  • Check your 12 words: a quick check a week after your backup and again twice a year, so you know your backup works before you need it. It happens on your phone only.
  • What's new: after an update, one short note says what changed, and NUTCADE tells you when a new version is ready to load (it waits until no money step is open).
  • Mint details: Mints → Details shows each mint's contact, terms and description.
  • Hide amounts: tap your balance (or the eye beside it) to show ••• instead of amounts on the wallet, notes and mints screens, and in arrival notices, their Details, the phone notification and the "received" messages. Payment screens always show the real amount.
  • Your initials: change the three letters on your high scores and challenges any time, in the Arcade or in Settings, and optionally rename the scores already on your phone.
  • Backup: Settings → Backup shows when you last made a backup file.
  • Text: the welcome text now says ten cabinets.

Known issues

The v1.16.0, v1.15.0, v1.14.2, v1.14.1 and v1.14.0 notes in the README still apply. Small things we found and put on the list for 1.17.1 and the final polish: with amounts hidden, the piggy-step and mint-move menus can still show an amount if opened at the wrong moment; the What's new note links to the checksums file, which only works once that file is published. In our tests, two checks in the arrival suite failed in some runs and passed in others (one also on v1.16.0, which is live now): one about a cut-off claim at a mint you removed that sometimes finds a second waiting record for the same token, and one about a balance line in an old-record case. Both passed in the final run before this site updated. We have not found the cause yet; they are the first items for 1.17.1.

Checks

  • One independent check on a mid model found nothing that blocks and nothing that touches money; its notes went on the list above.
  • All test suites passed on GitHub before the site updated (the final run, after fixes to translations and to tests).

Verify

gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt with the key in nutcade-signing-key.asc (fingerprint 2509 D115 03B7 2CBF BCB5 408F 4B72 9F05 6A52 9340).

Checksums

215a9af72f742e8ed7e2bbca7cf7bc88fdffc5824d6a04468e0f35f3db797cb3  index.html
7743f7eea912dfd7c76d8523d471267588e650d8a4e97408dbed8fe51dae0b2f  sw.js
5003fb4b88c4fbd1fd518a2fd8c8ad365c519e183a08c03a322dddfea3cea84e  zxing_reader.wasm