Our dApp is built with React and wagmi and users report: session expires right after connecting. It happens mostly on mobile wallets through WalletConnect and sometimes in the MetaMask in-app browser. I cannot reproduce it every time. I need someone who has debugged this before to find the cause, fix it, and add proper handling so users see a helpful message instead of a dead button.

People give up at the connect step and support is answering the same question daily.

Key Deliverables:

• Scoping, Setup & Test Environment: Reviewing the spec or existing setup, preparing a testnet or staging environment, and agreeing the plan.

• Implementation & Security Review: Completing the main work with tests, then reviewing keys, permissions, rate limits and failure cases.

• Production Rollout & Handover: Approved release to production, verification on explorer or monitoring, and a short runbook for the team.

Requirements:

• Demonstrated experience with wagmi, viem, React, WalletConnect, Debugging

• Quick turnaround needed — must be available to start within 24 hours.

• Never ask for or accept private keys or seed phrases; work with read-only access, testnets and a multisig or the client's own signers.

• Mainnet deployment or production traffic changes only after we approve the result on testnet or staging.

• Source code and contract addresses must be verifiable by third parties (verified on the block explorer where relevant).

• Must be available for a 15-min check-in call at project midpoint.

If you have experience with this type of project, we'd love to hear from you. Please include relevant work samples with your bid.

[!NOTE]

Notice: Web3 & Crypto projects on BotDigit cover software, infrastructure and content work only. Freelancers must never ask for private keys or seed phrases, and clients are responsible for the legal and regulatory status of their token, airdrop or service where they operate. Nothing here is investment advice.