Repository navigation
Goblin 172
Pre-releaseGoblin 172
This is a pre-release. The in-app updater keeps offering Build 171 until this build passes an on-chain check by the project owner: a send and a receive with a payment proof, checking an older proof, a rescan, and a send right after a cold start. Then 172 becomes the latest release. Until then you can install it by hand, and 171 stays the fallback.
If your wallet has Tor on, check it now. In our tests today, Build 171 with Tor on started Tor but reached no relay, on Android and on desktop. Build 172 connected in under 3 seconds on the same network at the same time. Three weeks ago the same check passed on Build 170. We have not found the cause yet. Without a relay, a Tor-on wallet cannot send or receive payments by username. Build 172 fixes that, so install it by hand if your wallet shows no relay connection.
Build 172 moves Goblin to the GRIM v0.3.6 wallet libraries, fixes a payment message that could be lost when it arrived as its wallet closed, and makes every screen and document say what Tor really does: it is your choice, per wallet.
Changed
- Tor is your choice, per wallet. A new wallet starts with Tor off, and the privacy step during setup offers a large Tor switch. Settings → Privacy → Tor routing turns it on or off at any time. New in this build: a wallet you add later from the wallet list also starts with Tor off. It has no privacy step, and before this build it started with Tor on without asking. A wallet with no recorded choice, such as one made by an older build, keeps Tor on.
- With Tor on, relays, username lookups and price fetches go over Tor. With Tor off they connect directly. The Grin node connection is direct either way.
- App text that said traffic always goes over Tor now stays true with Tor off: the receipt, the send review screen, the About page, the pairing note, the welcome screen and the username step. The README says the same.
Fixed
- A payment message that arrived a moment after its wallet closed could be lost. The closing wallet's old session handled it, failed, and marked it done. Now that session leaves the message on the relay, and the wallet handles it when it next opens.
- A wallet with many small coins could be offered an amount it cannot send: such a wallet cannot spend its whole balance in one transaction, because the transaction would be too big for the chain. The send screen now learns the real maximum and shows "You don't have enough grin" above it, as it does for an amount over the balance.
- The crash check from Build 171 now sits in front of the GRIM v0.3.6 slatepack parser. That parser returns an error for most of the crafted input that crashed the old one, and it checks what it reads after decrypting, so a crafted encrypted slatepack pasted by hand can no longer close the app. That was the one gap Build 171 left open. A passphrase-encrypted slatepack still crashes the new parser, so Goblin's own check stays in front and refuses it first. One check was dropped because the new parser reads that case safely: a payment proof signature with its top bits set. Proof verification still refuses such a signature. The 108 real slatepacks of every shape still pass, and the 8 hostile ones are refused.
- Integrated node: the new Grin node code refuses a malformed bitmap segment from a peer, which could crash the integrated node, and on Android the whole app. It also fixes how the chain database grows. The sync status now says which header download is running ("PIHD" for the parallel one).
- The integrated node's mining (stratum) server now caps each request line at 64 KiB. A miner connection that never ends its line can no longer grow memory without limit; only that connection is closed.
Under the hood
- GRIM v0.3.6 wallet libraries: the wallet submodule is at 9cc6a5eb, with the Grin node nested inside it at b76bf21a. The separate node submodule is gone, so the two cannot drift apart. A fresh clone of this build fetches its submodules from upstream. The Build 171 wallet pin is no longer on the upstream server.
- Tor on Linux and macOS: the new Tor library (arti 0.44, was 0.43) refuses a Tor data folder that other users can read, and earlier builds created it that way. Goblin now makes the folder owner-only before Tor starts, so a wallet with Tor on still reaches its relays after the update. Windows and Android are not affected.
- Fewer duplicate libraries: one ring (0.17; ring 0.16 was unmaintained, and the seed file format is unchanged) and one tokio. The stratum server moved off tokio 0.2, so tokio 0.2 and its old dependencies are gone, 18 packages in all.
- A Grin node that stops answering no longer holds a wallet request open: node requests time out after 60 seconds, as in GRIM.
- Payment proofs are now built and checked with the new pin's ed25519 code. This is one reason this build waits for the on-chain check.
- Security updates, lock file only: libz-sys 1.1.31, openssl 0.10.80, zstd-sys 2.1.2, zstd-safe 7.4.0, zstd 0.13.4, rustix 1.1.6 and tokio 1.54.1. Open advisories, both counted with today's advisory database: 38 for Build 171, 8 for Build 172. Of the 8, zip 0.5.13 (4 advisories) comes with the Grin node code, curve25519-dalek 3.2.0 with the wallet library's age crate, and rsa and libsqlite3-sys with arti. crypto-bigint is the eighth.
- 413 tests now, 406 in Build 171. New: the stratum line cap, the proof signature case, four for the close race, and one for the wallet-list Tor default. The wallet library's own local-chain tests pass at the new pin, 18 of 18: payment proofs, transactions, invoices, slatepacks, self send, no change, file and repost. No change to the Nostr payment message format.
- Checked live on desktop: crafted payment messages sent through a relay were refused, or in the proof-signature case read without harm, with no crash, and a real payment request still arrived. A message sent just after its wallet closed showed up after the next open. Two new wallets connected to relay.floonet.dev over Tor and synced from a public node.
- Updates checked: wallet data written by Builds 170 and 171 opens in 172 with no change, and opens again in the older build. On the Android emulator, 171 updated to 172 kept the wallet, the identity and the seed file, Tor connected, and six launches had no crash. A new install starts with the Tor switch off.
- Still open: a flood of junk messages can delay incoming payments until a restart.
Android packages are debug signed, as every Goblin release has been.