Authentication overview

icy.tools provides an analytics platform for NFT traders, offering real-time data, portfolio tracking, and rarity checking for various NFT collections. As of 2026, user authentication for icy.tools is designed for web-based access to its graphical user interface (GUI) and does not currently feature a public-facing API for programmatic data access. This means authentication focuses on securing user sessions within the browser environment rather than authenticating API requests. Users typically authenticate to access features such as detailed collection analysis, real-time market feeds, and personalized wallet tracking for NFT assets. The platform supports common web authentication patterns to ensure both convenience and security for its user base.

The primary goal of icy.tools's authentication system is to verify user identity before granting access to premium features and personalized data. This process ensures that only authorized individuals can view their specific portfolios and utilize features restricted to paid tiers like HODLER or PRO. Authentication also protects user settings and preferences, maintaining a consistent experience across sessions. The system is designed to be straightforward, reflecting common practices in web application security.

Supported authentication methods

icy.tools supports two primary authentication methods for accessing its web platform:

  1. MetaMask Wallet Connect: This method leverages the user's existing Ethereum wallet, specifically MetaMask, for authentication. It's a common approach in the Web3 ecosystem, allowing users to connect their wallet to the application without creating a separate username and password. The platform requests a signature from the connected wallet to prove ownership, which acts as the authentication token. This method is particularly relevant for NFT traders who already manage their digital assets through MetaMask and prefer a decentralized identity approach. For more information on how MetaMask handles key management, refer to the Web Cryptography API used in browser extensions.
  2. Email and Password: For users who prefer a traditional login approach or do not wish to connect a crypto wallet, icy.tools offers authentication via a registered email address and a self-selected password. This method follows standard web security practices, where passwords are typically hashed and stored securely on the platform's servers. Users create an account directly on the icy.tools website, providing an email and setting a password. This classic method provides account access independent of a blockchain wallet and is familiar to a broad user base.

The choice between these methods depends on user preference and existing infrastructure. Wallet Connect is often preferred by those deeply embedded in the Web3 space, while email/password caters to a broader audience familiar with traditional web services. Both methods are designed to secure access to the platform's features, though they operate using different underlying mechanisms for identity verification.

Authentication Methods Comparison

Method When to Use Security Level Key Considerations
MetaMask Wallet Connect Accessing with an existing Ethereum wallet, preference for decentralized identity. High (reliant on wallet security) Requires MetaMask browser extension or mobile app. No traditional password to manage.
Email and Password Traditional web login, no existing crypto wallet, or preference for separate credentials. Moderate-High (reliant on password strength and platform's storage security) Requires robust password practices. Centralized credential management.

Getting your credentials

The process for obtaining credentials depends on the chosen authentication method:

  1. For MetaMask Wallet Connect:
    • Ensure you have the MetaMask browser extension installed and configured with an Ethereum wallet. Instructions for installing and setting up MetaMask are available on the official MetaMask website.
    • Navigate to the icy.tools homepage or login page.
    • Click the "Connect Wallet" or "Login with MetaMask" option.
    • MetaMask will prompt you to select an account to connect and then to sign a message. This signature verifies your wallet's ownership without exposing your private key. Upon successful signature, you will be authenticated.
  2. For Email and Password:
    • If you don't have an account, navigate to the icy.tools registration page.
    • Provide a valid email address and create a strong, unique password. Follow any password strength requirements specified on the site.
    • Complete the registration process, which may include email verification.
    • Once registered, return to the icy.tools login page and enter your registered email and password to access your account. If you forget your password, use the "Forgot Password" link on the login page to initiate an email-based reset process.

It is important to manage these credentials securely, regardless of the method chosen. For MetaMask, this means securing your wallet's seed phrase and private keys. For email/password, it means using strong, unique passwords and potentially a password manager.

Authenticated request example

As icy.tools does not offer a public API, there are no programmatic API requests to authenticate. All authentication occurs within the web browser session when a user logs into the icy.tools platform through its graphical user interface. Once authenticated, the browser session maintains the user's logged-in state, typically using session cookies or local storage tokens, to authorize subsequent requests to the platform's backend services for data retrieval and feature access. This is a standard pattern for web applications where the user interacts directly with a front-end interface.

For instance, after a successful MetaMask connection or email/password login, the icy.tools web application will send requests to its backend servers to fetch real-time NFT data or display a user's tracked portfolio. These requests implicitly carry the session token or cookie established during the initial authentication, allowing the backend to verify the user's authorized access. Developers interested in the underlying mechanisms of session management in web applications can refer to comprehensive guides on HTTP Authentication and Session Management.

// This is a conceptual example of a browser-based fetch operation
// after a user has successfully authenticated via MetaMask or email/password,
// where the browser automatically includes necessary session cookies/tokens.

fetch('https://icy.tools/api/v1/user/portfolio-data', {
  method: 'GET',
  headers: {
    'Content-Type': 'application/json',
    // No explicit 'Authorization' header is typically set by the client-side JavaScript
    // for session-based authentication; browser handles cookies or local storage tokens.
  },
  // credentials: 'include' is often implied or default for same-origin requests
  // when dealing with cookies.
})
.then(response => {
  if (!response.ok) {
    throw new Error(`HTTP error! status: ${response.status}`);
  }
  return response.json();
})
.then(data => {
  console.log('User portfolio data:', data);
})
.catch(error => {
  console.error('Error fetching portfolio data:', error);
});

The above code snippet illustrates a hypothetical client-side request. In a real-world scenario, the browser would automatically manage the session credentials (like cookies or tokens stored in local storage) after a successful user login, making explicit header manipulation for authorization unnecessary from the front-end JavaScript perspective for internal API calls.

Security best practices

Maintaining the security of your icy.tools account is crucial to protect your NFT-related data and potentially your digital assets. Here are key security best practices:

  • Use Strong, Unique Passwords: If using email/password authentication, create a complex password that combines uppercase and lowercase letters, numbers, and special characters. Avoid reusing passwords across different services. A password manager can assist in generating and storing these securely.
  • Secure Your MetaMask Wallet: If using MetaMask, ensure your seed phrase (recovery phrase) is stored offline in a secure location and never shared. Protect your private keys and use a strong password for your MetaMask wallet itself. Be cautious of phishing attempts that try to trick you into revealing your seed phrase or private keys.
  • Be Wary of Phishing Attempts: Always verify the URL to ensure you are on the legitimate icy.tools website (icy.tools). Phishing scams often use similar-looking domains to trick users into entering their credentials on malicious sites. Legitimate sites generally use HTTPS to secure connections, indicated by a padlock icon in your browser's address bar.
  • Review Wallet Permissions: When connecting your MetaMask wallet to any dApp, including icy.tools, carefully review the permissions requested by the application. Only approve necessary permissions. Disconnect your wallet from sites you are no longer actively using.
  • Keep Your Browser and Extensions Updated: Ensure your web browser and any extensions (like MetaMask) are always updated to their latest versions. Updates often include critical security patches that protect against known vulnerabilities.
  • Monitor Account Activity: Regularly review your icy.tools account for any unusual activity. While the platform primarily offers analytical tools, vigilance helps detect unauthorized access early.
  • Understand Session Management: Be aware that once authenticated, your browser maintains a session. Log out of icy.tools, especially on shared or public computers, to prevent unauthorized access to your account by others. Clearing browser data can also help terminate sessions.
  • Consider Hardware Wallets: For increased security of your digital assets, especially if you hold significant value in NFTs, consider using a hardware wallet in conjunction with MetaMask. Hardware wallets provide an additional layer of security by requiring physical confirmation for transactions and interactions.

By implementing these practices, users can significantly enhance the security posture of their icy.tools account and their broader Web3 interactions.