v5.1.3

5.1.3 is a bug-fix release: a database containing a token with neither an account name nor an issuer refused to open, and a single such token blocked every other token from loading. It is a follow-up to the 5.1.1 fix for issuer-only tokens (#458).

Fixes

• FIX: a database (or import) containing a token with neither an account name nor an issuer refused to open on 5.1.x with "Token N has neither a label nor an issuer", locking you out of all of your tokens. Such tokens now load with a synthesized Unknown N placeholder label instead of being rejected, so the database opens and the token stays usable and editable. Interactive manual entry and editing still require a name (#462, follow-up to #458)

---

sha256: 2027d760599e75572d1d297a1bff2f2e7f26534b376d5e287a6fa4d921383f0c