Read access and signing are different responsibilities
A wallet integration belongs to a real application with a clear purpose. This site provides integration guidance and does not request accounts, signatures, or recovery phrases. Keep your own reading, connection, and signing flows separate.
Phantom
Phantom’s Solana connection documentation describes requesting permission to share the user’s public key. Read the provider’s current connection, rejection, and account-change behavior before designing your own flow.
Read Phantom’s connection documentation
Trust Wallet
Use the current browser-extension documentation to identify the networks and integration paths relevant to your application. Test the exact platform and method combination rather than assuming compatibility from a wallet name.
Read Trust Wallet’s extension documentation
MetaMask
Review MetaMask’s current connection options for the environment you intend to support. Keep provider discovery and user selection explicit, and treat network changes or rejected requests as expected application states.
Read MetaMask’s connection documentation
A practical integration review
State what connection does, give signing its own deliberate action, and show the intended account and network. Clear prepared actions when their context changes. Test cancellation, rejection, disconnection, and a return to the page after a pause.
Never ask users to send a private key or recovery phrase to support. Review the complete wallet connection checklist before adding prompts to your application.