On December 7, 2023, at 12 noon, there has been a rush to buy XAI node authorization (in the form of NFT). So far, the market response has been incredible. The continuous buying is really exaggerated. If you still plan to purchase a node license, please use capital 'BA' when entering the discount code so that you can enjoy a 5% discount.
In the previous article Understand and run Xai nodes to earn XAI tokens, we explained in detail how to run Xai nodes. So in this article, we will talk about how to let wallet B run nodes for multiple wallet A based on the whitelist mechanism introduced in version 1.0.34.
Let me remind you again: when purchasing the Xai node authorization KEY, the wallet you use is called wallet A. It is important to protect the private key of this wallet and never disclose it to others. In Xai's node system, the role of wallet A is to authorize another Operator wallet (that is, wallet B) to operate. Wallet B pays for all GAS consumption in the mining process and automatically receives the coins obtained from mining. In short, wallet A is responsible for authorization and currency collection, while wallet B is used for daily node operations. If you still have questions about this process, I recommend you read the article provided above for a more detailed explanation.
The logic principle of multiple wallet "A" authorizing wallet B:
In the early days of the Xai node ecosystem, the operating process was relatively simple. The user first uses wallet A to purchase the node authorization KEY, and then authorizes it to another wallet, wallet B, to run the node according to the tutorial. The process is usually very smooth. Initially, community members generally believed that wallet A and wallet B had a one-to-one relationship, and everyone was familiar with this concept.
However, as the community develops, not all community members can guarantee that their nodes can be online 24 hours a day. In addition, some members' lack of computer knowledge may also cause nodes to not operate smoothly, thus affecting mining profits. In order to solve these problems, we further refined the original concept.
In fact, the relationship between wallet A and wallet B is many-to-one. This means that multiple wallets A (such as A1, A2, A3) with node authorization can be authorized to a single wallet B at the same time. In other words, Wallet B can run nodes for multiple authorized wallets (A1, A2, A3) at the same time. This many-to-one configuration increases flexibility, as shown below:
How does wallet "A" authorize wallet B directly?
Our normal authorization interface is as follows:
The address in the red box is: https://sentry.xai.games/#/assign-wallet/0xc9FF78F63d9Ba9DfC07e292E17B0d98936e4F0C7
Therefore, 0xc9FF78F63d9Ba9DfC07e292E17B0d98936e4F0C7 is the address of wallet B.
Therefore, Zhang San, Xiao Ming, and Lao Wang only need to enter this URL in the browser, and then replace the "0xc9FF78F63d9Ba9DfC07e292E17B0d98936e4F0C7" part with the wallet B address they want to authorize!
Will it be affected if my wallet "A" authorizes multiple wallets B?
There is no problem if wallet A authorizes multiple wallets B (such as B1, B2, B3, etc.). This means that once authorization is completed, these wallet B can all run nodes at the same time. During this process, if a certain wallet B successfully mines a block, then this wallet B will pay the corresponding GAS fee. Specifically, if wallet B1 mines the block, the GAS fee will be paid by wallet B1; if wallet B2 mines the block, then wallet B2 will pay the GAS fee; if wallet B3 mines the block, the same applies to wallet B3. This arrangement ensures that wallet B of each running node bears the cost according to its own operating results.
Why are you saying such a good thing now?
Waiting for program optimization:
In the Xai node ecosystem before version 1.0.34, there was a key problem: Wallet B could not set a whitelist for multiple authorized wallets (such as A1, A2, A3). This means that even if reliable users like Zhang San, Xiao Ming and Lao Wang operate according to the rules, some unruly users, such as Zhao Gao, can also use Wallet B to run their nodes without paying anything for it. cost.
Specifically, in the above example, Zhao Gao not only failed to pay the GAS fees required to run the node to Wallet B, but also allowed 10 other people to use the same method to manipulate the system. This led to a problem where Wallet B was forced to provide resources to Zhao Gao and 10 other people without receiving corresponding GAS compensation, which was regarded in the community as "free prostitution" of Wallet B's GAS.
The issue was resolved after I reported it to the relevant team. In the repaired version, wallet B can now whitelist authorized wallets (such as A1, A2, A3), thus preventing unauthorized users from abusing resources. This improvement not only improves the security and efficiency of the system, but also ensures that the interests of legitimate users are not violated.
For details, please refer to: Xai sentinel node setting whitelist after version 1.0.34
Afraid of wrangling:
In Xai's node system, the design of wallet A and wallet B is theoretically very safe. Wallet A is used to purchase and hold node authorization KEY, while wallet B is used for actual node operation. This design aims to separate critical financial operations (handled by wallet A) and daily node maintenance tasks (performed by wallet B), thereby improving the security of the entire system.
However, a significant problem is that many users lack a full understanding of Web3 security and the importance of public and private keys. This may lead some users to leak the private key of their wallet A without fully understanding these concepts. To make matters worse, some users may have unknowingly disclosed their private keys and then mistakenly suspected that authorizing someone else's wallet B caused a security breach.
Such misunderstandings and inaccurate dissemination of information can easily lead to rumors and panic (FUD, short for Fear, Uncertainty, Doubt). Therefore, publishing a complete tutorial at the beginning may not be the best option, as this may lead to users operating their wallets incorrectly without fully understanding the steps and security measures, thus posing security risks.
To avoid this, more education and training is needed in the community so that users fully understand the importance of Web3 security and how to properly manage and protect their public and private keys. Doing so will not only improve the overall security of your system, but also reduce misunderstandings and unnecessary panic.
What do I do for the community?
I noticed that some users in the community only have a small number of node authorizations (less than 3), and they feel very anxious because of the low probability of KEY exploding (about 7 times in 30 days). To help alleviate their anxiety and make my community contribution, I purchased a server. I offered to help users who were willing to authorize me with wallet B run their nodes. My goal is to help them operate stably and reduce their anxiety.
During this process, I would like to emphasize a few points:
GAS fee: Everyone should know that a KEY requires approximately 0.02 ETH in gas fee per year. This is the operating cost, and everyone must be prepared.
My help is temporary: I run nodes for everyone, but this is just a transitional solution. After all, maintaining the server is very troublesome. I recommend that you run the node yourself because you need to check whether the server is running normally every day.
Safety and understanding are important: please make sure you fully understand the system. The most important thing is, never provide the private key of your own wallet A. If a dispute arises due to misunderstanding, it means good intentions lead to bad things.
By doing this, I hope to alleviate everyone's anxiety while also making a positive contribution to our community. As a member of the community, it is very important for us to help each other.
What is the future outlook for node ecology?
I believe everyone has discovered that with such a structure, modern dimensions will definitely appear in the future, so that I can retreat to the mountains and forests. I wish the node ecology will flourish! I wish you all good fortune!
