Security
Contracts
| Contract | Polygon PoS mainnet |
|---|---|
| PolysiaFactory (production) | Not deployed yet. It will be deployed after the professional audit, owned by the Polysia multisig (Safe), with verified source on Polygonscan. The address will be published here — use only the address on this page. |
| USDT (USDT0) — token Polysia accepts | 0xc2132D05D31c914a87C6611C10748AEb04B58e8F |
Design: one immutable factory; every payment address is a minimal proxy (CREATE2) that only the factory can flush; sweeps are permissionless and pay the business's own Hot Wallet; the platform fee is computed and paid on-chain in the same transaction. Fee-recipient and Hot Wallet changes are two-step; operator fee increases have a 3-day timelock.
Reviews so far
- Smart contracts: 100+ Foundry tests (unit, fuzz, invariant suites, forked-mainnet tests against the real USDT0 token), Slither static analysis, Halmos symbolic checks, two automated audit scans (AuditAgent) and independent AI-assisted reviews of each version. Every accepted finding was fixed with a regression test; the remaining accepted risks are documented. A professional audit is planned before the production deployment.
- Gateway software (API, payment pages, webhooks): an internal security review followed by two external reviews; 22 findings (2 high, 9 medium, 11 low/info) were reproduced with failing tests and fixed, and one reported issue could not be reproduced (hardened anyway). Areas checked without findings include cross-business isolation, webhook SSRF protection and template escaping.
Release signing
Releases and updates are signed with an Ed25519 key kept offline. The public key is built into Polysia and into
install.sh; an install refuses anything not signed by it, and never installs an older version. The key
fingerprint will be published here after the key ceremony.
Report a vulnerability
E-mail [email protected] with steps to reproduce. Please do not open a public issue. We answer within 3 working days and credit reporters who wish to be named.