Changenow wallets are self-Custody Tools With Network-Matched Addresses

Wrong-Network Transfers Create the Hardest Failure State

A wrong-network transfer records value on a ledger that the selected NOW Wallet asset view does not query, even when the recipient string looks valid.

An Ethereum-style 0x address passes the same structural checks on Ethereum, BNB Smart Chain and Polygon because each network uses the EVM account model. The ledgers remain separate. Sending USDT on BNB Smart Chain does not credit the Ethereum USDT balance, and adding the same address to a different asset view does not move the tokens. Bitcoin is stricter at the syntax layer because legacy, SegWit and Taproot encodings differ. Solana adds another distinction: a wallet public key and an SPL associated token account are related addresses with different roles. Resolving the state begins with the actual chain and transaction record.

One Recovery Phrase Produces Several Address Families

One recovery phrase feeds deterministic key derivation, while each network-specific path and address encoder turns that shared root into the account shown for an asset.

Local Key Material

NOW Wallet binds its private keys to a 12-word recovery phrase and performs transaction signing on the device. A PIN or biometric gate controls local app access, while the phrase recreates the underlying key tree after device replacement.

Deterministic Derivation Paths

BIP44 defines five path levels: purpose, coin type, account, change and address index. Its first external Bitcoin example is m/44'/0'/0'/0/0; an Ethereum-style example uses coin type 60'. Two wallet apps may accept the same words yet show different addresses when their paths, account indexes or script conventions diverge. NOW Wallet’s import flow includes path choices designed for Trust Wallet and Exodus portfolios.

Network-Specific Encoders

The derived public key still needs the target network’s address rules. Ethereum renders a 20-byte account as 40 hexadecimal characters after 0x. EIP-55 adds a mixed-case checksum. Solana represents a 32-byte account address in base58. Bitcoin encodes an output script rather than a general account identifier, so its visible string also signals the spending condition.

How Do EVM Networks Reuse One Address?

EVM networks reuse one address because the same secp256k1 public key maps to the same 20-byte account identifier across compatible execution environments.

The 40 hexadecimal digits therefore stay constant, but a chain ID binds each signed transaction to a particular ledger. Ethereum uses chain ID 1, Optimism uses 10, BNB Smart Chain uses 56 and Polygon PoS uses 137. Base uses 8453, Arbitrum One uses 42161 and Avalanche C-Chain uses 43114. That same account string remains valid syntax on each network. The node connection and selected chain determine which nonce, native balance and token contracts appear. Matching the address without matching the chain ID leaves the transfer on a different ledger.

Bitcoin Address Formats Define the Accepted Script

Bitcoin receiving addresses encode an output script, so NOW Wallet must match the sender’s supported script type rather than present one universal Bitcoin account string.

A mainnet pay-to-public-key-hash address begins with 1, while pay-to-script-hash begins with 3. Native SegWit pay-to-witness-public-key-hash uses witness version 0, a 20-byte program and a bc1q Bech32 address. Taproot uses witness version 1, a 32-byte program and a bc1p Bech32m address. BIP84 places native SegWit accounts under a path such as m/84'/0'/0'/0/0. A sender must support the exact format that the receiving wallet supplies. Converting the text manually changes the script or invalidates its checksum.

Token Standards Stay Bound to Their Native Network

A token standard defines contract behavior on one network; it does not turn identically named assets on other networks into the same balance.

ERC-20 and BEP-20 Contracts

ERC-20 balances live inside a contract mapping on an EVM chain. The receiving input therefore consists of a chain ID, token contract and account address. BEP-20 follows the EVM model on BNB Smart Chain, but its ledger and contracts remain separate from Ethereum. NOW Wallet needs the correct contract in the selected network catalog before it can label the balance accurately.

SPL Associated Token Accounts

Solana’s original Token Program and Token-2022 store balances in token accounts for a particular mint. An associated token account is deterministically derived from the owner address, token program and mint. A wallet interface may let the user share one owner address while preparing the required token account behind the screen. Native SOL follows the System Program path instead of an SPL mint.

TRC-20 Contract Routes

TRC-20 tokens execute through contracts on TRON and use a TRON receiving address. A ticker such as USDT therefore needs the TRON network label and its TRC-20 contract context, not an Ethereum ERC-20 route. NOW Wallet displays the token under the ledger where its contract state exists. TRX supplies that network’s resources and fee balance.

Destination Tags and Memos Complete the Route

Some receiving routes need an address plus an auxiliary identifier, and omitting that second field leaves the on-chain payment without the recipient’s internal routing context.

XRP Ledger Destination Tags

The next part of this is set out in Guide to changenow. An XRP Ledger classic address starts with r, while a destination tag occupies an unsigned 32-bit field from 0 through 4,294,967,295. Shared receiving accounts use that tag to assign one payment to the intended internal record. An X-address packs a classic address and tag into one encoded value. The protocol itself stores the classic destination and tag as separate transaction fields.

Stellar Transaction Memos

Stellar supports four memo forms. A text memo holds up to 28 bytes, and an ID memo is an unsigned 64-bit integer. Hash and return-hash memos hold 32 bytes. A personal Stellar account does not inherently need a memo, but a receiving platform may require one for internal allocation. The destination instructions decide whether the address alone completes the route.

Native Fee Assets Govern Outbound Transfers

An outbound transfer uses the native fee asset of the ledger being signed, regardless of the token ticker displayed in the receiving field.

Ethereum and its EVM rollups Base, Optimism and Arbitrum One charge fees in ETH; 1 ETH equals 10 ¹⁸ wei. BNB Smart Chain uses BNB, Polygon PoS uses POL and Avalanche C-Chain uses AVAX. Bitcoin divides 1 BTC into 100,000,000 satoshis. Solana divides 1 SOL into 1,000,000,000 lamports. XRP Ledger records 1 XRP as 1,000,000 drops. TRON records 1 TRX as 1,000,000 sun. The live fee changes with network demand, transaction size or computational work, but the required asset and base-unit conversion stay fixed.

Seven Wallet Recovery Models Compared

Wallet choice changes recovery portability and key isolation more than address appearance, because similar receiving screens may rely on different seed formats or hardware boundaries.

NOW Wallet, MetaMask, Trust Wallet, Exodus and Phantom document 12-word recovery material for their software-wallet flows. Electrum generates a versioned Bitcoin seed rather than a BIP39 seed. Trezor Safe 3 places signing keys in hardware and supports both BIP39 and SLIP39 backups. These differences matter during migration because a compatible phrase format still needs the expected derivation path and account discovery behavior.

The same ground is broken down in Changenow why troubleshooting matters in detail. The table describes recovery design, not guaranteed cross-import parity. A wallet must recognize the source seed format, derivation paths and address types before it can reproduce every account. Hardware isolation also changes the signing boundary. Trezor confirms operations on the device, while the listed software wallets sign through locally protected key material.

Recovery Restores Keys Before It Restores Context

Restoring a phrase recreates deterministic keys, yet the visible accounts still depend on the derivation path, address index, network catalog and imported-key history.

A 12-word BIP39 mnemonic encodes 128 bits of entropy plus a 4-bit checksum from a 2,048-word list. BIP39 then applies 2,048 PBKDF2-HMAC-SHA512 iterations to produce a 512-bit seed. Those constants define the seed. BIP32, BIP44 and network-specific schemes define the child keys and address forms. A separate BIP39 passphrase creates a different valid seed, so recovery needs the same passphrase when one was originally used.

NOW Wallet creates a 12-word portfolio backup and accepts 12- or 24-word phrases in supported import flows. Choosing the path associated with Trust Wallet or Exodus helps reproduce their account layout. A private key imported separately in any wallet needs its own backup because it is not derived from the active portfolio phrase. Recovery succeeds when the phrase format, optional passphrase, derivation path and address index all agree.

Can One Test Transfer Validate the Entire Route?

One test transfer validates only the exact network, asset contract, recipient fields and fee path used for that transaction at that moment.

A successful ETH transfer to an EVM address proves control of that address on the selected chain; it says nothing about a similarly named token contract on another chain. Likewise, an XRP payment without a required destination tag does not test the platform’s internal allocation route. A native SOL transfer does not exercise an SPL token account. The test becomes meaningful when its chain, contract or mint, memo or tag and receiving address match the planned transfer. Recheck the displayed destination when a platform creates a fresh deposit instruction or changes the supported network.

Network Matching Rewards Repeated Multi-Chain Use

Network-matched address discipline delivers its greatest value to people who repeatedly move the same ticker among exchanges, self-custody portfolios and several live chains.

Changenow wallets become easier to manage when each transfer begins with its route. Select the asset and network in NOW Wallet, copy the address that appears for that pairing and carry over any required memo or destination tag. On the sending side, choose the identical network label before reviewing the final transaction. Keep enough of that chain’s native asset for later outbound fees and retain the recovery phrase together with the source wallet and derivation-path context.

This method suits regular USDT transfers across Ethereum, BNB Smart Chain and TRON as well as users managing BTC, SOL, XRP or XLM beside EVM assets. It also makes wallet migration clearer because the recovery record describes more than twelve words. The decisive record is a compact mapping of asset, network, address format, auxiliary field and recovery path; update it whenever a new portfolio or chain joins the workflow.