README "Non-Goals for 1.0": Ethereum mainnet and the Sepolia testnet are in scope, other chains are not. No other README line limited the wallet to mainnet; "shown on mainnet only" in the native-currency section is about the USD price line and is still true.
The provider flag in src/content/inpage.js stays. Its comment now says it is an interface-compatibility flag many dApps check, kept as a written exception, and points to where that is written: the README's Policies section and the no-competitor-names rule in RULES.md.
script/check-censored is unchanged. It already allows the flag only as that exact literal, only in src/content/inpage.js and its built copies under dist/, and fails on the name anywhere else.
Not visible in the diff: the new README and RULES.md text describes the flag instead of spelling it. Spelling it would make script/check-censored fail on those files, and allowing it there would widen the exception beyond the flag.
Disclosures:
Judgement call: script/check-censored also allows the name in three places that were documented before this PR (README "Third-Party Data Files" and the script's header): script/vendor-blocklist, the second provider identifier in src/content/inpage.js (the object wagmi probes), and one token's on-chain name in src/shared/tokenList.js. This PR neither adds them to the written exception nor removes them.
Deviation: the code comment says "a written exception", not "the one", because that second identifier is in the same file.
RULES.md is marked owner-maintained; this edit rests on the ruling linked above.
Model: opus-5-5
Resolves https://git.eeqj.de/sneak/AutistMask/issues/165 as ruled in https://git.eeqj.de/sneak/AutistMask/issues/165#issuecomment-132663.
- README "Non-Goals for 1.0": Ethereum mainnet and the Sepolia testnet are in scope, other chains are not. No other README line limited the wallet to mainnet; "shown on mainnet only" in the native-currency section is about the USD price line and is still true.
- The provider flag in `src/content/inpage.js` stays. Its comment now says it is an interface-compatibility flag many dApps check, kept as a written exception, and points to where that is written: the README's Policies section and the no-competitor-names rule in `RULES.md`.
- `script/check-censored` is unchanged. It already allows the flag only as that exact literal, only in `src/content/inpage.js` and its built copies under `dist/`, and fails on the name anywhere else.
Not visible in the diff: the new README and `RULES.md` text describes the flag instead of spelling it. Spelling it would make `script/check-censored` fail on those files, and allowing it there would widen the exception beyond the flag.
Disclosures:
- Judgement call: `script/check-censored` also allows the name in three places that were documented before this PR (README "Third-Party Data Files" and the script's header): `script/vendor-blocklist`, the second provider identifier in `src/content/inpage.js` (the object wagmi probes), and one token's on-chain name in `src/shared/tokenList.js`. This PR neither adds them to the written exception nor removes them.
- Deviation: the code comment says "a written exception", not "the one", because that second identifier is in the same file.
- `RULES.md` is marked owner-maintained; this edit rests on the ruling linked above.
Model: opus-5-5
The README's 1.0 non-goal said Ethereum mainnet only, while Sepolia
ships as a selectable network. It now puts mainnet and Sepolia in scope
and other chains out of it.
The injected provider's flag named after the other wallet stays, as an
interface-compatibility flag many dApps check. It is now written down
as an exception to the rule against naming competitors, in the README's
Policies section and in RULES.md, and the comment beside it says so.
Neither document spells the name, so script/check-censored, which
already allows the flag only in src/content/inpage.js and its built
copies, is unchanged.
Model: opus-5-5
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.
Resolves #165 as ruled in #165 (comment).
src/content/inpage.jsstays. Its comment now says it is an interface-compatibility flag many dApps check, kept as a written exception, and points to where that is written: the README's Policies section and the no-competitor-names rule inRULES.md.script/check-censoredis unchanged. It already allows the flag only as that exact literal, only insrc/content/inpage.jsand its built copies underdist/, and fails on the name anywhere else.Not visible in the diff: the new README and
RULES.mdtext describes the flag instead of spelling it. Spelling it would makescript/check-censoredfail on those files, and allowing it there would widen the exception beyond the flag.Disclosures:
script/check-censoredalso allows the name in three places that were documented before this PR (README "Third-Party Data Files" and the script's header):script/vendor-blocklist, the second provider identifier insrc/content/inpage.js(the object wagmi probes), and one token's on-chain name insrc/shared/tokenList.js. This PR neither adds them to the written exception nor removes them.RULES.mdis marked owner-maintained; this edit rests on the ruling linked above.Model: opus-5-5
PASS
Model: opus-5-5