Requests

Interacting with decentralized applications (dApps) involves actions called requests. There are three main types of requests: sign-in requests, signing requests, and connection requests. Each type allows for secure interactions with dApps while ensuring your private information remains protected.

Sign-in requests allow you to securely connect and prove ownership of your wallet to a dApp, typically using Sign In With Ethereum (SIWE) or similar protocols. These protocols establish a secure connection, enabling you to interact with the app while keeping your Private Keys safe. Signing in to a dApp only requires proving ownership of your wallet, without exposing sensitive information.

Signing requests are prompts for you to authorize an action by cryptographically signing it with your Private Key. This proves your ownership of an associated wallet address, without revealing sensitive information. These requests are commonly used for authentication, transaction confirmation, and data validation.

Establishing connections between your cryptocurrency wallet and a decentralized application involves establishing a secure link. You can initiate the process by clicking on the “Connect Wallet” button within an dApp/website interface and then scanning the generated QR code with Family, or connecting directly from within Family’s in-app browser. The connection process does not expose your Private Key to the dApp, ensuring that your funds remain secure.

You can disconnect your wallet from dApps when you no longer need to interact with the app or want to maintain your privacy. Disconnecting a wallet from a dApp typically involves clicking a “Disconnect” or “Log Out” button within the app interface, or can be initiated directly within Family. It is a good practice to disconnect from dApps when they are not in use to minimize potential security risks.