Part of #1. The extension still presents itself as "polkadot{.js} extension". It becomes blackbeard, sharing the sigil and palette of blackbeard.observer.
Visible
Manifest name and short_name become blackbeard, and default_title and page <title>s follow.
Description: a post-quantum wallet for the Quantus Network.
Icons (16–128) and favicon are rendered from observer's sigil.svg, which also replaces the header's pjs.svg.
The accent colour moves from polkadot orange (#FF7D01) to the sigil's gold (#BD8829).
The remaining "polkadot{.js}" UI strings: the header fallback and the phishing page.
Behavioural, and why they are part of this
The name dapps find us under changes from window.injectedWeb3['polkadot-js'] to 'blackbeard'. With the real polkadot{.js} extension also installed, both wrote the same key and one silently replaced the other. qapi console's extension list gets a label for the new name.
Message channel names follow short_name (EXTENSION_PREFIX, used to namespace page and content-script messages). Sharing polkadot{.js} with the real extension meant each content script answered the other's page messages.
Firefox add-on id changes from upstream's {7e3ce1f0-…} to extension@blackbeard.observer, so Firefox no longer treats this as polkadot{.js}.
Storage keys stay exactly as they are. Four stores prefixed their keys with EXTENSION_PREFIX unless it was literally polkadot{.js}, so renaming would orphan every account and wallet already stored. chrome.storage is per-extension already, so the prefix adds nothing there; the keys become fixed.
Not in scope
The @polkadot/extension-* package names. They aren't user-visible, and renaming them touches every import in the monorepo and the forks.
A full dark-theme palette change.
Part of #1. The extension still presents itself as "polkadot{.js} extension". It becomes **blackbeard**, sharing the sigil and palette of blackbeard.observer.
## Visible
- Manifest `name` and `short_name` become `blackbeard`, and `default_title` and page `<title>`s follow.
- Description: a post-quantum wallet for the Quantus Network.
- Icons (16–128) and favicon are rendered from observer's `sigil.svg`, which also replaces the header's `pjs.svg`.
- The accent colour moves from polkadot orange (`#FF7D01`) to the sigil's gold (`#BD8829`).
- The remaining "polkadot{.js}" UI strings: the header fallback and the phishing page.
## Behavioural, and why they are part of this
- **The name dapps find us under** changes from `window.injectedWeb3['polkadot-js']` to `'blackbeard'`. With the real polkadot{.js} extension also installed, both wrote the same key and one silently replaced the other. qapi console's extension list gets a label for the new name.
- **Message channel names** follow `short_name` (`EXTENSION_PREFIX`, used to namespace page and content-script messages). Sharing `polkadot{.js}` with the real extension meant each content script answered the other's page messages.
- **Firefox add-on id** changes from upstream's `{7e3ce1f0-…}` to `extension@blackbeard.observer`, so Firefox no longer treats this as polkadot{.js}.
- **Storage keys stay exactly as they are.** Four stores prefixed their keys with `EXTENSION_PREFIX` unless it was literally `polkadot{.js}`, so renaming would orphan every account and wallet already stored. `chrome.storage` is per-extension already, so the prefix adds nothing there; the keys become fixed.
## Not in scope
- The `@polkadot/extension-*` package names. They aren't user-visible, and renaming them touches every import in the monorepo and the forks.
- A full dark-theme palette change.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #1. The extension still presents itself as "polkadot{.js} extension". It becomes blackbeard, sharing the sigil and palette of blackbeard.observer.
Visible
nameandshort_namebecomeblackbeard, anddefault_titleand page<title>s follow.sigil.svg, which also replaces the header'spjs.svg.#FF7D01) to the sigil's gold (#BD8829).Behavioural, and why they are part of this
window.injectedWeb3['polkadot-js']to'blackbeard'. With the real polkadot{.js} extension also installed, both wrote the same key and one silently replaced the other. qapi console's extension list gets a label for the new name.short_name(EXTENSION_PREFIX, used to namespace page and content-script messages). Sharingpolkadot{.js}with the real extension meant each content script answered the other's page messages.{7e3ce1f0-…}toextension@blackbeard.observer, so Firefox no longer treats this as polkadot{.js}.EXTENSION_PREFIXunless it was literallypolkadot{.js}, so renaming would orphan every account and wallet already stored.chrome.storageis per-extension already, so the prefix adds nothing there; the keys become fixed.Not in scope
@polkadot/extension-*package names. They aren't user-visible, and renaming them touches every import in the monorepo and the forks.