A user holding assets across MetaMask, Phantom, or other self-custody wallets faces a practical decision: whether to consolidate into a single application or maintain several separate wallets. The operational case for consolidation is straightforward—fewer recovery phrases to protect, one interface for portfolio management, and integrated access to DeFi, NFT trading, and token swaps. But the migration itself introduces specific risks. Moving cryptocurrency requires precision in identifying which assets exist on which blockchains, understanding the distinction between import and transfer, and ensuring that the receiving wallet is correctly configured before funds arrive.

The okx wallet extension / okx wallet download / okx wallet provides one path for this consolidation, available across browser, desktop, and mobile platforms with support for over 30 blockchains. Unlike hosted services, OKX Wallet grants users direct control through a secret recovery phrase rather than storing assets on OKX’s servers. That custody model means the migration process is a movement of assets themselves, not a transfer of account access. Understanding what actually happens during that movement, what should happen, and where the common mistakes occur is essential before pressing send on any significant balance.

Understanding the difference between import, recovery, and transfer

The OKX Wallet Extension supports three distinct operations that are often confused with each other. The first is recovery from a secret recovery phrase, which reconstructs wallet addresses and balances from a known seed. If you have an existing 12 or 24-word recovery phrase from another wallet, OKX Wallet can re-derive your addresses using that same phrase. This operation does not move cryptocurrency—it simply displays the same wallet on a different application. Your original wallet remains valid, and both applications show identical addresses and balances.

The second operation is importing a private key directly into OKX Wallet, which adds a specific address to your wallet without using the recovery phrase as the master seed. This is useful if you want to manage a single address from an old wallet while maintaining your primary OKX Wallet recovery phrase. A private key import creates no on-chain record and no transaction; it simply extends which addresses your OKX Wallet can access and sign for.

The third operation is transfer, which is an actual blockchain transaction. It moves funds from one address to another, creating a transaction record, incurring gas fees, and leaving a permanent record on the ledger. Many users arrive at OKX Wallet because they want a single consolidated portfolio, which typically means using recovery or import for addresses they already control, then transferring funds from other addresses they don’t directly control, or consolidating dust from multiple addresses within their own wallet structure.

The reason this distinction matters is that recovery and import have no cost, no delay, and no risk of loss—they simply add addresses to OKX Wallet. A transfer is irreversible and requires fees. If you recover your MetaMask phrase into OKX Wallet and then send funds from MetaMask to the new OKX address, you have completed a transfer. If instead you recover the same phrase and see the funds already present, you have simply accessed the same wallet through a new interface. The operational outcome is identical, but the mental model matters for understanding what is actually happening.

Step-by-step recovery of an existing wallet into OKX Wallet Extension

To import an existing wallet using its recovery phrase, start by opening OKX Wallet Extension in your browser and selecting the option to import or restore a wallet. Write down the exact 12 or 24-word recovery phrase from your original wallet application—do not type it directly from your screen if possible, and do not copy it into any online tool or untrusted application. Have the phrase written on paper or visible only to yourself in a private context.

In OKX Wallet Extension, select the import option and enter the recovery phrase word by word. The application will display each word that matches as you type, which can catch spelling errors immediately. Some wallet phrases use BIP39 standard words; others use proprietary lists. OKX Wallet supports the standard BIP39 list, which is compatible with MetaMask, Phantom, Ledger, Trezor, and most other popular wallets. If your original wallet uses a non-standard phrase, recovery may not work, and you will need to use private key import or transfer instead.

Once you have entered the complete phrase, OKX Wallet will derive the addresses and display your existing balances. The derived addresses should match exactly what you see in your original wallet. If they do not match, stop immediately and verify that you have entered the phrase correctly. A single character error in the recovery phrase will produce a completely different set of addresses with zero balance, not a partial failure or warning message.

After confirming the addresses match, set a password for OKX Wallet Extension if you have not already done so. This password protects your access to the application but does not encrypt your recovery phrase storage—the application stores the phrase securely on your device, not in a cloud service or browser extension storage that could be synced across devices. If you use OKX Wallet on multiple devices, you should either recover the same phrase on each device or use hardware wallet integration for higher-value accounts.

Importing individual private keys when recovery phrase migration is not possible

Some wallets use non-standard recovery phrases or you may want to add a single address from another wallet without committing to full recovery. In these cases, private key import is the appropriate method. Private keys are typically displayed as a hexadecimal string or as a QR code in the original wallet’s security settings. The import process in OKX Wallet Extension allows you to add the private key, which then appears as one address among possibly many in your wallet structure.

The critical security practice is to never export a private key online, through email, into a cloud storage service, or into any application other than OKX Wallet itself. If your original wallet is on a mobile phone, use a screenshot or manual note-taking in a secure context, then enter it into OKX Wallet Extension on your computer. If the original wallet is on a hardware device, export it directly to a password manager or secure note that will not persist in your browser history or system clipboard.

OKX Wallet Extension will display the imported address and its current balance immediately. Unlike recovery, which derives multiple addresses from a single phrase, each private key import adds one address at a time. If you have multiple addresses in the original wallet, you will need to repeat the import process for each one. For a user with a significant number of addresses, this can become tedious, which is one reason full recovery via the secret recovery phrase is preferred when possible.

The security difference between private key import and recovery is worth understanding. When you recover a phrase, OKX Wallet stores the phrase securely and uses it to re-derive addresses on demand. When you import a private key, OKX Wallet stores that single key. If your OKX Wallet Extension is compromised by malware or a malicious browser extension, both the recovered phrase and imported keys are at equal risk. The distinction is mainly for organization and ease of backup—a recovered phrase is one secret that regenerates all addresses, while imported keys must be backed up individually.

Transferring funds between wallets: execution and confirmation

After you have recovered your existing wallet or confirmed that your addresses are now visible in OKX Wallet Extension, you may still choose to transfer funds to consolidate them into a single address or to truly migrate to OKX’s infrastructure. This is an on-chain transaction and requires network fees, which vary based on blockchain congestion and gas price.

Before initiating any transfer, confirm four specific details. First, identify which blockchain the asset is on. Ethereum tokens, for example, exist only on Ethereum and its L2 networks like Polygon and Arbitrum. A token called USDC exists on Ethereum, but sending Ethereum-based USDC to a Solana address will result in loss of funds—the asset will not appear on Solana, and recovery is not possible. The receiving address must be compatible with the blockchain you are using. MetaMask and OKX Wallet both support Ethereum addresses (starting with 0x) on multiple chains, so a funds transfer within this ecosystem should work if both are on the same chain, but Phantom uses Solana addresses, which are fundamentally different and cannot receive Ethereum tokens.

Second, verify the receiving address character by character. Copy and paste it from OKX Wallet Extension to your sending wallet, or use a QR code if the interface provides one. Do not type the address manually. Typos in blockchain addresses are catastrophic—a single character error will send funds to an unknown address, and there is no recovery mechanism. Some wallets display a checksum or warning for invalid addresses, but some accept malformed input without comment.

Third, start with a small test amount. If you are moving a significant balance, send 0.01 of the asset or a token worth $10–50 first, confirm that it arrives in OKX Wallet Extension at the correct address, and wait for several block confirmations before transferring the remainder. This approach costs slightly more in total fees but eliminates the risk of discovering a configuration error after all funds are sent.

Fourth, understand the gas cost and timing before submitting. OKX Wallet Extension displays estimated fees for each transaction and allows you to adjust the gas price if you want to pay more for faster confirmation or less for slower confirmation. On Ethereum mainnet, this can range from $1–50 depending on network load. On Polygon or Arbitrum, fees are typically under $1. On Solana, fees are fractional. The exchange rate between the asset you are sending and the network’s native token (ETH for Ethereum, SOL for Solana, etc.) can significantly affect the effective cost of the transfer.

Managing multiple blockchains within OKX Wallet Extension

One of the primary advantages of OKX Wallet Extension is support for over 30 blockchains, meaning your consolidated wallet can hold Ethereum, Solana, Polygon, Arbitrum, Bitcoin, and other assets without switching applications. However, this multi-chain capability creates the most common source of user error during import and transfer.

When you recover a recovery phrase from another wallet, OKX Wallet Extension derives addresses on all supported blockchains simultaneously. This means a single 12-word phrase generates an Ethereum address, a Solana address, a Bitcoin address, a Polygon address, and many others—all valid and all showing zero balance unless you previously sent funds to them. Your original wallet may have only used the Ethereum address, but OKX Wallet shows all of them, which can be confusing.

The blockchain selection interface in OKX Wallet Extension should make this clear, but the practical lesson is that you must always specify which blockchain you are sending to and receiving from. If you see an Ethereum address in your OKX Wallet and you are sending USDC from MetaMask, confirm that MetaMask is also connected to Ethereum (not Polygon or another chain). Browser extension wallets typically display the current network prominently at the top, and it is worth checking before every transaction.

For users consolidating multiple blockchain holdings, the Crypto Multi-Sender feature available in OKX Wallet can streamline bulk transfers. If you have dust amounts (small token balances that are not worth individual gas fees) across multiple addresses, Multi-Sender allows you to send from several addresses to a single consolidated address in one transaction, potentially saving on gas costs compared to sending each separately. This is particularly useful when migrating from multiple old wallets to a single OKX Wallet instance.

Security during and after migration

The migration process itself creates a temporary period where your funds exist in multiple places and multiple applications have access to the same secret recovery phrase. During this window, the security of your recovery phrase is critical. Do not photograph it, store it in a digital file, or enter it into any application other than OKX Wallet Extension and your original wallet. If you are migrating because you suspect your original wallet was compromised, do not recover the phrase into OKX Wallet—instead, import individual private keys only for addresses you want to save, and transfer funds to a newly generated OKX Wallet address that is derived from a new recovery phrase.

After recovery or import is complete and you have confirmed that OKX Wallet Extension shows the correct addresses and balances, you have a decision point. If you keep the original wallet installed and active, both applications will continue to work with the same addresses. This is fine from a technical standpoint but increases the number of applications that could be compromised. A more secure approach is to verify that you have a written backup of your recovery phrase in a secure location, then uninstall the original wallet from your browser or device.

OKX Wallet Extension offers security settings including biometric authentication for transaction approval, automatic lockout timers after inactivity, and recommendations for hardware wallet integration. For larger balances, hardware wallet support through compatible devices like Ledger or Trezor provides an additional layer of protection by keeping private keys offline and requiring physical confirmation of transactions.

The backup of your OKX Wallet recovery phrase is the security-critical step that many users rush. Write it down on paper, not in a digital file, and store it in a location that is both physically secure and accessible if you need it. Do not store it with other identity documents or valuables in a way that suggests it is important. A small note folded in an envelope inside a book on your shelf is more secure than a document on your computer or a note in your phone.

Common mistakes and how to avoid them

The most frequent error during wallet import is entering the recovery phrase incorrectly and not realizing it until after funds have been transferred. The derived addresses will be valid but wrong—OKX Wallet will show zero balances, and the funds sent to those addresses will not appear. To prevent this, verify that the addresses in OKX Wallet Extension match exactly those in your original wallet before transferring anything.

The second common mistake is transferring funds to the wrong blockchain. A user who has Ethereum-based USDC in MetaMask may create a Solana address in OKX Wallet, then send USDC to that address. Solana blockchain will receive a transaction but will reject or ignore it because USDC (Ethereum version) does not exist on Solana. The funds will not appear, and recovery is not possible. This is prevented by always confirming the blockchain in both the sending and receiving wallets before approving a transaction.

The third mistake is reusing the same recovery phrase across multiple devices without proper protection. If you recover your OKX Wallet Extension on a desktop computer and then also on a mobile phone, you have the same secret phrase on two devices. If either device is compromised, the entire wallet is at risk. A better practice is to recover on one device and use hardware wallet integration or private key import on secondary devices, limiting the number of places where your complete recovery phrase is stored.

A fourth error is not testing the receiving address before sending significant funds. Always send a small amount first, confirm it arrives, and verify the address and blockchain are correct. This costs slightly more in total fees but is negligible compared to the cost of sending to the wrong address.

Ongoing wallet management after successful import

Once your assets are successfully in OKX Wallet Extension, you have a consolidated portfolio across multiple blockchains with access to additional features such as real-time price alerts, gas tracking, DeFi staking, NFT trading and import, and spot and futures trading. The Web3 integration allows OKX Wallet to connect to decentralized applications, much like MetaMask or Phantom, meaning you can use the same addresses across DeFi protocols, marketplaces, and other blockchain services.

The consolidation does introduce concentration risk: all assets now depend on the security of one recovery phrase and one application. Monitor OKX Wallet extension updates to ensure you have the latest version, which includes security patches. Keep your recovery phrase in a secure location where you can access it if you need to recover your wallet on a new device or application, but do not expose it unnecessarily.

For ongoing management, make regular backups of any new addresses you add via private key import, and document which addresses are on which blockchains if you have a complex portfolio. OKX Wallet’s portfolio management interface provides a unified view, but understanding the underlying blockchain structure remains important for troubleshooting and for understanding transaction fees and confirmation times across different networks.

A user installs Rabby Wallet as a browser extension, connects their Ledger device via USB, and encounters a blank device list or a persistent “connection failed” message. They try unplugging and reconnecting, restarting the browser, and toggling various settings—but the hardware wallet still does not appear. This is a common friction point: Rabby Wallet is a self-custodial cryptocurrency and NFT wallet designed for Ethereum and EVM-compatible networks, and it explicitly supports hardware wallet integration with Ledger and Trezor, yet the practical connection often fails silently or with vague error text.

The root causes are rarely cryptographic. They almost always involve browser permissions, USB access, WebHID protocol support, device firmware versions, or incorrect connection sequencing. Understanding the distinction between these layers—and working through them in the correct order—resolves most failures without requiring a support ticket or a wallet replacement. The issue is not that Rabby’s hardware integration is broken. It is that the setup involves multiple components that must align, and misalignment at any point produces the same symptom.

How Rabby Wallet communicates with hardware devices

Rabby Wallet does not directly control USB hardware. Instead, it relies on the browser’s WebHID (Human Interface Device) API, which acts as an intermediary. When a user clicks “Connect Hardware Wallet” in Rabby, the wallet sends a request to the browser asking for permission to access USB devices matching specific vendor and product IDs—Ledger’s 0x2c97 for Ledger Nano S/X, and similar identifiers for Trezor models. The browser then presents a permission dialog listing attached devices. The user must explicitly approve the connection before Rabby can read data from or send commands to the device.

This permission model exists for security. Without it, any malicious website could probe for hardware wallets, read balances, or attempt to initiate transactions without the user’s consent. However, it also means that several prerequisites must be met. The browser must support WebHID (Chrome, Brave, Edge do; Firefox does not), the device must be properly recognized by the operating system, USB communication must not be blocked by driver issues, and the device firmware must be recent enough to respond to WebHID requests correctly.

Trezor and Ledger both sign transactions inside the device—the browser and Rabby Wallet cannot access the private key. The hardware device receives a transaction object, displays it on its screen for user review, and returns a signature. Rabby then broadcasts the signed transaction to the blockchain. This isolation is the entire reason to use a hardware wallet, yet it also means that any disruption in the communication channel breaks the workflow. A timeout, a protocol mismatch, or a permission denial produces the same “cannot connect” message from the user’s perspective.

Browser compatibility and WebHID support

Not all browsers expose the WebHID API, and not all versions of supported browsers have it enabled by default. Chrome and Chromium-based browsers (Brave, Microsoft Edge, Opera) support WebHID from approximately version 89 onward. Firefox does not implement WebHID and relies instead on a proprietary extension or a bridge application. Safari has no WebHID support as of the current public versions. This is the first point of failure: if a user tries to use Rabby Wallet with a hardware wallet in Firefox or Safari, the connection simply cannot happen.

Checking browser compatibility is straightforward. Open the browser console (F12 or Ctrl+Shift+K), paste the command `console.log(navigator.hid)`, and press Enter. If the output is `undefined`, the browser does not support WebHID. If it returns an object, the API is available. Some operating systems (particularly Linux) may require additional steps. Windows users should have no special WebHID prerequisites beyond the base browser version, while macOS and Linux users may need to check whether the browser has permission to access USB devices in the system settings.

A user experiencing persistent connection failures should verify their browser version first. This eliminates an entire category of issues without touching the wallet, the device, or the USB cable. If Rabby Wallet as a browser extension is being used, the browser version determines hardware wallet capability regardless of what other software or drivers are installed.

Device recognition and operating system drivers

Before WebHID can do anything, the operating system must recognize the Ledger or Trezor device as a USB device. Windows requires Ledger Live or the Ledger device driver to have been installed at least once. macOS and Linux may require libusb or similar packages. On Windows, opening Device Manager and looking for “Ledger Nano” or similar under “USB Devices” confirms that the operating system recognizes the hardware. If the device appears as “Unknown Device” or with a warning symbol, the driver is either missing or corrupted.

For Trezor, Windows should recognize the device as “TREZOR” without additional drivers (Trezor uses standard USB HID protocol). macOS requires no special setup. Linux users may need to install udev rules to grant non-root access, but the process is documented in Trezor’s setup guide. The crucial step is always the same: plug the device in, open the operating system device manager or equivalent, and verify that the device is listed with a recognizable name rather than a generic error.

If the operating system does not recognize the device, Rabby Wallet cannot connect regardless of version, browser, or configuration. The solution is to uninstall any existing drivers, restart the computer, and reinstall the manufacturer’s software or drivers from the official source. This is not a Rabby-specific problem, but it is the most common reason that hardware wallet connection fails before Rabby even gets a chance.

USB cable, port, and hardware device troubleshooting

A surprising number of hardware wallet connection failures are caused by USB cable problems. Damage to the connector, internal wire breakage, or simple incompatibility with the port can prevent communication. Swapping the cable for a known-good one (ideally one that works with other USB devices) is a quick test. Likewise, trying a different USB port on the computer can isolate port-specific issues, particularly on laptops where one port may be damaged or have contact problems.

The device itself may also have a problem. If the Ledger or Trezor does not respond to any connection attempt, does not power on, or shows only a blank screen, the issue is hardware-level and requires contacting the manufacturer’s support or exploring warranty replacement. However, if the device works with other applications (such as Ledger Live, Trezor Suite, or the manufacturer’s CLI tool), the problem is specifically with the Rabby Wallet integration or the communication protocol between Rabby and the device.

Testing with the manufacturer’s official application is a diagnostic step often skipped. If Ledger Live or Trezor Suite can see and use the device, the hardware and operating system are working correctly. The failure is then narrowed to Rabby Wallet configuration, browser permissions, or a protocol-level issue specific to how Rabby implements hardware wallet support. This saves hours of debugging and points directly to the relevant layer.

WebHID permission and the Rabby permission dialog

When a user clicks “Connect Hardware Wallet” in Rabby Wallet for the first time, the browser displays a USB device selection dialog. This is the critical moment. The dialog should list the Ledger or Trezor device by name. If the list is empty, the device is either not plugged in, not recognized by the operating system, or the browser does not support WebHID (revisit the browser compatibility section above). If the device is listed but selecting it produces an error, the permission may have been denied at the OS level or the WebHID handshake is failing.

Granting permission once should persist for future connections. However, some users report that the permission dialog reappears every time, or that Rabby “forgets” the approved device. This usually indicates that the browser’s site data or cookies have been cleared, or that Rabby Wallet’s stored permissions have been reset. Clearing the browser cache or resetting extensions can inadvertently revoke hardware wallet permissions. The solution is to verify that the site containing Rabby (or the Rabby extension itself if installed locally) is not being cleared from the browser’s privacy settings on exit.

For users on macOS, an additional check is required: System Preferences > Security & Privacy > USB Restricted Mode. If the Mac has been locked for an extended period, USB access may be restricted. Unlocking the Mac and attempting the connection again often resolves the issue. This is an OS-level security feature, not a Rabby Wallet setting, but it is frequently overlooked during troubleshooting.

Ledger device-specific configuration and firmware

Ledger Nano S, Nano S Plus, and Nano X devices require the Ethereum application to be installed on the device itself. This is separate from the device firmware. If the Ethereum app is missing, outdated, or malfunctioning, Rabby Wallet will not be able to retrieve account information or sign transactions. Opening Ledger Live and navigating to the Apps section allows the user to install or update the Ethereum app. After installation, the Ethereum app must be explicitly opened on the device (by navigating to it and pressing both buttons simultaneously) before Rabby can communicate with it.

The Ledger device firmware should also be up to date. Ledger regularly releases firmware updates that fix bugs, improve compatibility, and patch security issues. An outdated firmware may not respond correctly to WebHID requests. Updating is done through Ledger Live: the application detects available updates and prompts the user to install them. The process takes a few minutes and requires the device to remain connected and unlocked.

After updating either the firmware or the Ethereum app, disconnect the Ledger device, close Ledger Live, close the browser entirely, and restart the computer. This ensures that all old connections are dropped and the operating system re-enumerates the USB device. Then reconnect the device, open the browser, and attempt to connect Rabby Wallet again. Many intermittent “connection failed” errors resolve after this restart sequence.

Trezor connection and bridge application requirements

Trezor devices can connect to Rabby Wallet either directly via WebHID (supported in modern browsers) or through the Trezor Bridge application, a small daemon that runs in the background on the user’s computer. The direct WebHID connection is preferred if the browser supports it, as it eliminates an extra layer of software. However, some users find that Trezor Bridge is more reliable, particularly on Linux or when experiencing intermittent WebHID timeouts.

If using Trezor Bridge, the application must be running before attempting to connect Rabby Wallet. The user can verify this by checking the system tray or running processes. If Bridge is not running, Trezor Wallet will not see the device. Restarting the Bridge application (by closing and reopening it) often resolves connection timeouts. Users who frequently switch between Ledger, Trezor, and other wallets sometimes accidentally leave an old Bridge instance running, which can conflict with WebHID detection. Closing all Bridge instances and ensuring WebHID is enabled resolves this contention.

For Trezor users on Linux, the udev rules must be installed correctly. These are system-level permissions that grant user-space applications (like the browser or Trezor Bridge) access to USB Trezor devices without requiring root privileges. If udev rules are not installed or are incorrect, the browser or Bridge may not see the device even if the operating system recognizes it. Trezor’s GitHub repository contains the udev rules; installing them requires a brief terminal command and a system restart.

Practical step-by-step debugging sequence

When hardware wallet connection fails, following a structured troubleshooting order saves time and avoids circular debugging. First, verify that the device is physically plugged in and powered on. Second, check the browser version and WebHID support using the console test. Third, confirm that the operating system recognizes the device in Device Manager or equivalent. Fourth, test the device with the manufacturer’s official application (Ledger Live or Trezor Suite) to confirm hardware and drivers are working. Fifth, restart the computer entirely. Sixth, open a fresh browser instance and attempt to connect Rabby Wallet.

Only after completing these steps should attention turn to Rabby Wallet configuration. At that point, verify that the Ethereum app is open on Ledger devices, that Trezor Bridge is running if being used, and that the browser permissions dialog correctly lists the device. If these are all in order and the connection still fails, check the browser console for specific error messages. WebHID errors often include cryptic details that can guide further investigation or provide useful information for support requests.

For users who installed Rabby Wallet as a browser extension, downloading the official version from the browser’s extension store (Chrome Web Store, Edge Add-ons) is important. Sideloaded or unofficial versions may have outdated code or missing functionality. The official rabby wallet extension / rabby wallet download / rabby wallet is maintained by the development team and receives regular updates to improve hardware wallet compatibility and fix reported issues.

When to escalate beyond self-troubleshooting

If the device works with the manufacturer’s application but not with Rabby Wallet, if the browser supports WebHID but the device is not listed in the permission dialog, or if error messages reference specific protocol failures, the issue is beyond the scope of basic troubleshooting. At this point, gathering detailed information for a support request is more efficient than continued guessing. Information should include the browser name and version, the hardware device model and firmware version, the operating system, the exact error message or behavior, and confirmation that the device works with other applications.

Opening an issue on the Rabby Wallet GitHub repository (since Rabby is open-source) or contacting the Ledger or Trezor support team (if the issue appears hardware-specific) can provide access to developers who understand the integration layer. Including the browser console output and any WebHID-related error messages accelerates diagnosis. Many users find that what appeared to be a Rabby Wallet bug was actually a browser cache issue, an outdated device firmware, or an overlooked permissions setting—information that only emerges through structured troubleshooting with support.

The key insight is that hardware wallet integration in Rabby Wallet depends on multiple independent systems working in concert: the browser, the WebHID API, the operating system, USB drivers, device firmware, and Rabby’s application code. A failure in any one produces the same user-visible symptom. By testing each layer independently and in a logical order, users can identify the exact point of failure and address it directly rather than reinstalling the wallet or replacing the hardware unnecessarily.

This is a sample post created to test the basic formatting features of the WordPress CMS.

Subheading Level 2

You can use bold text, italic text, and combine both styles.

• Bullet list item #1
• Item with bold emphasis
• And a link: official WordPress site

1. Step one
2. Step two
3. Step three

This content is only for demonstration purposes. Feel free to edit or delete it.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit Non Existing amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.