Transaction Signing
Understand the different methods for signing transactions in AVM Studio.
Signing Methods
AVM Studio supports two primary methods for signing transactions:
Platform-Managed Accounts
Store encrypted keys in AVM Studio for convenient signing.
- Quick and easy setup
- No external software needed
- Keys encrypted at rest
- Best for development
External Wallets
Connect your own wallet via WalletConnect.
- Keys stay on your device
- Full control over signing
- Multi-device support
- Best for production
Platform-Managed Accounts
Creating an Account
- Go to Settings → Signing Accounts
- Click Add Account
- Choose to generate new or import existing mnemonic
- Give the account a recognizable label
- Save the account
Using for Signing
- When prompted to sign, select your platform account
- Review the transaction details
- Click Sign
Security Considerations
Platform-managed accounts store your private keys encrypted on our servers. For high-value Mainnet deployments, consider using an external wallet where you control the keys directly.
Viewing Your Mnemonic
You can view your account's 25-word recovery phrase:
- Go to Settings → Signing Accounts
- Click on the account
- Click Show Mnemonic
- Store it securely offline
External Wallets
Supported Wallets
- Pera Wallet - iOS and Android
- Defly - iOS and Android
- Any WalletConnect-compatible wallet
Connecting Your Wallet
- When prompted to sign, click Connect Wallet
- A QR code appears
- Open your mobile wallet app
- Scan the QR code
- Approve the connection request
Signing Transactions
- Build or initiate the transaction in AVM Studio
- Review the transaction details shown
- A signing request is sent to your wallet
- Review and approve in your wallet app
- Transaction is submitted
Tip
Keep your wallet app open during signing. The connection may time out if you take too long.
Reviewing Transactions
Always review before signing:
Key Details to Check
- Type - Payment, app call, asset transfer, etc.
- Recipient - Verify the destination address
- Amount - Confirm the value being sent
- Fee - Transaction fee in ALGO
- App ID - Contract being called (for app calls)
Red Flags
- Unexpected recipient address
- Unusually high fees
- Multiple transactions when you expected one
- Close-to address set (would empty your account)
Best Practices
- Use testnet first - Verify everything works before Mainnet
- Small test transactions - Send a small amount first
- Backup mnemonics - Store securely offline
- Separate accounts - Use different accounts for dev vs production
- External wallets for Mainnet - Maximum security for real value