# RWA Daily Update - 2026-09-11

## Lesson title

**MAS Project Guardian FX lesson: tokenised bank liabilities still need liquidity providers, price oracles and legal settlement finality.**

## Sources checked

1. **Monetary Authority of Singapore - Guardian FX workstream: Use of tokenised bank liabilities for transaction banking**
   - Landing page URL: https://www.mas.gov.sg/publications/monographs-or-information-paper/2025/guardian-fx-transaction-banking
   - PDF URL: https://www.mas.gov.sg/-/media/mas-media-library/development/fintech/guardian/project-guardian-fx-workstream-transaction-banking.pdf
   - Publication date shown by MAS page: 03 July 2025. PDF document date: 01/07/2025.
   - Retrieval: managed web extraction retrieved the official MAS page and PDF text successfully on 2026-09-11.
   - Extracted official-source facts:
     - The report is a Guardian Foreign Exchange Industry Group paper led by Ant International with ISDA collaboration and contributions from GFMA GFXD, MAS, OCBC, BNY and HSBC.
     - It uses `tokenised bank liabilities` in a broad functional sense for commercial bank money represented on a shared ledger, without asserting a specific legal or regulatory classification.
     - MAS describes cross-border payment and FX pain points including time-zone/cut-off constraints, correspondent-banking complexity, cost opacity, fragmented settlement layers and settlement risk.
     - The report says shared-ledger and tokenised-bank-liability systems may support 24/7 operations, but meaningful use requires adequate operational and legal frameworks and commonly recognised settlement finality.
     - It identifies operating models including a liquidity provider swapping tokens between different currencies/issuers, hash-time locked contracts between private permissioned ledgers, and shared-ledger-based PvP orchestration.
     - The risk table flags parallel digital/fiat systems, liquidity fragmentation, smart-contract malfunction, cybersecurity, data integrity, delayed finality, interoperability, third-party dependencies, jurisdictional variability, evolving regulations and limited transparency into platform governance/intermediary roles.
     - The Ant International example describes a liquidity provider, off-chain FX pricing through a price oracle, and automatic AML screening through a user whitelist maintained by the MTS service provider.

2. **Existing Managing Expectations RWA source trail**
   - Checked `rwa.html` and recent source notes through 2026-09-10.
   - Earlier updates covered MAS Project Guardian at a general standards level, Swift tokenised-deposit orchestration, BIS stablecoin/tokenised-deposit distinctions, settlement-asset questions, CCP collateral risk, and tokenised-bond market evidence. Today's angle is distinct: the specific FX transaction-banking mechanics that appear when tokenised bank liabilities cross currencies and issuers.

## No-hype summary

MAS's Guardian FX workstream is a useful RWA lesson because it shows that tokenised bank liabilities are not just `bank deposits on a blockchain`. In cross-border FX, the hard part is exchanging bank-liability tokens in different currencies, potentially issued by different banks, across ledgers and legal regimes. The paper discusses several operating models: a liquidity provider that swaps tokens, hash-time locked contracts between private permissioned ledgers, and shared-ledger PvP orchestration.

The practical lesson is that every promised 24/7 payment rail imports new diligence questions. Who is the liquidity provider? Who supplies the off-chain FX price? Is the price oracle reliable? Are AML/user whitelists and manual review controls documented? At what exact point is settlement final, unconditional and legally recognised across jurisdictions? MAS's paper is optimistic about potential efficiency, but it also flags risks around fragmented liquidity, smart-contract bugs, cyber resilience, third-party dependencies, transparency and legal/regulatory uncertainty.

## Learning takeaways

- Tokenised bank liabilities can represent commercial bank money on programmable rails, but the legal category may vary by jurisdiction.
- Cross-currency tokenised payments still need FX conversion mechanics; tokenisation does not remove liquidity-provider, pricing or settlement-risk questions.
- A price oracle is a critical control point when off-chain FX prices are used to execute on-chain/token swaps.
- `24/7` availability is not the same as legal settlement finality, insolvency protection, error reversibility or regulatory approval.
- Serious RWA payment infrastructure must document governance, compliance controls, incident response and contractual liability among banks, providers and platform operators.

## Practical watch phrase / question

Watch phrase: **liquidity provider plus price oracle**. Ask: **when tokenised bank-liability tokens in two currencies are swapped, who quotes the price, who holds the liquidity, who can reverse or pause errors, and when is settlement legally final?**

## Editorial caution

Educational source note only. This is not investment, legal, tax, banking, FX, custody, payment-system, stablecoin, tokenised-deposit, smart-contract, liquidity-provider, oracle, AML/compliance or regulatory advice. The MAS source supports a transaction-banking infrastructure lesson; it does not endorse any bank, tokenised-bank-liability product, liquidity provider, FX venue, chain, wallet, fund, stablecoin or investment strategy.