If your agent integrates Web3 features like DeFi or NFTs, focusing on the following details can make a big difference in the overall user experience.
MetaMask is still a go-to wallet for many, but its UI can feel outdated—and more importantly, it doesn’t automatically detect malicious smart contracts. To deliver a smoother and safer experience, consider recommending alternative wallet extensions (all supported by MyShell) right in your bot’s welcome message. Popular options to highlight include:
OKX Web3 Wallet
**https://chromewebstore.google.com/detail/mcohilncbfahbmgdjkbpemcciiolgcge**
Rabby Wallet
**https://chromewebstore.google.com/detail/rabby-wallet/acmacodkjbdgmoleebolmdjonilkdbch**
By recommending these alternatives, you empower users with more modern and secure tools for interacting with Web3.
Currently, most transactions on MyShell occur on the Binance Smart Chain (BSC). Utilizing public RPC (Remote Procedure Call) endpoints to broadcast transactions exposes users to the risk of Miner Extractable Value (MEV) attacks, such as sandwich attacks. These exploits can lead to unnecessary financial losses for users.
Therefore, before initiating any transaction steps, it's crucial to advise users to employ privacy-focused RPC endpoints that offer anti-MEV protection. This process may involve users manually adding these RPCs to their wallets. It's essential to first inform users about the potential risks associated with using public RPCs and then provide clear instructions or links to relevant tutorials on how to configure a secure, anti-MEV RPC.
By proactively guiding users towards anti-MEV solutions, you can significantly enhance their security and prevent frustrating financial losses.
MyShell currently uses PancakeSwap’s liquidity pools for token swaps. To avoid failed transactions due to low liquidity, always instruct users to include WBNB (Wrapped BNB) as one of the tokens in the swap—either as the base or quote asset. Swapping between two non-WBNB tokens often leads to errors from insufficient liquidity.
Clearly communicating this requirement to users will prevent confusion and ensure smoother, more reliable token swaps.
On the blockchain, every transaction is assigned a unique identifier known as a Transaction Hash (Tx Hash). This value allows users to quickly and easily locate and track the status of their submitted transactions on the blockchain explorer. To provide transparency and empower users to verify their actions, it's imperative to retain and display the Tx Hash in the final step of every transaction process. This allows users to confirm that their transaction has been successfully broadcast and included in a block.
By consistently providing the Tx Hash, you instill confidence in users and enable them to independently verify the outcome of their interactions with your agent.