QX Interoperability - v.0.7
  • 💡ABOUT
    • License
    • How to Give Attribution For Usage of QX Interoperability
  • 👬Industry Initiatives
    • ISO Interoperability Framework
    • EEA Crosschain Interoperability Specification Suite
    • IEEE Standards for Blockchain Interoperability
    • ICMA Bond Data Taxonomy
    • IETF Secure Asset Transfer Protocol
    • SODA MIT Crosschain Interop WG
    • Decentralized ID for Tokenization
    • Cross-chain Interoperability Alliance
    • SWIFT Coalition
    • BIS Projects
    • MAS Projects
    • Regulated Liability Network
      • UK Finance - Regulated Liability Network
      • US - Regulated Liability Network
    • Hyperledger Projects
    • EEA-OASIS L2 WG
    • RollColl WG
    • ITU Digital Currency Global Initiative
    • EIP-5164: Cross-Chain Execution
    • EIP-3220: Crosschain Identifier Specification
    • EIP-7281: Sovereign Bridged Token
    • ERC-7092: Financial Bonds
    • ERC-3643: Permissioned Tokens
    • ERC1400: Universal Token for Assets and Payments
    • ERC6960: Dual Layer Token
    • CASA CAIPs
    • COSMOS IBC
    • Polkadot XCM
    • IEEE Crosschain Workshop
  • 🏦Use Cases
    • Payments/Digital Asset Transactions
      • Enable transfers of digital payment tokens
      • Conduct Compliant Cross-VASP Digital Asset Transaction
      • Swap NFT for Tokenized Bank Deposits
      • Enable Intra-Group Payments with Tokenised Deposits
    • Wholesale CBDC (wCBDC)
      • Enable Settlement with Simultaneous Delivery versus Payment
      • Facilitate Cross-Border Payments with wCBDC
      • Enable FX transactions to facilitate cross-border payments
      • Settle Crypto Derivatives using wCBDC
      • Access Liquidity via wCBDC
      • Settle Interbank Payments with wCBDC
      • Settle Interbank Payments with wCBDC (Acquirer-Merchant Settlement)
      • Make Property Payments with Tokenized Deposits
      • Provide FX Liquidity using wCBDC
      • Enable Payment versus Payment (PvP)
      • Crosschain digital bonds trades
    • Decentralized Finance (DeFi)
      • Aggregate Yields across Blockchains for Corporate Treasuries
    • Retail CBDC (rCBDC)
      • Provide Targeted Government Transfers (Government Vouchers)
      • Streamline Home Equity Lending
      • Provide Corporate Vouchers and Rewards
      • Make Milestone-Based Property Purchase Payments
      • Enable Traceable and Targeted Donations
      • Consumer Prepayments to Corporations
      • Enable Asset Transactions
      • Enable Cross-Border Remittances
      • Government Payouts
      • Managing Learning Accounts
    • Private Markets/Asset Tokenization and Trading
      • Tokenize and Trade Private Equity Fund Shares
      • Distribute and Settle Private Corporate Debt Issuance
      • Trade Employee Stock Grants as Digital Securities
      • Enable Secondary Trading for Non-Listed Assets and Private Markets
      • Automated Discretionary Portfolio Management with Tokenized Assets
    • Trade & Commerce
      • Support Tokenized Electronic Bills of Lading for Global Trade
      • Commercial Vouchers
      • Online Commerce
      • Programmable Rewards
    • DAOs
  • 🛠️Solutions Providers
    • Swift
    • Mastercard
    • Fnality
    • Quant Network
    • Ownera
    • Fujitsu
    • Deutsche Bank/Standard Chartered Ventures
    • Kaleido
    • Onyx/JP Morgan
    • Canton Network
    • Universal Digital Payments Network Alliance
    • Li.Fi
    • Visa
    • Partior
    • CLSNet
    • Impel
    • Adhara
    • Datachain
    • Ant Group
    • CitiGroup
    • WeBank
    • IMF ?
    • BIS ?
    • Progmat ?
    • GroundX ?
  • 📓Requirements
    • Legal & Regulatory Layer
    • Governance and Policies Layer
      • Audit and Compliance sub-layer
      • Operations sub-layer
    • Application Layer
    • Integration and Middleware Layer
      • Oracle sub-layer
    • Semantic Layer
    • Syntactic Layer
    • Foundational Layer
      • Discovery sub-layer
      • Smart contract sub-layer
      • Function call sub-layer
      • Messaging sub-layer
      • Transaction sub-layer
      • Consensus sub-layer
      • Data transfer sub-layer
      • Security sub-layer
        • Identity and Authentication
        • Data Privacy
    • -
  • Protocol Providers
    • Chainlink
    • Axelar
    • Connext
    • Across
    • Toposware
    • IBC
    • Hyperlane
    • Sovereign Labs
    • Polymer Labs
    • Orb Labs
    • Zetachain
    • Sygma
    • deBridge
    • Wormhole
    • Routeur Protocol
    • Synapse
    • Wanchain
    • Gnosis
    • LayerZero
    • Comparison
  • Bridging Approaches
    • Bridges
    • Native Bridge
    • Third Party bridge
    • Multi-bridge
    • Oracle
    • Shared Sequencer
    • Mechanisms
      • Hash Locking
      • Notary Schemes
      • Proof Aggregation
    • zk-rollup ecosystems
    • Intent-centric
    • Function Calls
    • Relayers
      • Multisig
      • MPC
      • Light Client
      • ZKP Stark
      • ZKP Snark
      • Hybrid method
Powered by GitBook
On this page

Was this helpful?

  1. Requirements

Legal & Regulatory Layer

PreviousRequirementsNextGovernance and Policies Layer

Last updated 1 year ago

Was this helpful?

Focus: Adherence to legal requirements and standards.

Objective: Ensure compliance with relevant laws and regulations.

Description: This layer governs the legal aspects of blockchain use and interoperability, including compliance with local and international laws, regulatory requirements, and oversight.

Layer owner: National regulatory bodies, International organizations (e.g., Financial Action Task Force (FATF) for anti-money laundering (AML) and combating the financing of terrorism (CFT) regulations)


Some considerations:

  • EU DLT Pilot Regime (DLTR) :

  • Abu Dhabi Global Market (ADGM) DLT Foundations Regime

  • Legal Entity Identifiers (LEIs)

  • A ‘Designated Depository’ role is important to satisfy regulatory obligations. Liability and recourse must be clearly addressed for cross-chain transfers. Issuer control & rights

  • Public blockchains as an underlying settlement layer, how can this be supported in a secure and compliant manner.

  • Regulatory clarity remains the market’s largest need.

  • Ownership of an asset must be legally unambiguous at all times in order to ensure events such as interest payments can be correctly processed, making solutions dependent on technical ‘escrow’ functionality or terminology inappropriate

  • Onboarding of Users: This would be conducted only by Institutions that are regulated entities. All users of the scheme will be KYC’d.

  • Data Privacy: Records and operations would be conducted in the partition operated by an Institution are intended to be private to that institution. Only the parties involved in a transaction would have transaction visibility.

  • FATF Recommendations: Payments would include necessary information of the parties involved in the payments chain through the messaging layer that carries the information associated with each settlement.

  • Sanctions: Participating institutions would sanctions check all transactions according to the applicable lists through the messaging layer.

  • Anti-Money Laundering: participating institutions would conduct AML monitoring through the messaging layer.

  • Fraud: All customer instructions would be authenticated using Strong Customer Authentication (SCA) to reduce the likelihood of fraud.

  • Transaction Limits: These would be maintained by each participating institution and may be enforced through smart contracts.

------------------

Related to tokenization:

  1. Providers take full responsibility for tokenized products, ensure effective record-keeping, and demonstrate operational soundness.

  2. Public-permissionless blockchains cannot be used without proper controls.

  3. Disclosure on whether settlements happen on-chain or off-chain.

  4. Providers must prove ownership of tokens at all times.

  5. Have at least one competent staff member with relevant experience to operate/supervise tokenization arrangements and manage associated risks.

  6. Meet all applicable product authorization requirements for the underlying investment product being tokenized.

  7. Implement additional safeguards to address risks associated with tokenization.

  8. Clearly disclose terms and details of tokenization arrangement to investors.

  9. Comply with all existing regulatory requirements applicable to the underlying product.

  10. Ensure intermediaries meet licensing requirements and are competent in tokenized products.

  11. Conduct proper due diligence on agents distributing tokenized products.

  12. Provide regular training to staff on tokenized products and arrangements.

https://www.esma.europa.eu/sites/default/files/2023-10/ESMA12-2121844265-3182_Report_on_the_DLT_Pilot_Regime_-_Study_on_the_extraction_of_transaction_data.pdf
https://www.trisa.io/
📓
Page cover image