Developers Forum for XinFin XDC Network: 11ppm

Repeated Error When Setting Up XDC Node

11ppm — Tue, 14 Jan 2025 11:11:52 +0000

I am attempting to set up an XDC node on a server that was hard reset, but I keep encountering the following error repeatedly. Despite trying various solutions, the issue remains unresolved. I have tested this on two servers, and the result was the same. Additionally, it seems that others are experiencing the same error. I would like the XDC team to look into this issue.

ERROR[01-14|03:10:09] Failed to retrieve block author          err="recovery failed"                                                                number=0 hash=4a9d74…42d6b1
ERROR[01-14|03:10:24] Failed to retrieve block author          err="recovery failed"                                                                number=0 hash=4a9d74…42d6b1
WARN [01-14|03:10:44] Full stats report failed                 err="ping timed out"
WARN [01-14|03:10:44] Failed to retrieve stats server message  err="read tcp 172.18.0.2:39586->45.82.64.150:3000: use of closed network connection"
WARN [01-14|03:10:54] Stats server unreachable                 err="dial tcp 45.82.64.150:3000: i/o timeout"
WARN [01-14|03:11:10] Stats server unreachable                 err="read tcp 172.18.0.2:34086->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:11:30] Stats server unreachable                 err="read tcp 172.18.0.2:37066->45.82.64.150:3000: i/o timeout"
ERROR[01-14|03:11:49] Failed to retrieve block author          err="recovery failed"                                                                number=0 hash=4a9d74…42d6b1
WARN [01-14|03:12:09] Full stats report failed                 err="ping timed out"
WARN [01-14|03:12:09] Failed to retrieve stats server message  err="read tcp 172.18.0.2:36694->45.82.64.150:3000: use of closed network connection"
WARN [01-14|03:12:19] Stats server unreachable                 err="read tcp 172.18.0.2:43042->45.82.64.150:3000: i/o timeout"
ERROR[01-14|03:12:41] Failed to retrieve block author          err="recovery failed"                                                                number=0 hash=4a9d74…42d6b1
WARN [01-14|03:13:01] Full stats report failed                 err="ping timed out"
WARN [01-14|03:13:01] Failed to retrieve stats server message  err="read tcp 172.18.0.2:58750->45.82.64.150:3000: use of closed network connection"
WARN [01-14|03:13:11] Stats server unreachable                 err="read tcp 172.18.0.2:35534->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:13:31] Stats server unreachable                 err="read tcp 172.18.0.2:35760->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:13:51] Stats server unreachable                 err="read tcp 172.18.0.2:52106->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:14:11] Stats server unreachable                 err="read tcp 172.18.0.2:53050->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:14:31] Stats server unreachable                 err="read tcp 172.18.0.2:58428->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:14:51] Stats server unreachable                 err="read tcp 172.18.0.2:54984->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:15:11] Stats server unreachable                 err="read tcp 172.18.0.2:36082->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:15:31] Stats server unreachable                 err="dial tcp 45.82.64.150:3000: i/o timeout"
WARN [01-14|03:15:50] Stats server unreachable                 err="read tcp 172.18.0.2:38446->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:16:10] Stats server unreachable                 err="read tcp 172.18.0.2:49742->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:16:27] Stats server unreachable                 err="read tcp 172.18.0.2:39772->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:16:47] Stats server unreachable                 err="read tcp 172.18.0.2:57710->45.82.64.150:3000: i/o timeout"
WARN [01-14|03:17:07] Stats server unreachable                 err="read tcp 172.18.0.2:38510->45.82.64.150:3000: i/o timeout"

Proposal: Enhancing the Validator Node Rotation System in the XDC Network

11ppm — Fri, 27 Dec 2024 12:22:00 +0000

Introduction

Currently, XDC masternodes are promoted to validator nodes using a round-robin system. This system ensures fairness while assigning validator roles to standby nodes. However, the existing approach has a potential drawback: certain nodes may remain as validators for extended periods, which raises concerns about decentralization.

This proposal aims to address this issue by presenting a refined mechanism to promote decentralization, while balancing fairness and efficiency.

Proposal Details

1. Periodic Rotation of Validator Nodes

Objective:

Prevent any single node from operating as a validator for extended periods and enable more operators to participate.

Details:

Set a maximum tenure of 1 year for validator nodes.
After the tenure ends, the node returns to the standby pool.
Introduce a 3-year cooldown period, during which the node cannot serve as a validator again.

2. Improved Selection Mechanism: Combination of Registration Order and VRF

Objective:

Balance fairness and unpredictability while prioritizing nodes with stable performance.

Details:

Split the selection process into two components:

Registration Order RotationAllocate 50% of slots based on the order in which standby nodes were registered.
Performance-Based VRF SelectionUse Verifiable Random Function (VRF) provided by the decentralized oracle Plugin to randomly select the remaining 50% from nodes with stable performance.

Benefits:

Maintains fairness based on registration order.
Introduces unpredictability via VRF, enhancing security and decentralization.

3. Transparent Performance Evaluation Criteria for Standby Nodes

Objective:

Ensure a transparent selection process and maintain network reliability.

Details:

Establish criteria such as uptime, response times, and historical performance for evaluating nodes.
Nodes failing to meet these performance standards will be excluded from selection.

Benefits of the Proposal

Promoting DecentralizationReduces the risk of network dominance by specific nodes over extended periods.
Improved FairnessCombines registration order and VRF to create a balanced and inclusive selection system.
Enhanced Efficiency and StabilityPerformance-based criteria ensure network-wide reliability.
Encouraging New ParticipantsCooldown periods create more opportunities for new nodes to serve as validators.

Conclusion

This proposal provides a practical and effective approach to improving decentralization and fairness in the XDC network. By enhancing the round-robin system with registration order rotation and performance-based VRF, it ensures the stability and security of the network while enabling broader participation.

Implementing this mechanism will help the XDC network evolve into a more decentralized and sustainable ecosystem, driving its long-term growth and success.

This is merely one proposal, but it represents a realistic and meaningful approach to enhancing decentralization, fairness, and efficiency within the XDC network. By incorporating detailed implementation plans, this proposal can become even more feasible and effective.

This proposal is intended to serve as a starting point for discussion and thought within the community. My goal is not to present a final solution, but rather to raise key questions and ideas that could spark further exploration. I believe that by engaging in thoughtful discussions, we can refine and develop this concept to better suit the needs of the XDC network and its stakeholders.

I look forward to hearing your thoughts and feedback on how we can improve the validator node rotation system, and how we can ensure that decentralization remains at the core of the network's future development.

Thank you for taking the time to consider this proposal, and I’m excited to continue the conversation with all of you!

[Solved] Issue with One-Click Installer Download Availability

11ppm — Tue, 06 Feb 2024 23:05:53 +0000

Hi, I want to test the "One-Click Installer", but I am unable to download it on Windows, Linux, and Mac. Please fix so that the download is available.

[Query] Query on Recent Masternode Snapshot Alterations

11ppm — Mon, 15 Jan 2024 00:38:52 +0000

I have a question regarding the mainnet snapshot of the masternode. Previously, when I unzipped the file, an XDC directory was created in the current directory, containing a large number of ldb files. However, when I try it now, the XDC directory is not created, and a large number of files appear directly in the current directory. Has the handling of the snapshot changed? Previously, after unzipping, I believe the XDC directory that was created was moved to the xdcchain directory.

[Solved] Query about XDC Mainnet Gas Price Post-XDPoS 2.0 Upgrade

11ppm — Fri, 17 Nov 2023 04:42:12 +0000

Hi XDC community,

If there are any developers from the XDC team present here, I have a question regarding XDPoS 2.0. I understand that on the Apothem network, the Gas Price has changed as follows:

Before the upgrade:

Gas Limit & Gas Used By Txn: 21,000 | 21,000 (100.00%)
Gas Price: 0.00000000025 XDC (0.25 Gwei)

After the upgrade:

Gas Limit & Gas Used By Txn: 21,000 | 21,000 (100.00%)
Gas Price: 0.0000000125 XDC (12.5 Gwei)

I would like to know if this change to 12.5 Gwei for Gas Price in Apothem will also be applied to the Mainnet. The reason I ask is that when the Apothem network transitioned to XDPoS 2.0, transactions on the Plugin 2.0 nodes failed to complete because the Gas Price exceeded the set limit. Adjusting the settings resolved the issue, allowing transactions to complete. Since a similar situation could occur on the Mainnet, if the Gas Price is expected to be 12.5 Gwei with XDPoS 2.0 there as well, it might be wise to start setting up validator nodes from now to prepare for this change.

Thanks for your time and insights,
11ppm

[Solved] 502 Error on Apothem Network WebSocket

11ppm — Mon, 11 Sep 2023 11:44:36 +0000

Apothem Network's websocket is constantly giving a 502 error. I would like it to be fixed. If there are any other websockets that can be used, please let me know. Currently, there is only one option: wss://ws.apothem.network/. I would like another one to be provided. Thank you.

(It happened again.)The dissociation between "Current Value" and "Estimated Value on Day of Txn On the Explorer

11ppm — Fri, 21 Oct 2022 15:46:13 +0000

The same issue happened. Please fix it.

https://www.xdc.dev/11ppm/the-dissociation-between-current-value-and-estimated-value-on-day-of-txn-on-the-explorer-49an

The dissociation between "Current Value" and "Estimated Value on Day of Txn On the Explorer

11ppm — Tue, 27 Sep 2022 22:48:05 +0000

On the Explorer the dissociation between "Current Value" and "Estimated Value on Day of Txn" is unusually large . It is clearly wrong, and I would like to have it corrected.

https://explorer.xinfin.network/txs/0x5b7ec19ccc74c36c88a04f7ac44867648da936afb48b5b7882aa02dce370b065#overview