Account Access

Use this guide to create account access, migrate a license-key account, or recover the correct login path. A successful result is an authenticated Proxima session with at least one linked method you can use again.

Before you start

Prepare the item required by your path:

• the existing license key for a legacy account;
• a valid referral code for a new account;
• access to the email inbox, passkey provider, or wallet previously linked to an existing account.

Never share a license key, private key, seed phrase, passkey prompt, backup code, or one-time verification code with support.

Choose the correct path

Starting point	Path
Account still uses a license key	Migrate the license key once, then link a login method.
Account was already migrated	Sign in with a method previously linked to that account.
No existing account	Create an account with the fields shown, then link a login method.

Existing license-key accounts

If your account still uses a license key, select Migrate my License Key on the login screen. Enter the full key in License key, select Link and continue, then link one of the login methods offered by Proxima. This migration is performed once; future sessions use the linked method.

If the account was already migrated, continue below IF ALREADY MIGRATED and select Continue with Email, Continue with Passkey, or Continue with a Wallet, using the method linked previously.

Verify the migration

Sign out only after confirming that the linked method can identify the intended account. Future sessions use the linked login method rather than the license-key migration form.

Create a new account

The current sign-up form asks for a username and a valid referral code. A referral link may prefill the code; otherwise enter it manually. After validation, choose an available login method.

Use the fields and eligibility rules shown in the current sign-up flow. Access requirements can change without changing an existing account.

Choose a login method

Email verification code

Select Continue with Email, enter your email address, request a verification code, and enter the code on the next screen. Keep access to that mailbox and secure it with its own recovery method.

Passkey

Select Continue with Passkey, then use Log in with Passkey for an existing credential or Create a Passkey to register one. The browser or operating system opens its native passkey prompt.

Passkey availability and synchronization depend on the device, browser, and credential provider. Register a second supported access method before relying on a single device.

Wallet

Select Continue with a Wallet, choose a supported wallet provider and network, connect the intended address, and sign the authentication message. The login signature confirms control of the address; it is not an on-chain transaction and should not move funds.

Always read the wallet prompt before signing. Reject any request that does not match the Proxima login flow you initiated.

The authentication signature confirms control of the selected address. It is not an on-chain transaction and should not request a transfer or approval.

Expected result

After authentication, Proxima should open the intended account. In Settings > Connections, confirm that the login method you just linked appears before relying on it for a future session.

Secure the account

• Keep at least two usable access or recovery methods when the account settings allow it.
• Enable the security controls offered in Settings, including two-factor authentication or backup codes where available.
• Store backup codes offline and never paste them into support chats.
• Review connected sessions and revoke devices you no longer recognize or use.
• Use a dedicated, secured browser profile for operational accounts.

If access or verification fails

1. Try the login method previously linked to the account.
2. Check the email, passkey provider, wallet network, and selected address.
3. If another active session is available, add or repair an access method from Settings.
4. Contact the official Proxima support channel without sharing a private key, seed phrase, backup code, or one-time verification code.

Do not create another account merely because one login method fails. First confirm whether the original account was migrated and which method was linked to it.

What cannot be undone from this page

Signing in does not move on-chain assets. However, losing every linked access method or exposing a secret can prevent safe account recovery. Add a second supported method and configure 2FA and backup codes while you still have an active session.