Hi team,
I maintain SSP Wallet — open-source browser extension wallet. Our submission has been in review for 3+ months, and we’re ready to ship v1.39.0 with Solana support and important fixes our users
are waiting for.
Every submission we send already includes:
- Full source code
- Reproducible / deterministic builds — any reviewer can rebuild the exact ZIP from the public git tag
- Reviewer notes documenting build steps, dependencies, endpoints, and permission justifications
The same builds clear Chrome Web Store and our mobile apps clear Apple/Google review within hours.
I understand AMO is fighting a flood of malicious submissions, and that work matters. So my real question is: what more can a project like ours do to land in a faster lane? If reproducible
builds + open source + reviewer notes + a clean review history isn’t enough signal, we’d genuinely like to know what is — and we’ll do it.
Is there a lighter-touch path for established, reproducibly-built, open-source extensions after N clean reviews? If not, would the team consider one? I’d happily contribute to defining the
criteria.
Thanks for the work you do.
SSP Wallet - MultiSig Crypto Wallet – Get this Extension for 🦊 Firefox (en-US)