How can we help?

Open Create account or Sign in. Continue with a passkey to create or return to a NUvault wallet, or connect an existing Ethereum-compatible wallet. Returning users should use the same passkey account or wallet as before.

Signing in also connects your private balances when the service is available. Your wallet may ask you to approve a message proving ownership; this cannot move funds or approve payments. There is no separate balance setup page. Valid access is reused automatically. If you cancel, retry on the same screen or continue without balances; your account stays saved.

No email or identity document is requested to create a NUvault account. Account creation must be enabled on the site, and individual providers may impose their own requirements on enabled services.

No. The sign-in message proves that you control your wallet and starts an account session. A payment needs a separate approval. Check the site address and read every wallet request; reject anything you did not initiate.

Unlock your wallet and allow it to connect to this site. On a phone, try your wallet’s own browser. Check for a pending connection or signature request, then reload NUvault and try once more. Choose the correct wallet account before signing.

WalletConnect and passkey creation have separate availability requirements. If NUvault says a method is unavailable, retrying will not activate it. You never need to import a recovery phrase into NUvault.

Check that your wallet is using the same address as before. A different address identifies a different NUvault account. Your wallet’s on-chain balance is also separate from a NUvault private balance; connecting does not move funds between them.

New receiving addresses can receive more than one deposit into your NUvault balance without sharing your sign-in wallet address. Choose the asset and network, then click Get receiving address.

New address gives you a fresh address when you want one. Addresses created under the old receiving system are kept in history and are not offered for reuse. Public networks and service providers can still hold transaction information.

Choose the asset and network. Share the complete address and any required memo or tag, and check the displayed minimum. Similar-looking assets on different networks are not interchangeable.

Use only the receiving details generated for your signed-in account. Example addresses and dashboard images are not funding instructions.

Check the sending wallet’s transaction status and compare the asset, network, address, memo and amount with the original request. Keep the transaction hash and request reference. Network confirmation does not always mean the private balance has already been credited.

Do not send a second deposit to try to fix the first. Deposits below the minimum, unsupported assets, wrong networks or old receiving routes may need provider investigation and may be unrecoverable. A refund is not guaranteed; follow the request’s status and any confirmed refund instructions.

A .nu payment is intended to move assets between NUvault private accounts. A withdrawal sends to a wallet address on a supported public network. Withdrawals are publicly observable. Neither service is enabled in this preview.

For a name payment, confirm the resolved recipient with the person through a trusted channel. A familiar name is not proof of their identity. For a withdrawal, check the full destination and network before approving.

Choose the asset you hold and the asset and network you want. NUvault requests a route through its connected providers. Review the input, expected output, minimum output, fees and expiry before signing. A listed asset does not mean every route is available.

A quote can expire or become unavailable as prices and liquidity change. Request a fresh quote rather than approving outdated details. Your sign-in wallet balance is not automatically available for a private-balance swap.

Read the review screen for the selected route. Provider, bridge and network costs can differ by asset and network. Minimum received and displayed fee amounts describe that particular quote; do not assume that another route or later quote costs the same.

The wallet or exchange sending an incoming deposit may charge a separate fee. NUvault does not publish a fixed universal fee or promise fee-free transfers. If costs or the minimum received are unclear, do not approve the operation.

Check Activity and keep the operation reference. A request can reach a provider even if the confirmation does not reach your browser. Pending or unknown does not mean that nothing happened.

Do not create or sign a replacement payment until the original outcome is established. Refreshing Activity checks status; it does not require you to sign the payment again. Record any transaction hash and the time of the original attempt for support.

You can decline a wallet request before signing. Once an operation has been submitted or settled, NUvault cannot promise cancellation or reversal. Incorrect destinations, unsupported assets and missing memos can cause permanent loss. Refund timing and eligibility depend on the actual route and provider outcome.

Your .nu name identifies your account inside NUvault. It is not a blockchain domain, an internet domain registration or a guarantee of ownership elsewhere. Name lookup is designed to resolve the NUvault recipient without displaying their sign-in wallet address.

Registering a name does not activate payments or messages. Those services must also be available for you and the recipient.

The name is unavailable. It may already belong to an account or be held in NUvault’s reserved pool. Common first names and a curated selection of valuable and service names are reserved. Try a distinctive variation; adding a name to your private contacts does not register it.

You can choose your initial name and then rename it once during the lifetime of your account. Review the new spelling before confirming. The old name stays reserved and is not released for another person to claim.

Deactivating and reactivating your latest name does not use another rename or reset the allowance. The Profile page shows the remaining allowance. A name change does not move ownership to a different wallet.

Contacts are your private address book. Saving a contact does not create a mutual friendship or send money. A friend request must be accepted before it becomes mutual. Check saved wallet addresses and networks before using them.

Use the available blocking controls to stop supported interactions with another account. Blocking does not reverse a completed payment or remove records already held by the other person. Report impersonation through the published NUvault support contact when available.

Messaging is not available in this preview. When enabled, both accounts need a supported messaging identity and the required consent. A .nu name alone is not proof that a person can receive messages. Never share recovery phrases, private keys or sign-in codes in a chat.

Save an address with its network in Contacts to give it a label. Labels appear when that exact address and network are shown in Send or Activity; they cannot identify an unknown sender. You can add a note of up to 280 characters to an activity entry and search labels and notes on the page you have loaded. Load older history to search earlier entries.

Live account notes are private to your account in NUvault, but are stored on the server and are not end-to-end encrypted. NUvault’s server operators can access them. Do not put passwords, recovery phrases or other secrets in notes. Demo notes stay in this browser, separate from live account notes, and may be lost when browser data is cleared.

Your signup passkey signs you into your NUvault account. There is no separate protection switch or additional passkey setup required to use your created wallet. Sends and swaps still need their own review and approval.

Settings → Wallet backup lets you add an optional backup passkey using another passkey manager or security key. Test signing in with it on another device and confirm you return to the same wallet and profile. A synced copy in the same passkey manager is not an independent backup.

Export wallet opens Privy’s secure window for the wallet’s private key after you acknowledge what the key controls. NUvault does not receive the key. If your wallet already has additional provider verification enabled, Privy may still request it. A backup sign-in passkey does not automatically replace an existing MFA factor.

For a wallet created through NUvault, keep access to your passkey manager and consider an independent backup passkey. Your exported wallet key lets you control that wallet in another compatible wallet app; it does not automatically recover your NUvault profile. Keep a passkey for account access.

For an external wallet, follow its provider’s official backup process. A .nu name, screenshot or NUvault browser session cannot restore a lost wallet. Never send your private key or recovery phrase to NUvault or anyone offering support.

Use your wallet provider’s official recovery process, then sign in with the same restored address. Creating a new wallet does not recover the old NUvault account. Recovery cannot be guaranteed if all wallet keys, passkeys or supported backup methods are lost.

Avoid anyone who asks for an upfront recovery payment or your secret credentials. NUvault cannot recreate missing wallet keys or promise to recover inaccessible funds.

Sign out ends the current NUvault account session. Sign out everywhere revokes the NUvault sessions for that account. Use these controls when leaving a shared device.

Signing out does not undo a signed payment or necessarily revoke a separate wallet or provider session. Review connected sites and permissions in your wallet as well. Clearing cookies alone is not the same as revoking every session.

Stop approving requests. Check the site address, secure your wallet and passkey accounts, and review connected sites using your wallet’s official tools. If you can safely access NUvault, sign out everywhere. Follow the wallet provider’s incident guidance for a compromised key.

Keep references and redacted screenshots for investigation. Never post account cookies, signing payloads, private keys or recovery phrases. No support representative needs those secrets.

Reload the page to get the current app files. If it still fails, try a current browser and check whether an extension is blocking this site. Light/dark mode is a display preference, not a privacy setting.

Your appearance choice is stored in this browser. Private browsing, blocked storage or clearing site data may prevent it from being remembered. Make sure your wallet recovery is safe before clearing site data.

An unavailable feature cannot be activated by repeatedly clicking it. In this preview, financial services are off and examples are not usable funding instructions. Signing in or viewing a feature does not move funds.

If you previously submitted a real operation in an enabled service, check its own Activity status. A later outage does not prove the earlier operation failed, and it does not make a replacement payment safe.

Describe what you were doing, what you expected and the exact error. Include the approximate time, browser/device and the relevant operation or request reference. For a transaction issue, include its public transaction hash, asset and network only through a confirmed support channel.

Redact balances or personal details that are not needed. Do not include recovery phrases, private keys, passkey codes, full signatures, browser cookies or authentication tokens. Check the support section below for the published contact.