5th January Update

This is the first 2026 update for Quant Fusion.

Where to provide feedback?

There are multiple places for you to provide feedback. For private feedback, including if you are looking to build on Fusion, contact us via https://quant.network/contact/

For public feedback on x.com, use the hashtag #QuantFusion and tag the newly created @FusionLayer25, then your feedback will be read when possible.

5th January Update

Before Christmas, we restarted the testnet version of the Multi-Ledger Rollup. As a reminder, this was required to deploy updates to the Fusion Firewall smart contracts, which are intentionally non-upgradeable once live.

These updates were driven by institutional feedback of the previous testnet version, where it was requested to have greater flexibility, including:

• Allowing institutions to manage their own token whitelists, rather than relying solely on a Quant-managed whitelist.
• If institutions whitelisted the same token(s), they still could isolate liquidity on the rollup side if desired.
• Quant will provide live updates of the whitelist details on-chain in the rollup in a private preserving manner, which will be useful for synchronisation with off chain systems.

All of the above enhancements have now been implemented and are live.

We also added the "Bring Your Own Node" (BYON) feature.

This is a foundational upgrade to allow Quant Connect users to start connecting their own nodes to Fusion.

We begin by allowing nodes from some pre-selected node providers.

The rationale for starting with pre-selected providers is:

1. It simplifies the setup and maintenance process for user nodes
2. It establishes a level of reliability for the connected nodes

After we get a certain number of these types of nodes connected, then we can consider user-hosted nodes as well or an expanded number of node providers.

It is worth noting that the backend infrastructure is fully generic. Any EVM-compatible node can be connected to Fusion in the same way once Quant enables this in the UI. Non-EVM nodes can also be supported, requiring only minor adjustments to the parameters provided by users in the UI.

For this initial testing phase, we are limiting connectivity to the Sepolia and Amoy public testnets for demonstration purposes.

In parallel, we have been building out the required staking infrastructure.

Of course staking and BYON are interlinked. When a user provides a node and wishes to be eligible for staking rewards, they will stake QNT “against” that node.

At present, nodes will be removed from Fusion if they are not available continuously throughout the day. We are considering adjustments to this behaviour to improve inclusivity.

Anyway, We do not currently plan to implement slashing for unreliable nodes. Experience from other networks (for example, Avalanche) suggests that withholding staking rewards can be a sufficient deterrent.

Next Steps

Quant continues to build for both QNT staking and a mainnet launch of the rollup.