En
← All articles

Simbolon connects two ledgers, not two business days into one

The EUR/SGD experiment links independent ledgers; its operating value still depends on waiting, liquidity commitment and finality rules.

ColumnTechnologyAuthorOpen Market NotesTypeArticle
Two ledger books and clocks show different times, with a red verification slip between the books.

MAS announced on November 16, 2026 that Project Simbolon tested wholesale-CBDC EUR/SGD payment-versus-payment settlement, using zero-knowledge proofs to coordinate independent central-bank test ledgers without direct ledger integration.

This is a new proof of concept, not a cross-border payment service already available to customers. Its significance is not another successful entry under “cross-chain.” It raises a stricter question: when two systems remain separate, who ensures a transaction has a definite outcome across two business days and operating rulebooks? This is Open Market Notes' original analysis of public evidence, not an equation of a trial with production readiness.

Independence does not remove shared responsibility

Keeping systems independent can avoid migrating every participant onto one platform. Integration costs do not disappear, however. They move into expressing transaction conditions, identifying messages, handling exceptions and allocating responsibility. Reading a proof successfully is not the same as agreeing what to do about every unexpected event.

Imagine a transaction is ready and one side enters a maintenance window. The business needs to know whether funds remain usable, whether processing will continue and who can declare the wait over, not whether an interface displays “connected.” This is a hypothetical design problem, not an account of a Simbolon test failure.

A connection can avoid a shared ledger while still requiring shared, executable commitments: which states permit progress, which events require a pause and how long silence can last before intervention. Those commitments cannot be too vague to implement, or so intricate that every change requires both sides to upgrade everything together. Interoperability concerns governing changes to common rules as well as moving information.

Time zones matter through the availability of money

Longer service hours sound like running computers for a few more hours. An institution's underlying concern is when money can fund its next activity. Receiving a status update, obtaining the target currency and being able to pay it onward are three separately testable milestones.

Suppose an investor exchanges currency for a transaction in another market. Faster currency settlement may still leave funds waiting if the downstream business is not accepting payment. Conversely, if that business can receive funds promptly but balances must be prepared far in advance, improving funding timing may matter more than removing the last few seconds. This example assumes no particular market timetable; it separates sources of delay.

Assessing economic value therefore requires more than timing a demonstration transaction. Examine the full interval from preparing funds until they are available again, and distinguish technical waiting from institutional requirements. A service with a fast average but occasional prolonged uncertainty may require users to keep more backup liquidity. The average need not capture the most expensive part.

Correct proofs still leave unfinished work to manage

The joint Insights Note identifies proof generation as the main test latency contributor. Relayers, provers and data access remain dependencies; legal finality needs separate establishment. The detailed report is scheduled for November 18.

This suggests more specific questions for the next stage than whether systems connect. How does a participant identify its current stage while waiting? If a proof has not arrived, are conditions unmet, generation unfinished or transmission delayed? These states may require different responses rather than one generic failure message.

Faster proof generation can improve the experience. Reliability also depends on identifying and bounding failure. If every uncertainty requires restarting the entire business process, repeated reconciliation may consume the speed benefit. If recovery is allowed, the original transaction needs an unambiguous identity so a retry is not treated as a new instruction. These are analytical requirements for future operations, not claims that the experiment lacks such mechanisms.

Likewise, avoiding direct technical integration does not eliminate coordination duties. Maintaining proof services, confirming data availability and notifying the other side of a pause need auditable arrangements. As a connection becomes easier to reproduce, roles and permissions become more important; adding systems can otherwise multiply ambiguity.

Ledger completion and discharge of obligations must align

The BIS financial market infrastructure principles call for a clear final-settlement point and linked final settlement of interdependent obligations. They provide an assessment lens here, not certification of Simbolon's compliance.

A technical state can establish whether a system accepted a change. Legal arrangements determine what that change means within the relevant relationships. Those questions should not be conflated. This article makes no judgment about specific jurisdictional legal effects. The issue to examine is whether institutions can share a consistent understanding of funds and fulfillment at the same identifiable milestone.

This also explains why avoiding a mismatch in principal delivery does not mean eliminating every risk. Even if a design prevents one party paying without the other, an unfinished transaction can still disrupt subsequent plans. Waiting costs, replacement arrangements and committed funds belong in the business comparison; controlling one risk does not erase them.

Simbolon should not be compared with other cross-border projects merely by name or use of tokens. More meaningful dimensions include the nature of the money, control retained by independent systems, timing commitments in normal and exceptional conditions, and recognition of the final outcome. Current evidence supports further examination of this approach, not a claim that cross-border settlement is already an always-on public service requiring no coordination.

The valuable next step is an explicit operating agreement beyond a feasible technical demonstration. It should explain not only how fast success is, but where funds are during unfinished work, who is responsible and when they can be used again. Ledgers may remain independent; participants should not inherit an unexplained wait.

Information only. No investment, legal, tax, or financial advice.