grenade

grenade pushed to quantus-keypair-types at quantus/common

2026-09-15 08:28:06 +00:00

49f3442e5c build: version the forked packages 14.0.3-quantus.1, not upstream's 14.0.3

grenade opened issue quantus/extension#10

2026-09-15 08:23:12 +00:00

Air-gapped signing: port the QR flow from Parity Signer to multipart UR

grenade opened issue quantus/extension#9

2026-09-15 08:22:54 +00:00

Address QR: show and scan a plain SS58 string, not polkadot-js's payload

grenade commented on issue quantus/extension#2

2026-09-15 08:09:06 +00:00

Build against the Quantus forks instead of the published @polkadot packages

The "how are the forks consumed" question is answered and in place. Option 2 — a private registry.

Published

Gitea's npm registry at https://git.lair.cafe/api/packages/quantus/npm/:

grenade pushed to quantus-restore-account at quantus/ui

2026-09-15 08:08:49 +00:00

f2a1ab3a72 build: consume the forked @polkadot packages from the registry, drop the scaffolding

grenade pushed to quantus-keypair-types at quantus/common

2026-09-15 08:08:32 +00:00

b39241c840 build: take @quantus/crypto from the Gitea registry, not a symlink

grenade transferred repository quantus/observer to blackbeard/observer

2026-09-15 07:42:11 +00:00

grenade renamed repository from blackbeard.observer to blackbeard/observer

2026-09-15 07:41:53 +00:00

grenade commented on issue quantus/ui#1

2026-09-15 07:41:13 +00:00

ui-keyring: restoreAccount cannot rebuild a Quantus public key from an address

Done, on quantus-restore-account (ec1399f3). 5 specs; 46 tests pass repo-wide, build clean.

The fix

Exactly as this issue framed it — solved in quantus/common#3 first, then mirrored.…

grenade created branch quantus-restore-account in quantus/ui

2026-09-15 07:40:57 +00:00

grenade pushed to quantus-restore-account at quantus/ui

2026-09-15 07:40:57 +00:00

ec1399f3f3 fix(ui-keyring): restoreAccount cannot rebuild an ML-DSA public key from an address

grenade transferred repository quantus/miner to blackbeard/miner

2026-09-15 07:40:29 +00:00

grenade pushed to quantus-keypair-types at quantus/common

2026-09-15 07:33:25 +00:00

74e1e0cc6a feat(util-crypto): export quantus-cli wallet files

grenade opened issue quantus/common#8

2026-09-15 06:54:07 +00:00

Export quantus-cli wallet files

grenade pushed to quantus-keypair-types at quantus/common

2026-09-15 06:44:12 +00:00

e55352aa4e feat(util-crypto): import quantus-cli wallet files

grenade commented on issue quantus/extension#8

2026-09-15 06:34:48 +00:00

UX decision: match upstream wherever the crypto allows, and where it does not

Correction to the body: the CLI-import work is quantus/common#7, not #8 — that number is this issue. The conversion lives in common because it is keyring-adjacent and testable there; the…

grenade opened issue quantus/common#7

2026-09-15 06:34:40 +00:00

Import quantus-cli wallet files

grenade opened issue quantus/extension#8

2026-09-15 06:34:16 +00:00

UX decision: match upstream wherever the crypto allows, and where it does not

grenade commented on issue quantus/common#3

2026-09-15 06:27:21 +00:00

keyring: account backup and restore is impossible for Quantus as the format stands

Correcting reason (1) in the comment above — it was overstated, and the record should not carry it as written.

What the upstream extension actually stores

Checked rather than assumed:

-…

grenade closed issue quantus/common#3

2026-09-15 06:19:25 +00:00

keyring: account backup and restore is impossible for Quantus as the format stands