- Your node is associated with your Web3 account.
- Web3 authorization is required for rewards and reputation distribution across the network.
- Your node’s Reputation is tied to your Web3 account.
- You remain in full control over your node/wallet at all times. To move your node to another OS or device, simply authorize in the Fortytwo App of your choice on that device with your Web3 account.
- You can use your wallet outside the Fortytwo network and control it with Web3 wallet apps, for example Phantom or MetaMask .
How does Node Identification Work?
For the network to identify your node, have it as an active participant and provide you with rewards, you need to authorize first. We use Web3 accounts for authorization. This way, your node gets its unique ID by which is recognized by the network, it has its own reputation and can acquire rewards while remaining entirely under your control no matter what application or device you are using in the moment. This way, we treat one node as one Web3 account.- You can create a new wallet for your node directly within the Fortytwo App and CLI. You will have full ownership over this wallet, so make sure to save its credentials to retain access to it. This is a major difference from Web 2 accounts, as we will not be able to recover your access should you lose your credentials.
- Any existing EVM Web3 wallet is compatible with the Fortytwo network. You can authorize in the Inference or Relay Nodes with an existing account by using your private key or Secret Recovery Phrase.
- A node can be migrated between devices and applications using its unique Web3 wallet address credentials.
For example, one Web3 wallet can be simultaneously used on two different machines within different Fortytwo applications (Fortytwo CLI and Fortytwo App). However, only one instance of your node will be able to participate in the network. See this section of FAQ for details.
The Node and Web3 Account Dependency
- You can run an unlimited number of nodes as long as it is one node/wallet per one device.
- Each different node requires a unique Web3 wallet to avoid ID collisions.
- You can install the same node (sign in with the same Web3 account) on multiple devices but can only run one instance of that node at any time. If running several nodes simultaneously under one account, only one node will perform at a time and it can lead to unexpected errors.
- As an exception, you can run both Inference and Relay Nodes on the same machine as long as each node uses a unique wallet ID and unique ports.
What is a Web3 Account?
A Web3 account is a unique identifier that works using blockchain technology, allowing for function and control in a decentralized manner. Since your node account is fundamentally a Web3 account, you need to know its 3 major identifiers:- Public Address
- Secret Recovery Phrase
- Private Key
Your node’s public address is primarily used for transactions, monitoring via blockchain explorers, determining leaderboard placements.
Fortytwo network requires it to:
- Send rewards for participation.
- Acknowledge your node’s participation history, reputation, and balance and determine a node’s reliability.
- It is safe to share: it functions similarly to bank credentials if anybody wants to send a transaction your way. However, keep in mind that anybody can see the entire history of transactions and earnings related to this wallet.
- Nobody can get access to your wallet with just your public address.
- Nobody can tie your wallet’s public address to your identity until you acknowledge the ownership publicly. This way, your privacy depends on your own actions.
Creating New Web3 Account for a Node
You can create a new EVM compatible wallet in any web3 wallet application that supports Etherium networks, for example Phantom or MetaMask , or conveniently create a new Web3 wallet directly in the Fortytwo CLI or Fortytwo App.When creating a new Web3 wallet outside of Fortytwo applications, note that only the first account in that wallet will be used at this time.
Creating a New Account in Fortytwo Inference Applications
Fortytwo CLI
Fortytwo App
1
When starting Fortytwo CLI for the first time, you are prompted to either:
- Create a new identity with an activation code,
or - Recover an existing identity with a recovery phrase.
2
While Fortytwo is in devnet phase, you will be prompted to enter your activation code to begin your participation. To get one, submit an application to get a chance to join the first wave of node operators: Application Form
3
Your new account is now created.The following information about your identity is provided in the
YOUR NEW IDENTITY CREATED box within the terminal window:- Public address of your node → Manually copy and store it to track your node’s perfomance on Dashboard or other explorers. You can also use it to refill your node’s balance. You can find it in the logs any time you restart your node.
- Your Secret Recovery Phrase → Write it down and keep it secure, as it is used to recover your identity.
- Location of your private key on your computer → Go to the defined location and copy the key file to a secure offline device. Do not delete it from this folder as it is required for Fortytwo CLI to function properly.
4
Never share your Secret Recovery Phrase or private key with anyone.
Finding Your Node’s Public Address
If you want to monitor your node’s perfomance on the Dashboard or other explorers, or simply want to provide somebody with your node’s credentials so that they can send assets your way, you need to know your node’s public address.- Fortytwo CLI
- Fortytwo App
1
Go through the standard CLI launch procedure, pick your desired model and launch your node.
2
After the Fortytwo logotype appears, look for the following block of information:Your wallet address is defined in the
Operator Wallet Address: line and begins with 0x.Exporting Your Node ID, Your Web3 Credentials
If you want to move your node to another device, transfer your node identity between Fortytwo CLI and Fortytwo App, or want to access your account through third-party Web3 wallets, you will need either your Secret Recovery Phrase or your private key.- Secret Recovery Phrase
- Private Key
Your node’s Secret Recovery Phrase can never be exported or extracted out of the node applications because Fortytwo never stores is anywhere for security reasons.If you have lost it but still have access to your node’s private key, then it we recommended you create another account, write down the Secret Recovery Phrase, save your new private key, and transfer your funds to that account.
It is best to have secure access to both Secret Recovery Phrase and private key as this way you have more methods to restore access to your assets.
If you have lost both the Secret Recovery Phrase and the private key your account can never be restored.
Migrating Your Wallet or Signing In with an Existing Web3 Account
Migrating your account between devices or between Fortytwo CLI and Fortytwo App follows the same procedure as signing in with an already existing Web3 account. For that you’ll need your wallet’s Secret Recovery Phrase or your account’s private key. If you are installing a new instance of the Fortytwo node and want to migrate your existing account to retain access to your previous identity and rewards, first you need to either already have access to your Secret Recovery Phrase or your private key since you saved them when creating a new account, or you need to export your credentials first.- Fortytwo CLI
- Fortytwo App
Authorization options:
- Secret Recovery Phrase
- Private Key
1
When starting Fortytwo CLI for the first time, you are prompted to either:
- Create a new identity with an activation code,
or - Recover an existing identity with a recovery phrase.
1
You are now prompted to enter your Secret Recovery Phrase.Type it separating each word with a single space and press Enter.
Currently, the account Fortytwo CLI/Fortytwo App imports when signing in with the Secret Recovery Phrase is the account which is the first by order in the wallet. So, though technically one wallet can have several accounts on it, only the first account is used at all times. Due to this limitation, each unique node requires a unique Web3 wallet.
1
If done correctly, CLI should recognize and restore your existing account.
Your new node will now use the same account as before. No reactivation or new wallet generation is required.
Important Security Takeaways
- Do not share or expose your private key file. It grants full access to your account.
- Do not share or expose your Secret Recovery Phrase. It grants full access to your entire wallet.
- Never rely on having access to the private key alone. Always have your Secret Recovery Phrase secured or both.
- If you are operating nodes on multiple devices, each node must use a separate Web3 account.