Launching
Wallet & Security
How wallet control and transaction approval are designed to work.
AutoPad is designed around a non-custodial wallet model.
Your wallet controls your funds
AutoPad should not need access to seed phrases, private keys, or wallet recovery phrases. Never share a seed phrase or private key with AutoPad, support staff, or anyone claiming to represent AutoPad.
Connecting a wallet
Connecting a wallet allows AutoPad to identify the public wallet address and request permitted wallet actions. A wallet connection alone should not give AutoPad permission to move funds.
Signing transactions
When a launch is ready:
- AutoPad prepares an unsigned transaction.
- The transaction is sent to the connected wallet.
- The wallet displays a signing request.
- The user reviews the transaction.
- The user chooses whether to sign.
Always verify before signing
Users should review wallet prompts carefully. Do not sign a transaction you do not understand or that contains unexpected instructions.
Security roadmap
Production security should include transaction simulation, smart-contract review, dependency auditing, rate limits, monitoring, abuse prevention, incident-response procedures, and third-party security audits where appropriate.