']\n}}>\n\n### Stores\n\nThis package utilizes stores to expose the list of connected wallets and the user's currently selected wallet,\nmaking these available by importing and subscribing to the stores:\n\n```\nimport { selectedWallet, connectedWallets } from 'avm-wallet-svelte';\n\n{$selectedWallet.address}
\n{#each $connectedWallets as wallet}\n Connected Wallet: ${wallet.address} with ${wallet.app}
\n{/each}\n```\n\n### Signing Transactions\n\nSend transactions to the current selected wallet and sign them:\n\n```\nimport { signAndSendTransactions, selectedWallet, ProviderStore } from 'avm-wallet-svelte';\nimport { get } from 'svelte/store';\nimport algosdk from 'algosdk';\n\nconst fromWallet = get(selectedWallet); // current wallet selected by user\nconst toWallet = 'ADDRESS_OF_WALLET_TO_SEND_TO';\n\nif (fromWallet) {\n const algodClient = get(ProviderStore).algodClient; // get the algodClient provided to the component\n if (!algodClient) {\n throw new Error(\"Algod client not available\");\n }\n const params = await algodClient.getTransactionParams().do();\n\n const txn = algosdk.makePaymentTxnWithSuggestedParamsFromObject({\n from: fromWallet,\n to: toWallet,\n amount: 1000, // amount to pay in microAlgos\n suggestedParams: params\n });\n\n const allTxns: algosdk.Transaction[] = [];\n allTxns.push(txn);\n\n try {\n const status = signAndSendTransactions([allTxns]);\n // if you want to use a different algodClient instance\n // or if none was provided to the component:\n // const status = signAndSendTransactions([allTxns], algodClient);\n }\n catch(e: any) {\n // error handling -- future plan is to make error events consistent across wallets\n console.log(e.message);\n }\n}\n```\n\n### Authentication\n\nThis section needs more documentation. Web3Wallet accepts an optional boolean parameter `showAuthButtons`.\nIf true, users will see an `auth` option after connecting their wallet. Clicking `auth` will send a validation\ntransaction to their wallet. Once authenticated, the signed transaction is stored as a token in the browser's\nsecure cookie storage and can be used for authentication. Token expiration is currently hard-coded for 90 days\nwith plans to be customizable in the future.\n\n### Roadmap\n\n- Improve layout flexibility and add styling options\n- Consistent error handling\n","readmeFilename":"README.md"}