SECURITY
CONTROLS / 09
Security is part ofthe product.
SOLVRENX uses a managed-wallet architecture, authenticated sessions, and server-side controls for privileged operations. We describe what exists. We do not claim any system is unhackable.
01
Controlled wallet architecture
Signing for managed wallets runs through controlled infrastructure. Seed phrases and raw private keys are not surfaced in client UI.
02
Secure authentication
Web and app access use InsForge authentication (email registration, verification, and session refresh). Privileged app routes require a signed-in, onboarded user.
03
Server-side privileged operations
Rewards, treasury settlement, and sponsored network fees are authorized on the server. Clients are not the source of truth for those actions.
04
Auditable financial events
Application ledgers record buy, sell, reward, and withdrawal events for operations review — alongside on-chain settlement where it applies.
05
Transaction monitoring
On-chain history is indexed and synced into the app so users can inspect activity rather than trust a screenshot.
06
Role-based administration
The admin console is separated from the public site, with roles, audit logging, and feature flags for sensitive capabilities.
07
Rate limits
Sensitive edges apply rate limits. This reduces abuse; it is not a guarantee against all automated attacks.
08
Security logging
Administrative and treasury-adjacent actions are written to audit trails for operators.
09
Controlled treasury operations
Buy, sell, and withdrawal capabilities are flag-gated and require pricing, inventory, and policy checks before they can complete.
No security control makes a product “100% secure.” Report suspected issues through official SOLVRENX channels when those addresses are published.