Security & current limits.
The safeguards implemented for accounts, and the on-chain guarantees that do not exist yet.
Current application safeguards
- Private routes verify the Privy token signature, expiry, issuer and intended application.
- Draft and image access is checked against the signed-in account.
- Draft edits use revisions to prevent stale-window overwrites.
- Writes have bounded inputs and account-based request limits.
- Browser writes are checked against configured origins.
Programs, addresses and audits
No RESET launch program address, mainnet mint, fee vault, migration pool or deployed auction contract is published by this release. There is no completed independent security audit to cite. Application tests are not a smart-contract audit.
Upgrade authority, administrative powers, mint/freeze authority and emergency controls remain undefined until the on-chain system is implemented. No immutability or locked-liquidity guarantee is made.
What the app does not guarantee
The backend is an initial implementation. End-to-end account recovery, full authenticated user journeys, image-scanning coverage and production-scale resilience still require further validation.
Future market data can be delayed or incomplete. Future wallet analysis can be wrong. Batch pricing will not eliminate losses, market manipulation or smart-contract risk. No feature described as planned should be relied on as protection today.
Reporting a problem
There is no in-app support ticket system or published bug-bounty program yet. During this private development phase, report reproducible problems through the existing project conversation. Include the page, action, visible error and approximate time.
Do not include a seed phrase, private key, App Secret or access token in screenshots or reports. A request ID, if shown, is enough to help identify a failed API request.