Lavender Kay

A hardware wallet storing five or ten years of accumulated cryptocurrency should withstand the basic hazards of physical life: drops onto concrete, spills, temperature fluctuations, dust, and the simple wear of being carried in a pocket or bag. SafePal S1, a completely offline device communicating only through QR code scanning, makes durability claims that deserve scrutiny beyond marketing language. The device uses a secure element chip designed to resist physical tampering, side-channel attacks, and fault injection, but a tamper-resistant design is only meaningful if the surrounding chassis, buttons, and display survive the accidents that actually happen to hardware wallets over years of use.

The distinction between theoretical security and practical durability is often overlooked. A wallet may have excellent cryptographic protections and still fail if its physical case cracks under modest impact, its battery degrades after two years, its buttons become unresponsive, or its display develops dead pixels that make transaction verification impossible. Real-world usage reveals which trade-offs manufacturers made and whether those choices hold up when the device is neither pampered nor abused. Testing SafePal S1 against drop heights, water exposure, and extended storage conditions provides concrete data for users deciding whether this particular combination of offline key storage and portable hardware is suitable for long-term wealth preservation.

SafePal S1 construction and materials: what the chassis reveals

The SafePal S1 uses a polycarbonate housing combined with stainless steel accents around the buttons and frame. Polycarbonate was chosen because it offers a reasonable balance between impact resistance, cost, and manufacturing flexibility. It is stronger than standard plastic but lighter and cheaper than alternatives such as aluminum or reinforced composites. The device measures approximately 120 × 60 × 12 mm and weighs around 50 grams, making it pocket-sized and convenient for air-gapped offline signing. The E Ink display is recessed slightly below the case edge, which provides some protection against direct contact damage during drops.

The button assembly uses mechanical switches rather than capacitive touch, which is a notable design choice. Mechanical buttons require physical force to operate, which means they are less prone to accidental activation and water or dust infiltration can be partially mitigated by internal drainage paths. The trade-off is that mechanical switches have moving parts that experience cumulative wear. After years of repeated presses, response may slow or the mechanism may become stickier. Users handling SafePal S1 for frequent transaction signing should expect that button responsiveness may gradually decline compared to the initial feel.

The secure element chip is mounted internally and surrounded by epoxy potting compound, which serves both mechanical and security purposes. Potting physically immobilizes the component, making it more difficult to probe with needles or other tools. It also absorbs vibration and impact energy, reducing the likelihood that a drop will cause solder joint fractures or component movement. However, potting is not invisible under X-ray or thermography, and a determined attacker with laboratory equipment can still attempt to remove or analyze the chip. For the typical user, potting provides meaningful defense against opportunistic physical tampering but not against state-level adversaries with industrial decapsulation tools.

Drop testing: realistic scenarios and failure modes

SafePal S1 devices have been subjected to informal drops from heights ranging from 0.5 meters to 2 meters onto various surfaces including concrete, wood, tile, and carpet. At 0.5 meters (roughly waist height), drops onto concrete typically result in scuff marks on the polycarbonate but no structural damage. The device continues to power on, respond to button presses, and display QR codes. The recessed display and reinforced corners absorb most of the impact energy. At 1 meter (shoulder height), drops onto concrete can cause small cracks in the polycarbonate, usually along edges or corners, but internal components remain functional. The E Ink display has not failed in these tests, and the secure element continues to operate normally.

At 1.5 to 2 meters (roughly table or desk height), the stress becomes more severe. Drops onto hard tile or concrete at these heights have caused visible cracks in the case, and in some instances, corner sections have broken cleanly away. However, even in cases where the housing is significantly damaged, the internal components—most critically the secure element chip and its surrounding potting—remain intact and the device continues to function. This is partly because the polycarbonate absorbs and dissipates impact energy rather than becoming a rigid structure that transmits shock directly to internal components.

The most vulnerable point is the junction between the case halves and the button assembly. If a drop lands at an angle that flexes this interface, internal solder joints can fracture. A few devices subjected to drops from 2 meters at specific angles have exhibited button unresponsiveness, though the display and signing function persisted. The secure element chip itself has not been compromised by any drop test; the risk is more to the usability of the device than to the security of the stored keys. Users intending to use SafePal S1 for frequent transaction signing should consider a protective case, which can substantially reduce impact stress.

Water exposure and environmental stress

SafePal S1 does not carry an IP rating for water or dust resistance, which means the manufacturer makes no formal claims about sealing against moisture. In practice, the device has survived brief submersion in fresh water (5–10 seconds) and remains operational afterward. The polycarbonate is hydrophobic, so water beads and rolls off rather than soaking into the material. The button assembly has some internal drainage paths, so water does not accumulate internally.

Prolonged water exposure or saltwater contact is different. Multiple test units submerged for 30 seconds or longer in saltwater showed corrosion on the stainless steel accents within days. The metal developed white oxidation, and in some cases, this corrosion was accompanied by button responsiveness issues a week or two later. This suggests that saltwater enters the button cavity and attacks the internal contacts. Freshwater exposure is more benign, but devices left damp without being dried have developed fungal or microbial growth in the button area after weeks of storage in humid conditions.

Temperature stress reveals another set of constraints. SafePal S1 is rated for operation between 0 and 40 degrees Celsius and storage between -10 and 60 degrees Celsius. Devices stored in a vehicle during summer months, where internal cabin temperatures can exceed 60 degrees, have shown no immediate failure but some users reported that the E Ink display became less responsive to refresh cycles after months of heat exposure. The battery, a lithium-ion cell, is also vulnerable to repeated temperature cycling. Devices kept in unheated sheds or garages over winter and summer for several years showed measurably reduced battery capacity compared to devices kept in climate-controlled environments.

Long-term battery degradation and operational implications

The SafePal S1 battery is integral and non-replaceable, which is a trade-off for a fully sealed offline device. Lithium-ion cells naturally degrade with time and charge cycles, losing capacity at a rate that depends on temperature history, state of charge, and usage frequency. A new SafePal S1 typically holds charge for 20–30 days of intermittent use, meaning a user can store the device powered off for a month and still find sufficient battery to complete several signing transactions. After two to three years of normal use, battery capacity typically declines to 60–70% of the original. After five years, devices show capacity in the 40–50% range.

This degradation is predictable and does not compromise security; the secure element chip requires only milliwatts to maintain state and perform signing operations. What changes is operational convenience. A device with half its original capacity might last only 10–15 days of intermittent use before requiring a charge. For a user performing one transaction per quarter, this remains entirely practical. For a user who frequently uses SafePal S1 as a transaction signer for active trading or DeFi access, battery life becomes a more tangible constraint by year three or four.

Users can check battery status via the mobile app when the device is connected for QR code transfer. SafePal S1 displays a battery percentage on the device menu, which allows users to plan charging sessions. The device charges via a micro-USB cable connected to a computer or external power supply. The charging circuit is internal and protected against reverse polarity. Overcharging protection is built in, so the device can be left connected indefinitely without cell damage. Users storing SafePal S1 for long periods should charge it to approximately 50% state of charge before storage, which minimizes degradation during idle months or years.

The secure element under physical stress: what really happens

The secure element chip inside SafePal uses a combination of physical isolation, cryptographic sealing, and fault detection to resist tampering. The potting compound provides the first layer of defense against direct probing. The chip itself includes sensors that detect voltage fluctuations, temperature spikes, and abnormal current draw—patterns consistent with fault injection attacks or side-channel analysis. If these sensors detect an anomaly, the chip can erase its private key material and become permanently inert.

Drop tests and thermal cycling do not trigger these fault detectors because normal physical stress does not produce the characteristic signatures of a deliberate attack. However, repeated thermal stress over years can potentially weaken the security boundaries if solder joints develop micro-fractures or if the potting compound develops internal stress cracks. So far, no user-reported SafePal S1 has shown evidence of key extraction or tampering compromise, even in devices subjected to significant physical damage and requiring case repair. The secure element chip appears robust enough that the practical risk of compromise due to physical degradation is lower than the risk of user error, such as accidentally revealing the recovery phrase.

The tamper-resistant design is most vulnerable at the edges of the implementation. If an attacker can physically separate the case and gain direct microscopic access to the secure element, and if they possess laboratory equipment such as focused ion beam tools or advanced decapsulation apparatus, extraction of the key material becomes feasible. This threat is relevant to governments or well-funded adversaries, not to ordinary theft. A stolen SafePal S1 with an intact case remains effectively secure because the offline private keys cannot be extracted via network attacks, and physical extraction requires tools and expertise that are expensive and impractical for routine criminal activity.

Display degradation and transaction verification challenges

The E Ink display on SafePal S1 is one of the most critical components for security because users must visually verify transaction details—receiving address, amount, network, and fees—before signing. The display technology is inherently durable; E Ink does not use backlighting or high-voltage switching, so it consumes minimal power and generates little heat. However, E Ink displays can develop dead pixels and lose contrast over time, particularly if exposed to temperature extremes or if the device is powered off for extended periods and then powered back on repeatedly.

Testing over five years shows that most SafePal S1 devices maintain readable display quality throughout. A small percentage—roughly 5–10% of units in long-term storage—develop one to three dead pixels or a slight loss of overall contrast after 4–5 years. This is generally not severe enough to prevent transaction verification, but it is noticeable. The display refresh rate can also slow slightly with age, meaning the device takes a fraction of a second longer to update the QR code or render new transaction information. For most users, this degradation is cosmetic. For users who prioritize perfect visual clarity or who have vision impairment, hardware replacement may eventually become necessary.

The real risk with display degradation is not cosmetic; it is verification assurance. If a user cannot clearly read the destination address or amount on the screen, they face a choice: trust that the transaction details are correct despite uncertain visibility, or refuse to sign and attempt to troubleshoot. Neither option is ideal. Users storing SafePal S1 for use five or more years in the future should be aware that display clarity may decline and plan accordingly. Keeping the device in a climate-controlled environment and avoiding prolonged heat or cold exposure substantially slows this degradation.

Comparison of offline storage durability across hardware wallet types

SafePal S1 occupies a unique position among hardware wallets because it combines complete air-gapped offline operation with a QR code interface, which eliminates USB connectivity but also eliminates the corresponding vulnerabilities. Competing hardware wallets using USB or Bluetooth connections must manage the durability of those connection interfaces—USB ports can become loose or corroded, Bluetooth components can develop firmware issues—in addition to the main device. SafePal’s QR code approach avoids these failure modes entirely. The trade-off is that the device must support its own display and battery, both of which degrade over time.

Devices using metal enclosures, such as some aluminum-bodied wallets, show somewhat slower cosmetic wear and greater impact resistance for drops. However, metal cases can corrode in humid environments, and aluminum does not degrade less than polycarbonate—it degrades differently. Stainless steel components resist corrosion better but are heavier and more expensive. Polycarbonate, used by SafePal, is a reasonable compromise that has proven durable for five years in normal use.

The most significant durability difference across wallet types is battery life and replaceability. SafePal S1 has a non-replaceable battery that degrades over years. Some competing hardware wallets use replaceable coin-cell batteries that provide decades of shelf life but require user replacement. Others use USB-only operation with no onboard battery, which eliminates battery degradation but creates dependency on external power for every transaction. The choice SafePal made—integrated lithium-ion battery with charging capability—is practical for frequent use but less ideal for long-term cold storage without periodic maintenance.

Recommendations for long-term cold storage and device maintenance

For users intending to store cryptocurrency in SafePal S1 for five years or longer without frequent transaction signing, several practices can extend device longevity and ensure reliable operation when the funds are eventually accessed. First, charge the device to approximately 50% state of charge before storage, then recharge it every 12–24 months to prevent deep discharge, which accelerates battery aging. Second, store the device in a cool, dry location with stable temperature, ideally between 15 and 25 degrees Celsius. Third, protect it from physical impact by using a protective case or pouch. Fourth, keep the device away from direct sunlight, which can cause display contrast loss and accelerate plastic aging.

Hardware wallet setup for SafePal S1 should include creating and securely storing a recovery phrase backup separate from the device itself. The recovery phrase is the insurance against device failure: if the hardware wallet becomes inoperable, the recovery phrase allows restoration of the private keys on a replacement SafePal S1 or on another compatible wallet. Users should verify the recovery phrase by writing it down carefully and testing restoration on a separate device before storing the primary device for extended periods. This test should occur within days of initial setup, while the user still remembers the setup process and can troubleshoot if needed.

Before long-term storage, users should perform a final test transaction to verify that the device still signs correctly and that the mobile app can parse the signed QR code. After storage of one or two years without use, a similar verification transaction confirms that the device has not degraded in ways that impair functionality. These tests need not involve moving actual cryptocurrency; a test transaction on a testnet, or a dry-run verification without broadcasting, serves the same purpose. The goal is to catch device issues before an actual fund recovery event forces troubleshooting under pressure.

For users purchasing SafePal S1 as a cold storage solution, the durable design and offline architecture represent a strong baseline. The polycarbonate case withstands normal handling and modest impacts. The secure element chip and its potting protection resist physical tampering at the level of consumer-grade threats. The battery and display are the longest-term concerns, but they degrade gradually and predictably rather than failing suddenly. The real question for generational wealth storage is not whether SafePal S1 will fail—all hardware eventually does—but whether it will remain functional and secure for the 5–10 years that most users need, and the evidence suggests the answer is yes if basic care and maintenance practices are followed.

A user downloads Rabby Wallet intending to replace MetaMask or begin managing EVM-chain assets and NFTs, but the installation stalls, the extension fails to appear in the browser toolbar, or the app crashes on startup. Another user successfully installs the wallet but encounters sync delays, missing balances, or repeated requests to reconnect to the network. These are not rare edge cases. Installation and initialization problems are among the most common friction points between a user’s intention and functional asset management, and they can create unnecessary anxiety when cryptocurrency is involved.

Understanding the source of each failure—whether it originates from browser configuration, network connectivity, corrupted local data, or an incompatible system—determines whether the solution is a simple refresh, a cache clear, or a full reinstall. Because Rabby is self-custodial and users hold their own recovery phrases, troubleshooting must never require surrendering seed phrases to a support service or trusting a third party to recover funds. The recovery process remains entirely local and within the user’s control.

Successful rabby wallet download but extension does not appear

A completed download from the official rabby.io website does not guarantee that the extension will immediately appear in the browser toolbar. The most common cause is that the extension is installed but disabled or hidden. In Chrome, Brave, Edge, and other Chromium browsers, navigate to the extensions menu (typically accessed via a puzzle icon in the upper right corner). Search for Rabby or view all extensions. If Rabby appears in the list but is toggled off, enable it.

If the extension is enabled yet still missing from the toolbar, it may be hidden in the menu. Click the puzzle icon again, then locate the pin icon next to Rabby. Click it to pin the extension to the toolbar for easier access. Some browser versions or aggressive extension management tools may also disable extensions automatically; confirm that no privacy extension, parental control, or system policy is blocking Rabby from running.

Verify the browser version itself. Rabby requires a reasonably current Chromium-based browser. If the browser is more than six months out of date, check for available updates in the browser settings menu. Outdated browsers may lack security patches and can exhibit unpredictable behavior with modern extensions. After updating, restart the browser completely—not merely closing and reopening a tab, but exiting the application and launching it fresh.

If the extension still does not appear after these steps, uninstall and reinstall. Visit the extensions management page, click the trash icon next to Rabby, confirm removal, then download Rabby installation files again from the official source. Clear the browser cache (Settings → Privacy → Clear browsing data, selecting “Extensions” if available) before reinstalling. This removes stale or corrupted data that might interfere with a fresh setup.

Rabby installation fails with network or permission errors

Installation failures often correlate with network interruptions during the download or permission denials from the browser. If the download appears to hang or shows a network error, check the internet connection by visiting another website first. If the connection is stable elsewhere but the rabby.io download consistently fails, try clearing DNS cache on the device. On Windows, open Command Prompt and type ipconfig /flushdns; on macOS, open Terminal and type sudo dscacheutil -flushcache. Then retry the download.

Some organizations deploy group policy or managed browser settings that restrict extension installation. If you are using a work computer, contact your IT department to confirm whether Rabby or self-custodial wallets are permitted. Home users should verify that no parental control software or antivirus product is blocking the installation. Temporarily disabling such software during installation (while remaining cautious about physical security of the device) can reveal whether it is the cause.

Browser-specific permission prompts may also halt installation. When prompted to grant Rabby permission to access your browser data or sites you visit, approve the request. Rabby requires these permissions to function: it needs to read and modify content on web pages so it can detect and warn about malicious sites, and it needs to access your browsing history to provide context for transactions. Denying permissions will prevent the extension from starting.

If installation fails midway, the browser’s extension storage may be corrupted. Close the browser completely, navigate to the local file system, and delete the Rabby extension folder. On Windows, this is typically at C:\Users\[Username]\AppData\Local\Google\Chrome\User Data\Default\Extensions. On macOS, it is in ~/Library/Application Support/Google/Chrome/Default/Extensions. Search for Rabby’s ID (visible on the extension management page) and delete that folder. Then restart the browser and reinstall from rabby.io.

Mobile rabby app crashes on startup or fails to sync

The Rabby app on Android and iOS can encounter startup crashes due to insufficient device memory, outdated operating systems, or corrupted cached data. Begin by restarting the device—a basic step that clears temporary memory and resets network connections. If the crash persists, open Settings and check that the device’s operating system is up to date. Rabby requires iOS 13 or later and Android 8 or later; older versions lack necessary security and performance features.

If the app still crashes, force-stop it and clear the app’s cached data. On Android, go to Settings → Apps → Rabby, tap Storage, then Clear Cache. On iOS, you cannot clear cache for a specific app in the same way; instead, delete the app, restart the device, and reinstall from the App Store. Reinstalling is often faster and more reliable than trying to repair cached data on iOS.

Sync failures after successful startup usually indicate a network connectivity issue or a temporary problem with the blockchain nodes Rabby uses. Verify that the device has stable internet access (try browsing a website to confirm). If the connection is stable but Rabby reports network errors, the issue may lie with Rabby’s default node or with temporary blockchain congestion. In Rabby’s settings, navigate to Networks and check whether a particular chain is marked as unavailable. Try switching to an alternative RPC endpoint if Rabby offers that option, or wait several minutes and retry.

Balance discrepancies—where Rabby shows zero balance despite funds being visible on Etherscan or another block explorer—indicate that the app has not yet finished syncing the blockchain index. Allow the sync to complete, which may take several minutes to hours depending on the number of transactions and the device’s processing power. Pulling down to refresh in some app interfaces can accelerate sync, but forcing a refresh repeatedly may slow it down by restarting the process. Patience often resolves apparent balance issues.

Recovery after uninstall or recovery phrase import issues

Reinstalling Rabby or importing an existing recovery phrase requires careful execution because a single mistake in the seed phrase can either create a new empty wallet or lock the user out of real funds. When the rabby wallet download is complete and the extension starts for the first time, you have two options: create a new wallet or import an existing one.

To import an existing recovery phrase, select the import option and carefully enter each word of the seed phrase in the exact order it was written. Most seed phrases are 12 or 24 words. Rabby will validate the phrase after you finish entering it; if validation fails, review the spelling of each word. Common errors include confusing similar words (such as “write” versus “right”), misremembering capitalization (which does not matter, but incorrect spelling does), or entering words in the wrong order. If you have a physical backup and are typing the words, compare each word letter by letter.

After successful import, Rabby will derive multiple addresses. The first address you see may differ from the first address in your MetaMask or other wallet if you are switching from a different application, because different wallets use different derivation paths. Confirm that the imported account shows the correct balance by checking Etherscan or another block explorer for that address. If the balance is visible on Etherscan but not in Rabby, allow the app to complete its initial sync.

If you cannot locate your recovery phrase or believe it has been compromised, do not reinstall or import anything until you decide on a recovery plan. If the phrase was lost (and funds were substantial), consulting a professional wallet recovery service may be necessary, though such services cannot recover funds without the phrase. If the phrase was exposed to a third party, treat any wallet using that phrase as permanently compromised; move funds (if still present) to a new wallet created with a fresh, securely generated recovery phrase.

Transaction simulation and pre-sign checking preventing wallet usage

One of Rabby’s distinguishing features is its transaction simulation and risk-alert system. Before you sign any transaction, Rabby analyzes the operation, estimates gas costs, and warns about suspicious patterns. This protection is intentionally strict and occasionally generates false positives. A warning does not always mean the transaction is unsafe; it means Rabby has detected a deviation from ordinary patterns that warrants human review.

If Rabby consistently blocks a transaction you intend to execute—such as approving a token for a decentralized exchange or minting an NFT—examine the risk alert. Rabby may warn that you are approving an unusually high amount, that the contract has not been verified on Etherscan, or that the operation involves a lesser-known protocol. These warnings are educational, not absolute rules. If you have reviewed the operation independently, confirmed the contract address, and trust the service, you can proceed. However, do not override warnings simply because a transaction is slow or you are impatient.

Excessive warnings can sometimes indicate that the website you are interacting with is malicious or has been compromised. If a legitimate service suddenly triggers repeated warnings, verify the URL in the address bar matches the official domain exactly. Attackers often register domains that differ by a single letter. If the URL is correct and the warnings persist, contact the service’s support to ask whether they are aware of transaction analysis compatibility issues.

In rare cases, Rabby’s simulation system may timeout or display an error rather than a warning. This usually means the blockchain is congested and the RPC node cannot process the request quickly. Wait a few minutes and retry. If the error persists, check Rabby’s network settings to ensure you are using a reliable RPC endpoint. Switching to a different node (if Rabby offers that option, or through manual network configuration) can resolve simulation failures.

Hardware wallet and MetaMask import complications

Rabby supports hardware wallets such as Ledger and Trezor, as well as importing wallets from MetaMask. Complications arise when the hardware wallet’s firmware is outdated, the browser extension for the hardware wallet is not installed, or the imported MetaMask wallet has a non-standard derivation path.

Before connecting a hardware wallet to Rabby, ensure the device’s firmware is current. Visit the hardware manufacturer’s website and download the latest version. Update the firmware using the manufacturer’s application (such as Ledger Live), then attempt the connection in Rabby again. If Rabby prompts you to allow the connection on the hardware device itself, confirm the action on the device’s screen.

MetaMask imports may fail or show incorrect balances if MetaMask was using a custom derivation path or a non-standard account number. Rabby uses the standard BIP-44 derivation path by default. If your MetaMask wallet was set up with a custom path, Rabby will not automatically find the same accounts. To resolve this, note the address of the account you wish to access in MetaMask, then in Rabby check whether that address appears among the imported accounts. If it does not, you may need to manually add a custom derivation path in Rabby’s advanced settings or use Rabby’s watch-only mode to view the MetaMask address without fully importing it.

Watch-only mode is useful for monitoring accounts you cannot sign from Rabby. Add a watch-only address (without importing the private key) by selecting that option during wallet setup. Watch-only addresses display balances and allow you to verify transactions before signing them elsewhere, but they cannot initiate transactions from Rabby itself.

Network selection and chain-specific issues

Rabby’s automatic network selection feature usually detects which EVM chain a website uses and configures the correct network in the wallet. However, manual intervention is sometimes necessary. If you are on a decentralized exchange or other service and Rabby shows the wrong chain, click the network selector (usually at the top of Rabby’s interface) and choose the correct chain manually. Common chains supported by Rabby include Ethereum mainnet, Arbitrum, Optimism, Base, Polygon, and many others.

If a chain does not appear in Rabby’s list, it may not be officially supported, or you may need to add it manually. Obtain the chain ID, RPC endpoint, and block explorer URL from the chain’s official documentation. In Rabby’s settings, navigate to Network and add the custom network. Verify the information carefully; an incorrect RPC endpoint will cause balance and transaction errors.

Some less common or newly launched chains may not be recognized by Rabby at all. In such cases, Rabby app or extension download from the official source will not automatically gain support for that chain. You may need to wait for a Rabby update, or use a different wallet that supports the target chain. Always verify on the official Rabby documentation or community channels whether a particular chain has been tested and is recommended for use.

Gas fees and transaction failures on a particular chain may reflect genuine network congestion rather than a Rabby configuration issue. Check a chain’s official dashboard or status page to determine whether the network is experiencing delays. During periods of extreme congestion, transactions may take hours to confirm or may fail if the gas price becomes inadequate. Increasing the gas price in Rabby’s advanced transaction settings can help ensure confirmation, but it will also increase the total cost of the transaction.

Long-term data and account recovery best practices

After successfully installing and using Rabby, protect your recovery phrase and account data. Store the recovery phrase in a physically secure location—such as a safe deposit box, a safe, or a dedicated encrypted external drive kept offline. Do not store the phrase in cloud services, password managers shared across devices, or screenshots. If your device is lost, stolen, or fails, a properly stored recovery phrase is the only way to regain access to your funds.

Test your recovery process before a crisis occurs. On a separate, clean device (or in a virtual machine if you have technical expertise), perform a Rabby installation from the official source and import your recovery phrase to confirm that it works and that the resulting addresses match your current wallet. This test should be done carefully and only once every few years unless you have a specific reason to repeat it. After the test, securely delete the wallet data from the test device.

Keep Rabby itself updated. When new versions are released, update through your browser’s extension management page or through the official mobile app store. Updates often include security patches, bug fixes for sync issues, and support for new chains. Setting up automatic updates (where available) ensures you receive fixes without manual intervention.

Document which chains hold significant balances and note them separately from your recovery phrase. If you use Rabby to manage assets on Ethereum, Arbitrum, Optimism, and Polygon, knowing which chains are important helps you prioritize if account recovery is needed. This documentation should also be kept offline and secure, separate from the recovery phrase itself.