Developers Forum for XinFin XDC Network: XinFin XDC Network

How to Host an XDC Masternode Using Fireblocks via WalletConnect (Step-by-Step Guide)

XinFin XDC Network — Tue, 24 Mar 2026 09:13:40 +0000

Running a Masternode on the XDC Network requires staking 10,000,000 XDC, completing KYC, and securely managing validator funds.

For institutions and enterprises, using Fireblocks via WalletConnect v2 provides institutional-grade custody, governance automation, and transaction policy control.

This guide walks through the complete process using your referenced application flow and screenshots.

Why Use Fireblocks for XDC Masternode Hosting?

Fireblocks is an institutional digital asset custody and operations platform used by exchanges, fintechs, funds, and enterprises.

Multi-Layer Security

1️⃣ MPC-CMP Wallet Technology

Private keys are split into encrypted shares.
No single entity ever holds the full private key.
Eliminates single-point key compromise risk.

2️⃣ Secure Hardware (Intel SGX)

Signing operations occur inside secure enclaves.
Protects against malware and insider threats.

3️⃣ Policy Engine – Automated Governance Controls

The Policy Engine automates governance policies for transaction rules and admin approvals.
It allows you to configure rules that dictate how transactions are handled and approved.

You can define rules to:

Automatically approve transactions
Block transactions
Require additional signers

Rules can be applied using filters such as:

Transaction amount thresholds
Smart contract interaction
Specific destination addresses

Policy Engine rules can be configured for:

Internal wallets
Network connections
Exchanges
Fiat providers
Whitelisted addresses
Smart contract wallets

This is extremely valuable for Masternode staking because:

Large 10M XDC deposits can require multi-admin approval
Only approved validator contracts can be interacted with
Unstaking can require additional governance checks

4️⃣ Admin Quorum & MFA

Multi-admin approval workflows
Role-based access control
Multi-factor authentication enforcement
This makes Fireblocks ideal for institutional masternode operators.

Prerequisites Before Starting

Before beginning:

Fireblocks workspace with Web3 Wallet enabled
Minimum 10,000,000 XDC in your Fireblocks vault
Masternode server deployed and coinbase address generated
KYC document in PDF format

Masternode Application URLs:

Mainnet: https://mn.xinfin.network
Testnet: https://mn.apothem.network

Step-by-Step: Host XDC Masternode via Fireblocks

STEP 1: Open Masternode Application & Select WalletConnect v2

Visit the Masternode App.
Click Login (top right corner).

On the login page:

Under Network Provider, select: WalletConnect v2
Click Save

This initiates a WalletConnect session.

STEP 2: Scan QR Code with Fireblocks

After selecting WalletConnect:

A QR code window appears labeled Fireblocks
You will see:

Mobile / WebApp toggle
QR Code
“Scan this QR Code with your phone”

Action:

Open Fireblocks Web3 Wallet (Mobile App or Web UI)
Scan the QR code
Approve session request

This connects your Fireblocks vault to the XDC Masternode dApp.

STEP 3: Connect Vault to dApp

After scanning:
A popup appears: Connect vault to dApp

You will see:

Vault Account dropdown
Blockchain selection
Default fee rate (Medium / Fast)

Action:

Select the correct Vault account containing 10M+ XDC
Confirm Blockchain (XDC Network)
Click Connect Vault

Now your Fireblocks wallet is connected to the Masternode app securely via WalletConnect v2.

STEP 4: Click “Become a Candidate” & Stake 10,000,000 XDC

After successful login:

Click Become a candidate (top right)

You will now see the Masternode staking interface.

Inside the “Become a MasterNode” panel, You will see:

Minimum requirement: 10,000,000 XDC
Deposit will be locked
Stake field (pre-filled 10,000,000)
TX fee displayed

⚠️ The deposit will be locked as part of validator staking.

Now, In the highlighted section, You must enter:
Coinbase Address

This is your node’s validator address, generated when setting up your masternode server.

Example format:
xdc……………………………………b

⚠️ Important:

This is NOT your Fireblocks wallet address
It is your masternode server’s coinbase address

Once Stake amount confirmed & Coinbase address entered, Click on the Apply button.

STEP 5: Approve Transaction in Fireblocks

Once Apply is clicked:

Fireblocks will prompt a transaction approval

Depending on Policy Engine rules:

It may auto approve
It may require multiple signers
It may require admin quorum

Approve transaction securely.

STEP 6: Transaction Confirmation

After approval:

Transaction is broadcast to XDC Network
You will receive a transaction hash
Stake becomes locked
Node enters validator candidate pool

You can verify transaction on:
https://xdcscan.com

What Happens Next?

After staking:

Your masternode enters validator selection cycle
Once approved in an epoch
It becomes active validator
Begins earning rewards

Why Fireblocks is Ideal for Institutional Masternodes

Using Fireblocks provides:

Institutional custody of 10M+ XDC stake
Governance enforcement through Policy Engine
Multi-signature style MPC security
Hardware-enclave signing
Vault-level segregation of validator funds
Controlled unstaking workflows

This reduces operational and governance risk significantly compared to browser wallets.

Useful Links

Disclaimer

This article is intended strictly for educational and informational purposes only. It does not constitute financial, investment, or legal advice.

Running a masternode on the XDC Network, including staking requirements and infrastructure setup, involves technical, operational, and financial considerations. Readers are encouraged to conduct their own research (DYOR) and consult with qualified professionals before making any decisions related to digital assets or blockchain participation.

The mention of platforms such as Fireblocks or technologies like WalletConnect is for informational purposes only and does not imply endorsement.

By following this guide, you acknowledge that any actions taken are at your own risk.

Node Operator Alert: XDC Cancun hard fork (v2.6.8) is approaching

XinFin XDC Network — Mon, 26 Jan 2026 07:33:28 +0000

The v2.6.8 “Cancun” upgrade is scheduled to activate at Block 98,800,200, approximately 3 days from now. If your node is still running at a version lower than v2.6.8, you need to upgrade immediately.

The upgrade is scheduled to activate at Block 98,800,200.
⏳ Countdown: https://xdcscan.io/block/countdown/98800200

📖 Full technical overview:
https://www.xdc.dev/anilchinchawale/xdc-network-v268-cancun-upgrade-a-leap-forward-in-performance-and-compatibility-3pc5

⚠️ Important:
This is a hard fork. Any node that does not upgrade before the activation block will:

Fall out of consensus
Fail to sync
Be unable to produce valid blocks

🙏 We sincerely thank the node operators who have already upgraded. Your timely action plays a critical role in maintaining network stability and ensuring a smooth transition during the Cancun upgrade.

Who needs to act?
✅ Node owners / operators
❌ Normal users (no action required)

Upgrade instructions (summary):
From your mainnet directory, run:
bash upgrade.sh

We strongly recommend upgrading as soon as possible to avoid disruption.

XDC Network to Introduce EIP-1559 Support on Apothem Testnet.

XinFin XDC Network — Tue, 04 Feb 2025 11:10:25 +0000

The XDC Network continues to evolve with its latest upgrade, bringing EIP-1559 support to the Apothem Testnet. Scheduled for Block Number 71,550,000, this major update is targeted for February 14, 2025.

EIP-1559 is a crucial Ethereum improvement proposal that introduces a base fee model for transactions, improving fee predictability and enhancing the network's overall efficiency. By integrating this feature into the XDPoS v2.5.0-beta1 update, the XDC Network is advancing towards a more seamless and optimized transaction experience.

The XDC team has announced the release of v2.5.0-beta1, introducing significant improvements and new features to the Apothem Testnet. This update focuses on performance optimization, the implementation of Ethereum Improvement Proposals (EIPs), enhancements to RPC and API functionalities, and critical security fixes.

Performance Improvements

Optimized VM Execution: The virtual machine (VM) execution has been refined by reducing allocations and eliminating redundant conversions, leading to faster processing times.
Efficient Jump Destination Analysis: Unnecessary map lookups during jump destination analysis have been removed, streamlining the execution process.
Refactored VM Context: The vm.Context has been restructured into BlockContext and TxContext, providing a clearer and more efficient framework.
Enhanced EVM Reusability: Improvements have been made to the Ethereum Virtual Machine (EVM) to enhance its reusability across different modules.

Implementation of Ethereum EIPs

This release integrates several Ethereum Improvement Proposals to enhance network functionality:
EIP-1559: Introduces a new fee market mechanism, aiming to stabilize transaction fees and improve user experience.
EIP-2565: Lowers the cost for modular exponentiation, making cryptographic operations more efficient.
EIP-3651: Implements a warm coinbase feature for gas optimization, reducing costs associated with coinbase address access.
EIP-1153: Introduces transient storage, allowing for temporary storage during transaction execution, which can optimize certain contract operations.

RPC and API Enhancements

RPC Gas Cap: A new rpc-gascap flag has been added, setting the RPC gas cap to 50 million, providing better control over gas usage in remote procedure calls.
New API Method: The xdpos_getBlockInfoByEpochNum API has been introduced, enabling users to retrieve block information based on epoch numbers.
Gas Price Calculation Fix: Issues with gas price calculations in empty blocks have been addressed, ensuring accurate fee assessments.
EstimateGas API Improvement: Enhancements have been made to the EstimateGas API for more precise gas estimations.
Trusted Peer Management: New RPC methods admin_addTrustedPeer and admin_removeTrustedPeer have been added, allowing for better peer management within the network.

Security and Bug Fixes

Log Retrieval Fix: Resolved issues with block hash retrieval in the eth_getLogs method, ensuring accurate log data.
Transaction Pool Optimization: Addressed high pending special transactions in the core transaction pool, improving transaction handling efficiency.
Code Quality Improvements: Fixed various static analysis warnings to enhance overall code quality and maintainability.
Memory Leak Resolution: Fixed a memory leak in the node.Node AccountsManager, ensuring more stable node operations.

Code Refactoring and Cleanup

-Removal of Redundant Elements: Unused functions, redundant conversions, and unnecessary package imports have been eliminated to streamline the codebase.

-Migration to Updated Libraries: Transitioned from the deprecated ioutil package to io and os packages, aligning with modern Go language practices.

This release marks a significant step forward for the XDPoSChain, enhancing performance, security, and functionality. Users and developers are encouraged to test these updates on the Apothem Testnet and provide feedback to the development team.

For a comprehensive overview and to access the release, visit the official GitHub page: XDPoSChain v2.5.0-beta1 Release

[Informative] Token Reduction Triumph: XinFin XDC Network Community Executes 35 Million XDCE Burn.

XinFin XDC Network — Thu, 14 Dec 2023 10:09:21 +0000

The XDC Network community has reduced the supply of XDCE tokens by 35 Million and the token burn continues until XDCE contract termination.

The XDC Network community has decided to further reduce the supply of XDCE tokens, after the last major 2.1 billion, 300 million, 200 million, 500 million, 500 million, 500 million, 300 million, 10 million token burn. Hence, the network burns 35 million XDCE tokens taking the total supply of XDCE to approx. 363 million tokens. The community also plans to further reduce the supply of the XDCE tokens in the near future until the contract termination of XDCe. The users holding XDCE are requested to swap their XDCE with XDC as soon as possible. Swaps for the XDCE users will be provided by Mywish crosschain Swap.

XDCe Burning Transaction Detail:

Token Burn Hash:
https://etherscan.io/tx/0xcbf19a98e612a9e3a6c88082b2b5527b84a2f3604e3a9c73c2a6bf02168be189

Token Address: https://etherscan.io/token/0x41ab1b6fcbb2fa9dced81acbdec13ea6315f2bf2

We Are Open to Feedback

We believe that we can deliver the best of the XinFin XDC Network and the XDCE and XDC tokens to our users only when we know what our community members need. This is why we welcome feedback from our community members with open arms and work on them to make the network ready for the digitized future.

Find more information about XDC Network by visiting our website XinFin.org and follow us on our social medias: Twitter || Telegram || LinkedIn || Reddit || Facebook || Forum

[Informative]Enhancing Gas Fee Efficiency on the XDC Network: Improving Gas Management for Sustainable Operations.

XinFin XDC Network — Tue, 07 Nov 2023 12:22:26 +0000

The XDC Network aims to be at the forefront of innovation, constantly striving to improve its infrastructure for greater efficiency and sustainability. One of the recent proposals aimed at enhancing the network's performance is a strategic move to implement efficient gas fee management. Gas fees play a vital role in blockchain operations, particularly in terms of transaction processing and network functionality. While gas fees have increased, this upgrade on the Apothem Network (testnet) is designed to revolutionize gas management and optimize the fee structure for users and developers.

Here are some key aspects of this proposal and its significance for the XDC Network:

Efficient Gas Fee Structure: The proposed adjustments aim to refine the gas fee structure, ensuring a more predictable and manageable cost for transactions within the XDC Network. This refinement is anticipated to offer users a more user-friendly and stable fee experience.

Balancing Supply and Demand: By implementing a variable fee structure that automatically adjusts based on network activity, the XDC Network aims to strike a balance between transaction demand and network capacity. This adjustment should promote more efficient gas usage, reducing congestion and potential network slowdowns.

Sustainability and Network Optimization: The ultimate goal of this proposal is to enhance the sustainability and efficiency of the XDC Network. By providing a more structured and sustainable approach to gas fees, the network is poised to offer a more scalable, user-friendly, and cost-effective environment for its users and developers.

User-Centric Approach: With an eye toward user convenience, this proposal is expected to bring about a more user-centric experience by offering transparency in fee management. It aims to streamline the transaction process, provide a more predictable cost structure, and improve overall user satisfaction.

Now, XDC Apothem node upgrade is on the horizon. Node owners are encouraged to prepare for this upgrade, ensuring the continued seamless operation of the network. The upgrade will occur upon reaching the block height indicated in the countdown timer, currently visible at Countdown Link.

For node owners, it's imperative to stay updated and execute the necessary steps for a smooth transition.
To upgrade your Apothem node to XDC 2.0 , please use the following command:

git pull && ./docker-up.sh

In a significant update reflecting the XDC Network's commitment to progress, recent enhancements showcase a marked change in gas fees and overall transaction costs. The update, while maintaining a gas limit of 21,000, has effectively led to a transition in gas prices. Before the upgrade, gas was priced at 0.00000000025 XDC (0.25 Gwei), with a transaction fee of 0.00000525 XDC for a 100 XDC value. Following the upgrade, there was a substantial shift: gas price managed to 0.0000000125 XDC (12.5 Gwei) and the transaction fee rose to 0.0002625 XDC for the same 100 XDC value. This change signifies the network's evolution to balance efficiency and user convenience, with an updated fee structure reflecting this improvement.

Here's a summary of the before and after upgrade values:

Before upgrade:
Value: 100 XDC
Gas Limit & Gas Used By Txn: 21,000 | 21,000 (100.00%)
Gas Price: 0.00000000025 XDC (0.25 Gwei)
Actual Tx Cost/Fee: 0.00000525 XDC

After upgrade:
Value: 100 XDC
Actual Tx Cost/Fee: 0.0002625 XDC
Gas Limit & Gas Used By Txn: 21,000 | 21,000 (100.00%)
Gas Price: 0.0000000125 XDC (12.5 Gwei)

These combined updates signify the XDC Network's commitment to continual improvement and innovation. The proposed gas fee enhancement aligns with efforts to streamline transaction costs, offering a more user-friendly and cost-effective experience. Additionally, the Apothem node upgrade to XDC 2.0 is vital for maintaining the network's efficiency and stability.

What's New with XDC 2.0?

Introducing XDPoS 2.0, the future of decentralized consensus on the XDC Network! This next-gen engine, built on the cutting-edge BFT consensus protocol, promises military-grade security and blazing performance while being ultra resource-efficient. Plus, it's fully backwards-compatible with existing APIs.
Dive deeper into the details: https://arxiv.org/pdf/2108.01420.pdf

As the countdown continues and the community gears up for the Apothem node upgrade to XDC 2.0, it's crucial for node owners to act swiftly to ensure their nodes are updated and in line with the latest improvements. These advancements mark a crucial juncture in the network's journey toward greater efficiency, sustainability, and user-centric functionality.

Stay tuned for these crucial updates and keep your node in sync with the network's evolution. Let's collectively drive the XDC Network towards an optimized and efficient future.