Already known = sent; Transactions always on the home screen (0.5.12) #70

Merged
backmeupplz merged 1 commit from fix/already-known into main 2026-11-02 14:24:21 +00:00
Owner

"already known" (geth/op-geth; transaction already imported on anvil; known transaction on Besu) means the node already holds these exact signed bytes. Here that was an earlier collect attempt at the same nonce and fees, which signs identically. It's submitted, just not included yet. Plain Wallet passed it to the site as an error. Now broadcast() returns keccak256(signed) as the hash and lists the transaction under Transactions, where it can be sped up.

Transactions button is always on the home screen. Before, it waited for a first recorded transaction, and recording only started in 0.5.11. With nothing recorded, the list says "Nothing sent from this wallet yet. Transactions it sends from now on show up here, kept only on this device." (23 languages).

Release 0.5.12, notes in 24 store languages.

Tested: npm test, tsc, npm run build, store-copy. On anvil, broadcasting the same signed transaction twice: the node answers transaction already imported, broadcast returns the same hash both times, the list keeps one entry, and status is pending. In headless Chrome with a fresh disposable wallet, the home screen shows Transactions and the dialog shows the empty state.

🤖 Generated with Claude Code

**"already known"** (geth/op-geth; `transaction already imported` on anvil; `known transaction` on Besu) means the node already holds these exact signed bytes. Here that was an earlier collect attempt at the same nonce and fees, which signs identically. It's submitted, just not included yet. Plain Wallet passed it to the site as an error. Now `broadcast()` returns `keccak256(signed)` as the hash and lists the transaction under Transactions, where it can be sped up. **Transactions button** is always on the home screen. Before, it waited for a first recorded transaction, and recording only started in 0.5.11. With nothing recorded, the list says *"Nothing sent from this wallet yet. Transactions it sends from now on show up here, kept only on this device."* (23 languages). Release 0.5.12, notes in 24 store languages. **Tested:** `npm test`, `tsc`, `npm run build`, store-copy. On anvil, broadcasting the same signed transaction twice: the node answers `transaction already imported`, `broadcast` returns the same hash both times, the list keeps one entry, and status is pending. In headless Chrome with a fresh disposable wallet, the home screen shows Transactions and the dialog shows the empty state. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Already known = sent; Transactions always on the home screen
All checks were successful
Store release / select-stores (pull_request) Has been skipped
Store texts / check (pull_request) Successful in 33s
Store release / build-apple (pull_request) Successful in 2m13s
Store release / build (pull_request) Successful in 2m57s
Store release / github-release (pull_request) Has been skipped
Store release / submit-apple (pull_request) Has been skipped
Store release / report (pull_request) Has been skipped
947d18f179
A node answering "already known" (or "transaction already imported") holds
these exact bytes: an earlier try at the same nonce and fees signs
identically. It was shown to sites as an error; now broadcast() returns the
transaction's hash like any send and lists it, so it can be sped up from
Transactions. The Transactions button no longer waits for a first recorded
transaction, with an empty state. Release 0.5.12.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
backmeupplz deleted branch fix/already-known 2026-11-02 14:24:22 +00:00
Sign in to join this conversation.
No description provided.