Claiming your ERC1404 tokens as xx coin on MainNet

The team recommends that unless onboarding a node, you wait at least 72 hours after MainNet Launch to claim your tokens, in order to ensure the network is operating smoothly.

Once you are ready to claim your tokens, please use this guide:

https://xxnetwork.wiki/index.php/Claiming_Tokens

And you can use this wallet generator:

https://xx.network.dev/MainNet-wallet-gen

WARNING: Do not stake, bond, or lock all of your coins, you can get yourself into a position where you cannot pay

Updating the xx network to protect against DDoS attacks (and an urgent xx network MainNet update)

Claiming your ERC1404 tokens as xx coin on MainNet

xx network does not distribute, offer, solicit sales of, or sell any xx coins in any state or jurisdiction in which such a distribution, offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Click here for our full Privacy and Cookie policy.

Strictly Necessary

Always Enabled

Performance

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Cookie	Duration	Description
_ga	2 years	The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gat_UA-130126130-8	1 minute	A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
_gid	1 day	Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
CONSENT	2 years	YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.

Functional

Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.

Cookie	Duration	Description
__cf_bm	30 minutes	This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
__hssc	30 minutes	HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
__hssrc	session	This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.
__hstc	1 year 24 days	This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
aka_debug	session	Vimeo sets this cookie which is essential for the website to play video functionality.
guest_id	2 years	This cookie is set by Twitter to identify and track the website visitor.
guest_id_ads	2 years	This cookie is set by Twitter to identify and track the website visitor.
guest_id_marketing	2 years	This cookie is set by Twitter to identify and track the website visitor.
hubspotutk	1 year 24 days	HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.
mbox	2 years	This cookie is for marketing on developer.twitter.com
muc_ads	2 years	Twitter sets this cookie for tracking and targeting purposes.
personalization_id	2 years	Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting.
player	1 year	Vimeo uses this cookie to save the user's preferences when playing embedded videos from Vimeo.
sync_active	never	This cookie is set by Vimeo and contains data on the visitor's video-content preferences, so that the website remembers parameters such as preferred volume or video quality.
vuid	2 years	Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.

Claiming your ERC1404 tokens as xx coin on MainNet

Popular

Project Updates

Fixing Vesting Schedules

Project Updates

Updating the xx network to protect against DDoS attacks (and an urgent xx network MainNet update)

Project Updates

Claiming your ERC1404 tokens as xx coin on MainNet

Subscribe to our newsletter