Security model
Pools Markets spans browser injection, account infrastructure, backend services, external data and onchain contracts. Security depends on keeping these responsibilities separate rather than treating one component as universally trusted.
Trust boundaries
| Boundary | Trusted for | Not trusted for |
|---|---|---|
| Host launchpad page | Display context and discovery hints | Account authority, market rules or settlement |
| Pools Markets extension | User intent, local presentation and transaction review | Inventing server or chain state |
| Backend | Discovery, orchestration, indexing and evidence preparation | Moving funds outside protocol authorization |
| Data providers | The fields assigned in a frozen source policy | Changing market meaning |
| Resolver quorum | Attesting a result from frozen rules and evidence | Rewriting those rules |
| Pools Markets contracts | Enforcing onchain position, settlement and payout state | Determining offchain facts without evidence |
| Intelligence models | Proposing structured question intents | Funds, executable rules or final outcomes |
Account security
Pools Markets accounts use a secure signing architecture so raw keys are not required for routine use. Sensitive import and export operations require explicit user action. Pools Markets does not ask users to connect an arbitrary external wallet to use the product’s primary account experience.
Users should verify the extension source, requested action, active network, amount and destination before approving a transaction.
Market integrity
Integrity controls include:
- frozen market and settlement specification hashes;
- deterministic template and eligibility rules;
- economic manipulation and exposure checks;
- stable idempotency keys for value-moving operations;
- finalized evidence requirements;
- resolver quorum rather than a single model response;
- payout accounting bound to the final market result.
Upgrade and operational risk
Diamond architecture permits modular upgrades and therefore requires transparent authority. A production release must disclose its upgrade owner, delays or governance, installed selectors and emergency powers.
Until audit reports and verified production deployments are published, Pools Markets should be treated as pre-production software.
Reporting
A dedicated security reporting channel will be published before production launch. Do not disclose exploitable account or contract details publicly before a reporting path is available.