A parent or elderly relative decides to hold a small amount of cryptocurrency—perhaps as a hedge, a gift, or simply to understand what the technology does. The decision to begin raises an immediate practical problem: most cryptocurrency wallets assume technical competence, and the consequences of mistakes (lost recovery phrases, sent to wrong addresses, approved malicious transactions) are permanent and unforgiving. Rabby offers a more accessible entry point than many alternatives because it simplifies several mechanical steps, explains what is happening before you sign, and warns about suspicious activity. But accessibility does not replace discipline. The difference between a secure setup and a compromised one often depends on a single decision made during the first fifteen minutes.

Introducing a family member to self-custodial cryptocurrency requires more than handing over a wallet and instructions. It requires establishing a clear mental model of what the wallet does, which steps matter most, what can go wrong, and what to do if it does. The process is not technical in the way setting up a brokerage account is technical. It is behavioral: understanding that a recovery phrase is not a password, that the wallet does not talk to a company, and that once a transaction is signed it cannot be reversed. Rabby’s design helps with some of these lessons. The rest depends on how you explain and demonstrate the setup.

Download and installation: Verification as the first step

Begin by going directly to rabby.io in a web browser. Do not click a link from an email, search result, or social media post. Type the address yourself or use a bookmark you have created in advance. This single discipline prevents the most common entry point for wallet theft: a fake website that looks identical to the real one. Once you are on rabby.io, you will see options for browser extension, mobile app, and desktop application. For a non-technical family member, the browser extension is usually the simplest choice because it integrates into daily web browsing and requires no new software installation beyond what the browser already does.

Click the download link for your browser (Chrome, Firefox, Edge, or Brave). You will be taken to the official app store for that browser. Verify that the developer listed is “Rabby” and that the description matches what you see on the rabby.io website. Install the extension and then click the Rabby icon in your browser’s toolbar. A setup screen will appear. This is the moment to establish one critical habit: before doing anything in the wallet, the person should tell you what they are about to do. This transparency makes mistakes visible while they can still be prevented.

The installation process itself is straightforward: no API keys, no account creation, no phone number required. That simplicity is by design. Rabby is a self-custodial wallet, meaning the person holds their own private keys rather than trusting a company to hold them. The trade-off is clear: no customer service will recover a lost recovery phrase, no password reset will help if the phrase is forgotten, and no insurance will cover mistakes. Those consequences are real, but so is the benefit: the wallet provider cannot freeze assets, cannot be hacked to steal funds, and cannot be compelled to surrender private information.

Creating or importing: The recovery phrase decision

Rabby offers two paths at setup: create a new wallet (which generates a new recovery phrase) or import an existing one (if the person already has a recovery phrase from another wallet). For someone beginning with cryptocurrency, creating a new wallet is simpler. Rabby will generate a 12-word recovery phrase—a random sequence that serves as the master backup for the entire wallet. This is the most critical piece of information the person will ever handle. It is not a password. It is not a PIN. It is a private key written in words, and anyone with access to it can control all the funds in the wallet forever.

When Rabby displays the recovery phrase, have the person write it down by hand on paper. Not in their phone notes. Not in a document. Not in their email. Pen and paper, in order, on one page. Many people balk at this: it seems old-fashioned and fragile. But paper has important properties. It does not sync to the cloud, cannot be remotely accessed, and leaves no digital footprint that might be searched or stolen by malware. Once the phrase is written, the person should store it in a physical location they can access but others cannot: a safe deposit box, a home safe, a drawer in a locked cabinet. Tell them to imagine they are keeping the deed to a house. The level of care should be similar.

After the phrase is recorded, Rabby will ask the person to verify it by selecting the correct words in the correct order. This is not a test; it is a confirmation that the phrase was written correctly. If any word is misspelled or out of order, the backup will not work. Have the person do this verification while you watch, referring to the paper they just wrote. If they cannot verify it, ask them to write it again rather than continuing with an incorrect backup.

Setting a password: Local device protection, not ultimate security

Rabby will then ask for a password to unlock the wallet on the device itself. This password is local: it does not go to any server, and Rabby does not store it. Its purpose is to prevent casual access if someone picks up the device. A family member should choose a password they can remember, not one they need to write down. Length matters more than complexity for a password only they will type. Something like “MarchSnowball2024Blue” is better than “X#9@kLp” because it is easier to type consistently and less likely to be forgotten under stress.

Understanding the limits of this password is important. It protects against someone opening the browser and clicking the wallet icon to view the balance or send funds. It does not protect against malware that monitors keystrokes, a stolen device that has already been unlocked by someone else, or a recovery phrase that was written carelessly and left accessible. The password is one layer in a stack of protections, not a substitute for the others. If a family member forgets this password, Rabby can be reinstalled using the recovery phrase, but that is a more complex recovery process than simply resetting a password to an online service.

Recommend that the person write this password down somewhere safe and separate from the recovery phrase—perhaps in a locked drawer, a safe, or with a trusted advisor—so it is not lost. This sounds redundant until someone actually forgets a password. The difference between a recoverable situation (you have the recovery phrase) and a catastrophic one (you have neither) is often just one piece of written information stored securely.

Understanding what Rabby can and cannot do

Once the wallet is set up, the person now has a public address: a string of characters that begins with “0x” and looks like “0x1a2b3c4d5e6f…”. This is their receiving address. Anyone can send cryptocurrency to it. The address itself reveals nothing about the amount in the wallet, the transaction history, or the person’s identity—unless they tell others or unless they later move the funds to a service that requires identification.

Rabby is designed exclusively for EVM-compatible networks (Ethereum, Polygon, Arbitrum, Optimism, Base, and similar chains). It does not support Bitcoin or Solana. This is an important boundary to establish early. If a family member later wants to hold Bitcoin, they will need a different wallet. Rabby’s focus on EVM networks means it can provide sophisticated features for those chains: automatic network switching when visiting different DeFi services, NFT display and management, transaction simulation before signing, and risk alerts for suspicious transactions. These features work together. When the person visits a service like Uniswap or Aave, Rabby detects the network and prepares the appropriate connection. It then shows what the transaction will do—”You will send 1 USDC and receive approximately 0.99 ETH”—before asking for approval. This is not guaranteed safety; it is informed consent.

The wallet also provides security warnings when a transaction looks suspicious. If the person is about to approve a contract permission that seems excessive, Rabby will flag it. If a token being received is unknown or appears to be a scam, Rabby will warn. These alerts are helpful, but they are not foolproof. A person can still approve a bad transaction if they do not read the warning. The design philosophy is to make dangerous actions visible and difficult to do accidentally, not to prevent them entirely. The wallet trusts the person to make the final decision.

First deposit: A small, deliberate test

The next milestone is the first time the person receives funds. Ideally, this should be a small amount from a trusted source—perhaps from their own exchange account, a friend, or you. The purpose is to verify that the address works and that the person can see the funds arrive. Before sending, have the person tell you their receiving address and confirm it visually together. Make sure they read it aloud, character by character if necessary, and that it matches what Rabby displays. This seems excessive for a small test amount, but it establishes the habit. When larger amounts are at stake, the same verification process will be second nature.

After the funds arrive (this can take a few minutes to an hour depending on network congestion), check the balance together. Rabby will display it in the wallet interface. Confirm that the amount matches what was sent and that the transaction appears in the transaction history. This is also the moment to explain that the funds are now in the person’s wallet and under their control. No company holds them. No one can freeze them. But also no one can recover them if they are sent to the wrong address or if the recovery phrase is lost.

This first transaction is a deliberate practice run. If something goes wrong here—the address is wrong, the funds disappear—the financial loss is minimal and the lessons are clear. Once the person is confident with this small amount, larger amounts become less risky psychologically and practically.

Common operations: Sending, receiving, and recognizing traps

Sending funds is straightforward in Rabby. The person clicks “Send,” enters the receiving address, specifies the amount, and confirms. Before clicking the final approval button, Rabby should display what is about to happen. They should verify that the receiving address is correct (a common mistake is pasting a wrong address from the clipboard), that the amount is what they intended, and that the network is correct. Only then should they approve the transaction. Once the transaction is signed, it cannot be reversed or cancelled. If it is sent to the wrong address, the funds may be permanently lost.

Receiving funds is even simpler: the person provides their address to whoever is sending. They can find this address by clicking “Receive” in Rabby. One useful habit is to verify the address shown by Rabby against the address written down when the wallet was created (or visible if they imported a hardware wallet). This sounds paranoid, but it confirms that the address shown in the wallet is the actual wallet address, not a fake one created by malware.

The biggest trap for non-technical family members is approving transactions or token permissions in DeFi applications. When a person visits Uniswap or another decentralized exchange, they may be asked to “approve” the token before trading. This approval is a separate transaction that allows the contract to spend a specific amount of that token on the person’s behalf. Rabby will warn if the approval amount seems excessive (like asking approval to spend billions of dollars), but the person should always check. If they are trading 100 USDC, approving 1 million USDC is unnecessary. Some applications try to do this by default. Reject those approvals and use only as much as needed. This is where the transaction interpretation Rabby provides becomes invaluable: the person can see what the approval means before signing.

Hardware wallets and advanced security for larger amounts

If the person eventually holds a significant amount of cryptocurrency, a hardware wallet (such as Ledger or Trezor) adds another layer of protection. Rabby can integrate with hardware wallets through its connection interface. The setup is more complex than a software-only wallet, but the benefit is substantial: the private keys never touch the computer or phone, so even if the device is completely compromised, the funds cannot be stolen without physical access to the hardware device.

However, hardware wallet integration is not for everyone, and it should not be suggested for a family member just learning the basics. Wait until they are comfortable with the software wallet, understand the recovery process, and are confident enough to handle a slightly more complex setup. At that point, if they hold more than a trivial amount and want to reduce risk, a hardware wallet becomes a reasonable next step. The Rabby NFT wallet features also include support for hardware wallet imports, allowing seamless integration with devices like Ledger or Trezor if the person decides to upgrade their security model later.

For most non-technical family members in the early stages, the combination of a strong password, a securely stored recovery phrase, and careful verification before signing transactions is sufficient. The goal is to build discipline and understanding first. Optimization and additional tools can come later once the person has experience.

Ongoing practices: Backups, updates, and recognizing change

After setup is complete, three ongoing practices matter. First, keep Rabby updated. When a new version is available, install it. Security fixes are regular, and using an outdated version introduces risk. This is particularly true for a browser extension, which should be checked and updated regularly. Second, verify that the recovery phrase backup is secure and accessible. Periodically ask the person whether they still know where their recovery phrase is stored and whether it is still protected. If they are moving to a new location or major life change, this is the time to audit that backup. Third, watch for signs of compromise: unexpected transactions, balance changes that cannot be explained, or requests for verification or password from anyone claiming to be from Rabby. The wallet provider will never ask for a recovery phrase, password, or private key. If someone does, it is always a scam.

The wallet should also be treated as a device-specific application. If the person gets a new phone, they will need to install Rabby again on the new phone and import their recovery phrase. Alternatively, they can export the wallet to a MetaMask wallet or another application and import it there. Rabby supports importing MetaMask wallets, making migration from other self-custodial applications straightforward. The recovery phrase itself remains the single source of truth: as long as it is safe and private, the wallet can be reconstructed anywhere.

The responsibility conversation: Why this matters

Before a family member begins using Rabby, have an explicit conversation about what self-custody means. The person is now responsible for their own security in ways they may never have been before. There is no customer service to call, no password reset, no account recovery specialist. If they lose the recovery phrase, the funds are permanently inaccessible. If they approve a malicious transaction, the funds are gone. If they send cryptocurrency to the wrong address, it may be irretrievable. These are not hypothetical risks; they happen regularly to people who understand cryptocurrency and people who do not.

The purpose of this conversation is not to scare them away but to establish realistic expectations. They should hold only the amount they are comfortable losing entirely. They should treat the recovery phrase like the deed to a house or the title to a car. They should never share it with anyone, including technical support staff, friends, or family members who claim to be helping. If someone asks for it, assume they are trying to steal. And they should verify every address before sending funds, because addresses are long and human eyes are fallible.

This responsibility is real, but it is also manageable. Millions of people use self-custodial wallets without losing funds, not because the wallets are bulletproof but because they follow basic practices. The person using Rabby is joining that group. Clarity about what they are responsible for is the first step toward managing that responsibility well.