24th July Update

Firstly, we highlight the following, summarised from our Development Updates page:

We will publish updates when appropriate. It just so happens that the first two updates were weekly - we aim to engage publicly when it makes the most sense.

That said, here is an update on Quant Fusion's public release progress as of the 24th July 2025.

Where to provide feedback?

There are multiple places for you to provide feedback.

For private feedback contact us via https://quant.network/contact/, especially if you are looking to:

build an app on Fusion
build an open source connector for Fusion

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

24th July Update

As regards the Multi-Ledger Rollup section of Fusion, we have been hardening our backend processes; think devops automated pipelines, full unit and integration test coverage, and detailed audit reviews. This is a process that takes time but is a necessity as we prepare for the public Testnet launch phase.

As regards the Network of Networks section of Fusion, our key recent focus has been on finalising the "Open Source Connector" specification, which will be released to selected builders next week. Which led us to this decision point:

Decision Point: What public blockchains should our "Open Source Connector Specification" be initially tested against?

Key criteria:

(1) a Quant Fusion connector doesn't currently exist for this blockchain

(2) it is a fairly popular public blockchain

(3) it has some technically interesting characteristics to challenge our specification against

Decision: The chosen blockchains were:

(A) Hedera. Why? Hedera satisfies (1) and (2). It also has technically interesting characteristics such as: (i) it's Directed Acyclic Graph (DAG) based consensus protocol; (ii) it's combination of native on-chain services (e.g. tokenisation service, file service,...) and smart contract capabilities; and (iii) its high performance (high potential transactions-per-second, predictable fees, low energy usage).

(B) SUI. Why? SUI satisfies (1) and (2). It also has technically interesting characteristics such as: (i) it's object-centric data model, where all on-chain assets are treated as programmable objects with ownership; (ii) it's Move smart contract language; and (iii) its parallel execution engine, where transactions that don’t touch shared state are processed in parallel without consensus.

We will evaluate the implemented connectors and consider any tweaks to the specification before its public launch.

If you would like access to our open source connector specification before public release, please reach out to us through the feedback method mentioned above.

Next Steps

Continue with the Multi Ledger Rollup code reviews, audits and testing
Continue building towards Fusion's network of network release