rob thijssen
7fbcae31e4
Two halves of #6. **The approval screen names its recipient.** Moving call decoding onto @quantus/codec left `dest` rendering as 32 bytes of hex, because the codec has no business guessing an SS58 prefix. `metadataExpand` now tells it the one the chain's own metadata definition carries, so a transfer shows `qzkYEQv8tQsmniZYdame3Cku18RL5g9bGK9Pdydq5TMPdpE3y` rather than `0x300bb607…`. Somebody approving a transfer has to be able to check the recipient against what they meant to send to, and hex is the form nobody checks. Account ids are identified by registry path, not by length, so a 32-byte block hash still renders as hex — quantus/wasm has the test. **The fallback prefix is 189, not 42.** Upstream falls back to the generic Substrate prefix because it is a wallet for every Substrate chain and has no reason to prefer one. This one does: every account it can hold is a Quantus account, so 42 would show a correct address in a form no Quantus tool displays — the same account id, the same funds, an unfamiliar string. Somebody comparing the extension against quantus-cli or the mobile wallet would reasonably conclude they had created the wrong account. A chain's own ss58Format still wins where one is known, and the setting still overrides. Refs #6, quantus/wasm#3 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012uDUodEcRbBwNRi3UCmw8f
@polkadot/extension-chains
Definitions for chains that are supported by this extension. It contains the bare definitions as well as a stripped-down (call-only) metadata format.