How to Use AlgoSigner and WalletConnect on Algorand

AlgoSigner and WalletConnect are not interchangeable. AlgoSigner is a browser-extension wallet connection that an Algorand dApp must support; WalletConnect is a separate connection protocol that requires a compatible wallet on the other side. Seeing a WalletConnect button does not mean it will connect to AlgoSigner.

Before you begin, check which connection methods the dApp supports and whether your wallet supports that method on Algorand. If it lists AlgoSigner, use the extension flow. If it offers WalletConnect, choose a wallet that explicitly supports WalletConnect for Algorand. If neither matches, stop rather than installing an unfamiliar extension or signing through an unexpected route.

Also confirm that the dApp is intended for the Algorand network and that you have enough ALGO for the transaction fee and any amount the contract requires. A connection alone does not execute a contract call: the dApp must prepare a transaction, and you must review and sign it in your wallet.

Do these checks before opening the connection prompt:

1. Use the dApp’s official name and address from a source you already trust. Lookalike sites can imitate wallet prompts.
2. Check browser-extension details. Confirm that AlgoSigner is the extension you intended to use and that it is available for your browser. Don’t install a copy from an unsolicited message or search advertisement.
3. Confirm compatibility. The dApp must explicitly support AlgoSigner, or your chosen wallet must support WalletConnect on Algorand. A generic WalletConnect option is not proof of Algorand support.
4. Prepare the right account and network. Keep only the account you intend to use selected, and verify the dApp is asking for the expected Algorand network.
5. Keep funds limited to what the action needs. A dedicated account can reduce exposure if you regularly use unfamiliar dApps.

AlgoSigner’s current availability and compatibility can change. Before relying on it, verify that the extension can still be obtained through a trusted channel and works with your browser and the particular dApp. If you cannot verify that, use a currently supported Algorand wallet rather than weakening browser security.

For an AlgoSigner-supported dApp, use its in-page AlgoSigner connection option. The names and screens can vary, but a safe flow should be recognisable:

1. Open the dApp and choose its AlgoSigner connection option—not WalletConnect unless you are using a separate wallet that supports that protocol.
2. When the extension opens, check the requested account and network. Approve only the connection you intended.
3. Return to the dApp and confirm that it displays the expected account. A displayed address is not proof that the dApp is trustworthy; compare it with the account in your wallet.
4. Start the specific action you want, such as calling an application or submitting a transaction group. Read the wallet prompt before approving anything.
5. After the action, check the transaction status in the wallet or a trusted Algorand explorer. If it fails, don’t repeatedly approve retries until you understand the cause.

A connection request should not require your recovery phrase or private key. Never enter either into a dApp, a support chat, or a pop-up claiming to be AlgoSigner. Wallet connections should use the wallet’s own approval screen.

If the dApp instead provides a WalletConnect option, use it only with a wallet that explicitly supports WalletConnect on Algorand. The usual process is to select WalletConnect in the dApp, scan its session QR code or open the offered wallet handoff, and approve the connection in the wallet. The labels and mobile or desktop handoff vary by wallet.

Before approving, check the dApp name and requested network in the wallet. A session connection lets the dApp send transaction requests to your wallet; it is not the same as approving a contract call. Review and approve each request separately. If the wallet reports an unsupported network or cannot display transaction details, cancel instead of guessing.

When you finish, disconnect the session from the wallet or dApp’s connection controls, especially on a shared device. Disconnecting ends the session but does not reverse transactions already confirmed on-chain. If AlgoSigner is the only wallet you have, and the dApp supports only WalletConnect, you’ll need a compatible Algorand wallet or a dApp that supports AlgoSigner; there is no automatic bridge between the two connection methods.

A smart-contract interaction may be a single application-call transaction or a group of related transactions. The request can include an application ID, arguments, account references, asset or payment transfers, and a network fee. The wallet may not explain what every argument means, so don’t sign a request you cannot relate to the action you chose.

Before approving, compare the wallet prompt with the dApp’s description:

• Is the application ID the one you expected?
• Does the requested network match your intended Algorand network?
• Are the accounts, assets, and amounts consistent with the action?
• Is the transaction group expected, with no unexplained payment or transfer?
• Does the wallet show a fee you can accept?

Algorand’s network fee is separate from any fee a dApp may charge. The total can depend on the number and type of transactions, and the wallet should show its network-fee estimate before you sign. Check any dApp charge separately; don’t assume a displayed network fee includes it. Fees and transaction details can change, so judge the live prompt rather than relying on an old estimate.

A signature approves a particular transaction, not a general promise that the dApp will behave safely. Once a transaction is confirmed on-chain, it generally cannot be reversed by asking the wallet or dApp to cancel it. Treat unexpected requests as a reason to pause.

Avoid these common mistakes:

• Choosing WalletConnect just because AlgoSigner is unavailable. The wallet and dApp must both support that protocol and Algorand.
• Signing a transaction you can’t explain. Cancel if the displayed application, accounts, assets, amount, or group differs from the action you intended.
• Trusting a dApp’s name or logo. Check you opened the intended service through a trusted route.
• Approving repeated prompts without checking status. A retry may create another transaction or repeat an action.
• Sharing recovery details. No legitimate connection flow needs your seed phrase or private key.
• Leaving sessions open unnecessarily. Disconnect when finished, particularly on a shared computer.

If you signed something suspicious, stop further approvals, disconnect the dApp, and review the account’s on-chain activity. If assets or account access may be at risk, move remaining assets to a secure account you control, taking care not to interact with the suspicious dApp again.

A missing connection often means the dApp and wallet do not support the same method, the extension is unavailable to the browser, or the wallet session is stale. Close the prompt, reload the dApp from its trusted address, and try the supported connection method once more. Don’t install unofficial fixes or share account secrets with support.

If the dApp connects but shows the wrong account or network, disconnect and select the intended account in the wallet before reconnecting. Don’t sign a request hoping the dApp will switch networks afterward. If a transaction is rejected, read the wallet’s explanation and check whether it was submitted before trying again; a pending or confirmed transaction can make a second attempt risky.

For a WalletConnect problem, confirm that the selected wallet supports Algorand and that the session is still active. For an AlgoSigner problem, verify the extension is present and that the dApp explicitly supports it. If you can’t establish compatibility or inspect the transaction details, stop and use a supported route rather than approving blindly.

Use this final check whenever a dApp asks you to interact with an Algorand smart contract:

• The dApp is the one you intended to open.
• The connection method matches your wallet: AlgoSigner integration or WalletConnect with a compatible Algorand wallet.
• The account and network are correct.
• The application ID and transaction group fit the action you chose.
• You understand any amounts, asset transfers, and fees shown.
• You have not been asked for a seed phrase or private key.
• You are prepared for the possibility that a confirmed transaction cannot be undone.

If any item fails, cancel and investigate. You can reconnect later; signing an unclear transaction may be irreversible. For valuable or unfamiliar contract actions, consider using a separate account with limited funds and testing only when the dApp’s instructions and wallet prompt agree. Never treat a successful connection, a familiar interface, or a transaction simulation as proof that a contract is safe.