This page is for developers building Algorand dApps that integrate with MyAlgo Wallet. Connection patterns (WalletConnect v2, AlgoSigner-compatible APIs), supported transaction types, signing workflows, and references to the Algorand SDKs are documented below. For end-user wallet documentation, see /faq and the per-feature pages.
Connection patterns
WalletConnect v2 (recommended). MyAlgo Wallet implements the WalletConnect v2 protocol. Your dApp uses the official WalletConnect SDK; users pair their MyAlgo Wallet via QR code or pairing URI; transactions are requested through WalletConnect's standard methods.
Legacy AlgoSigner-compatible API. For dApps originally built against AlgoSigner (the deprecated Algorand browser extension), MyAlgo provides a compatibility layer. The API surface mirrors AlgoSigner's signTxn and accounts methods. New dApps should use WalletConnect v2; the AlgoSigner compatibility layer exists for transition rather than as a recommended path.
Supported transaction types
MyAlgo supports the full set of Algorand transaction types:
- Payment (ALGO transfers)
- Asset transfer (ASA sends)
- Asset opt-in (zero-amount self-transfers)
- Asset configuration (asset creation, modification, destruction — for asset issuers)
- Application call (smart contract invocation)
- Application state read/write (via standard application call mechanics)
- Atomic transfer groups (up to 16 transactions)
- Rekey (signing-key changes)
- Key registration (participation key for staking nodes)
Algorand SDK references
MyAlgo's signing flow is compatible with the canonical Algorand SDKs. For your dApp construction:
- JavaScript:
algosdk— official Algorand SDK - Python:
py-algorand-sdk - Go:
go-algorand-sdk - Java:
java-algorand-sdk
Construct unsigned transactions using the SDK; transmit them to MyAlgo via WalletConnect; receive signed transactions back; broadcast.
Best practices
- Display transaction details clearly in your dApp before requesting signatures — users sign more confidently when they understand what they're approving.
- Test with the public testnet before mainnet deployment. Testnet ALGO is freely dispensable from the Algorand testnet dispenser.
- Handle signing errors gracefully. Users may reject signatures, time out, disconnect, or have insufficient balance. Failed signing is normal user behavior, not an exceptional case.
- Don't request more permissions than necessary. WalletConnect v2 supports scoped permissions; request the minimum scope your dApp needs.
Open documentation
The Algorand developer portal at developer.algorand.org is the canonical resource for Algorand network documentation.
Related on-site references: ASA and smart-contract support, security architecture, latest updates.