cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start [2022/04/19 19:36] nick |
cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start [2022/06/17 19:09] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Question: 12. TBD I M P O R T A N T How could a CBDC provide privacy to consumers without providing complete anonymity and facilitating illicit financial activity? ====== | + | ====== Question: 12. How could a CBDC provide privacy to consumers without providing complete anonymity and facilitating illicit financial activity? ====== |
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:start| Return to CBDC Benefits, Risks, and Policy Considerations ]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:start| Return to CBDC Benefits, Risks, and Policy Considerations ]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | Question: 12. How could a CBDC provide privacy to consumers without providing complete anonymity and facilitating illicit financial activity? | ||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </WRAP> | | ||
| ===== Question ===== | ===== Question ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] |
| **How could a CBDC provide privacy to consumers without providing complete anonymity and facilitating illicit financial activity?** | **How could a CBDC provide privacy to consumers without providing complete anonymity and facilitating illicit financial activity?** | ||
| ===== Answer ===== | ===== Answer ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] |
| : **Note:** See the answers to the sections: | : **Note:** See the answers to the sections: | ||
| - | * [[cbdc:private:cbdc_omg:04_doc:15_common:45_privacy:start]] | + | * [[cbdc:public:cbdc_omg:04_doc:15_common:45_privacy:start]] |
| - | * [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q04:start]]. | + | * [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q04:start]]. |
| - | The simplest way to achieve this would rely on the existing intermediary financial institutions to continue to do what they already do in terms of [[[[cbdc:private:cbdc_omg:04_doc:15_common:45_privacy:start | Privacy]], [[:cbdc:private:cbdc_omg:04_doc:15_common:48_natsec:start | Natonal Security]], and [[https://www.omgwiki.org/CBDC/doku.php?id=cbdc:private:cbdc_omg:04_doc:15_common:50_international:start | International Security]] BUT with the addition of the ability to use a real-time U.S. CBDC transfer mechanism instead of only the existing [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:ach | Automated Clearing House (ACH) Network]]. This allows the existing mechanisms that are part of the existing intermediaries structure to remain in place for Privacy and Security. This of course assumes the existing mechanism on Privacy and Security is acceptable. | + | The simplest way to achieve this would rely on the existing intermediary financial institutions to continue to do what they already do in terms of [[cbdc:public:cbdc_omg:04_doc:15_common:45_privacy:start| Privacy]], [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start| National Security]], and [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start | International Security]] BUT with the addition of the ability to use a real-time U.S. CBDC transfer mechanism instead of only the existing [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:ach | Automated Clearing House (ACH) Network]]. This allows the existing mechanisms that are part of the existing intermediaries structure to remain in place for Privacy and Security. This of course assumes the existing mechanism on Privacy and Security is acceptable. |
| - | In essence, it would mean adding a new parallel U.S. CBDC transaction network to the existing ACH Network. The new U.S. CBDC network handles the real-time transactions requirements of the U.S. CBDC. This requires the: | ||
| - | |||
| - | * Development of a U.S. CBDC is probably based on Stablecoin Model. | ||
| - | * Use of an energy-efficient Consensus Algorithm | ||
| - | * Development of a bridge between the existing ACH Network and the new U.S. CBDC Network | ||
| - | * Development of a new standardized [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interface (API)]] to connect the outside world to the newly enhanced combined ACH Network and CBDC Network for the existing intermediaries to use for transfers | ||
| - | : **Note:** The API could be in the form of Web Services, Remote Procedure Calls (RPC), [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:c:corba | Common Object Request Broker Architecture (CORBA)]], [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:dds | Data Distribution Service (DDS)]] or other interprocess communication mechanisms defined using [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.b_stds:tech:omg:idl&s[]=idl | ISO/OMG Interface Definition Language (IDL)]], [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:w:wsdl | standardized Web Services Interface Language (WSDL)]], etc. | ||
| - | |||
| - | Figure {{ref>simpleCbdcFlow}} provides a very simplistic overview of how a Dual ACH/CBDC network might work. The intention is to build onto the existing financial system already in place but to allow an option to use a U.S. CBDC probably built as a Stablecoin. The Existing Intermediaries would still fulfill their existing roles while providing an option to use a CBDC network to transfer the money. The existing validation and verification for the number of transactions, the quantity of money transferred, and all of the checks for criminal activity and assurance for privacy would stay in place. | ||
| - | |||
| - | |||
| - | <figure simpleCbdcFlow> | ||
| - | {{ :cbdc:private:cbdc_omg:04_doc:20_comments:brp:q12:screen_shot_2022-04-19_at_12.58.12_pm.png?700 |}} | ||
| - | <caption>Theoretical Very Simplified Dual ACH-CBDC Network Concept.</caption> | ||
| - | </figure> | ||
| - | |||
| - | <table DualNetworkFlow> | ||
| - | ^ Scenario ^ Step Number ^ Description ^ | ||
| - | ^ Current Process ^ 1 | <WRAP> | ||
| - | The First End User (Person, Corporation, Institution, a Computer process, etc.) goes into an Existing Intermediary and wants to transfer money to a Second End User. | ||
| - | </WRAP>| | ||
| - | ^ ^ 2 | <WRAP> | ||
| - | The First Existing Intermediary uses the newly U.S. CBDC Application Programming Interface (API) to start the transaction. The First Existing Intermediary asks if the money is to be transferred immediately requiring U.S. CBDC or if it will just be done using U.S. Dollars. | ||
| - | </WRAP>| | ||
| - | ^ ^ 3 | <WRAP> | ||
| - | The FIrst End User responds that they will be using U.S. Dollars. | ||
| - | </WRAP>| | ||
| - | ^ ^ 4 | <WRAP> | ||
| - | A transaction is created that meets the requirements of the ACH is formulated. | ||
| - | </WRAP>| | ||
| - | ^ ^ 5 | <WRAP> | ||
| - | The ACH Transaction is placed onto the existing ACH Network and routed to the appropriate Second Existing Intermediary. | ||
| - | </WRAP>| | ||
| - | ^ ^ 6 | <WRAP> | ||
| - | The Second Existing Intermediary receives the transaction and waits for the transaction to settle (usually within 24 hours). | ||
| - | </WRAP>| | ||
| - | ^ ^ 7 | <WRAP> | ||
| - | The Second Existing Intermediary places the money designated in the transfer transaction to the Second End User's bank account (i.e., debit, credit, checking, savings, Credit Card account, etc.) | ||
| - | </WRAP>| | ||
| - | ^ ^ 8 | <WRAP> | ||
| - | The Second End User possesses the money. | ||
| - | </WRAP>| | ||
| - | ^ Scenario ^ Step Number ^ Description ^ | ||
| - | ^ U.S. CBDC Process ^ 1 | <WRAP> | ||
| - | The First End User (Person, Corporation, Institution, a Computer process, etc.) goes into an Existing Intermediary and wants to transfer money to a Second End User. | ||
| - | </WRAP>| | ||
| - | ^ ^ 2 | <WRAP> | ||
| - | The First Existing Intermediary uses the newly U.S. CBDC Application Programming Interface (API) to start the transaction. The First Existing Intermediary asks if the money is to be transferred immediately requiring U.S. CBDC or if it will just be done using U.S. Dollars. | ||
| - | </WRAP>| | ||
| - | ^ ^ 3 | <WRAP> | ||
| - | The First End User responds that they will be using U.S. CBDC. | ||
| - | </WRAP>| | ||
| - | ^ ^ 4 | <WRAP> | ||
| - | The First Existing Intermediary verifies that the First End User has the correct amount of U.S. CBDC to complete the transaction. If Not, the First End User can convert some existing U.S. Dollars to U.S. CBDC to complete the transaction. | ||
| - | </WRAP>| | ||
| - | ^ ^ 5 | <WRAP> | ||
| - | A transaction is created that meets the requirements of the U.S. CBDC is formulated. | ||
| - | </WRAP>| | ||
| - | ^ ^ 6 | <WRAP> | ||
| - | The U.S. CBDC Transaction is placed onto the new U.S. CBDC Network and routed to the appropriate Second Existing Intermediary. | ||
| - | </WRAP>| | ||
| - | ^ ^ 7 | <WRAP> | ||
| - | The Second Existing Intermediary receives the U.S. CBDC transaction after the transaction is been validated and verified by the U.S. CBDC Consensus Alorithm. | ||
| - | </WRAP>| | ||
| - | ^ ^ 8 | <WRAP> | ||
| - | The Second End User possesses the money. | ||
| - | </WRAP>| | ||
| - | |||
| - | <caption>Various steps in using a simplistic theoretical dual ACH/CBDC network.</caption> | ||
| - | </table> | ||
| ===== Examples ===== | ===== Examples ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] |
| - | The "desirements" specified in [[https://www.omgwiki.org/CBDC/doku.php?id=cbdc:private:cbdc_omg:15_summary:start&do=edit | White Paper]] and identified by the [[https://www.omgwiki.org/CBDC/doku.php?id=cbdc:private:cbdc_omg:15_summary:start | OMG's White Paper Analysis]] as **Privacy Issues** are listed in Table {{ref>privacyReq}}. | + | For a list of desirements, see [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start#examples| Dual Payment Networks - Examples]] |
| - | <table privacyReq> | ||
| - | <caption>Examples of **Privacy Desirements** identified during the White Paper Analysis conducted by the OMG</caption> | ||
| - | |< 100% 20% ->| | ||
| - | ^ Category ^ Desirements ^ | ||
| - | ^ Benefits | B0004, B0022 | | ||
| - | ^ Policies and Considerations | P0004 | | ||
| - | ^ Risks | R0014 | | ||
| - | ^ Design | D0012 | | ||
| - | </table> | ||
| ===== Discussion of Examples ===== | ===== Discussion of Examples ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] |
| - | + | ||
| - | Table {{ref>privacyReqDiscussion}} provides discussion points for each of the "desirements" identified by the [[https://www.omgwiki.org/CBDC/doku.php?id=cbdc:private:cbdc_omg:15_summary:start | OMG's White Paper Analysis]]. | + | |
| - | <table privacyReqDiscussion> | ||
| - | <caption>Privacy references of desirements in the **White Paper**</caption> | ||
| - | |< 100% 5% 45% 50%->| | ||
| - | ^ Desirement No. ^ Desirement Text ^ Comment ^ | ||
| - | ^ B0003 ^ Complement, rather than replace, current forms of money and methods for providing financial services | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0004 ^ Protect consumer privacy| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0005 ^ Protect against criminal activity| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0007 ^ Provide households and businesses a convenient and electronic form of central bank money with: <WRAP> | ||
| - | - safety | ||
| - | - liquidity | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0008 ^ Provide entrepreneurs a platform on which to create new financial products and services | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0009 ^ Provide faster and cheaper payments (including cross-border payments) | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0011 ^ Make payments: <WRAP> | ||
| - | - faster | ||
| - | - cheaper | ||
| - | - more convenient | ||
| - | - more accessible | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0012 ^ Provide payment services to households and businesses around the clock, every day of the year| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0013 ^ Provide immediate access to transferred funds| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0022 ^ Provide a CBDC that is:<WRAP> | ||
| - | - [[cbdc:private:cbdc_omg:8_append:20_glossary:privacy-protected| Privacy-Protected ]] | ||
| - | - [[cbdc:private:cbdc_omg:8_append:20_glossary:intermediated| Intermediated]] | ||
| - | - [[cbdc:private:cbdc_omg:8_append:20_glossary:transferable| Widely Transferable]] | ||
| - | - [[cbdc:private:cbdc_omg:8_append:20_glossary:identity-verified| Identity-Verified]] | ||
| - | </WRAP> | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0024 ^ Provide transactions finalized and completed in real time | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0026 ^ Provide a bridge between legacy and new payment services | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0027 ^ Maintain the centrality of safe and trusted central bank money | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0037 ^ Support private-sector innovation | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0038 ^ Allow private-sector innovators to focus on: <WRAP> | ||
| - | - new access services | ||
| - | - distribution methods | ||
| - | - related service offerings | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0045 ^ Enable rapid and cost-effective payment of taxes | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0046 ^ Enable rapid and cost-effective delivery of:<WRAP> | ||
| - | - wages, | ||
| - | - tax refunds | ||
| - | - other federal payments | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0047 ^ Lower transaction costs | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ B0051 ^ Generate data about users’ financial transactions similar to the current Commercial Bank(( | ||
| - | Commercial banks include banks licensed either by federal or state banking agencies, credit unions, and thrifts from the **White Paper**. | ||
| - | )) and [[cbdc:private:cbdc_omg:8_append:20_glossary:nonbank_money]] | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ P0021 ^ The intermediaries would operate in an open market for CBDC services | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ P0023 ^ CBDC would need to be readily transferable between customers of different intermediaries | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ P0025 ^ CBDC intermediary would need to verify the identity of a person accessing CBDC | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ P0026 ^ CBDC transactions would need to be final and completed in real-time | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ P0028 ^ Require significant international coordination to address issues such as:<WRAP> | ||
| - | - common standards | ||
| - | - infrastructure, | ||
| - | - the types of intermediaries able to access any new infrastructure, | ||
| - | - legal frameworks | ||
| - | - preventing illicit transactions | ||
| - | - the cost and timing of implementation | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0001 ^ Risk of affecting financial-sector market structure | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0003 ^ Risk to the safety and stability of the financial system | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0007 ^ Risk CDBC is difficult to use without service providers | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0010 ^ CBDC has Risk of significant energy footprint similar to Cryptocurrencies | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0011 ^ Increased Risk to consumer's vulnerability to: <WRAP> | ||
| - | - loss | ||
| - | - theft | ||
| - | - fraud | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0014 ^ Risk of not achieving an appropriate balance between safeguarding the privacy rights of consumers and affording the transparency necessary to deter criminal activity | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0018 ^ Risk a CBDC could fundamentally change the structure of the U.S. financial system, altering the private sector and central bank:<WRAP> | ||
| - | - roles | ||
| - | - responsibilities | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0019 ^ Risk of reducing the aggregate amount of deposits in the banking system, which could in turn increase bank funding expenses, and reduce credit availability or raise credit costs for households and businesses.| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ R0020 ^ Risk that interest-bearing CBDC could result in a shift away from other low-risk assets, such as shares in money market mutual funds, Treasury bills, and other short-term instruments. | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ D0012 ^ Design should address privacy concerns by leveraging existing tools already in use by intermediaries | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ D0013 ^ Design should facilitate compliance with a robust set of rules already intended to combat <WRAP> | ||
| - | - money laundering | ||
| - | - the financing of terrorism | ||
| - | - customer due diligence | ||
| - | - record-keeping | ||
| - | - reporting requirements | ||
| - | </WRAP>| <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ D0014 ^ Design should involve private-sector partners with established programs to help ensure compliance with existing rules | <WRAP> | ||
| - | </WRAP>| | ||
| - | ^ D0015 ^ Design should include any dedicated infrastructure required to provide resilience to threats such as operational disruptions and cybersecurity risks | | ||
| - | </table> | ||
| + | For a list of discussion of the desirements, see [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start#discussion_of_examples| Dual Payment Networks - Discussion of Examples]] | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
cbdc/public/cbdc_omg/04_doc/20_comments/brp/q12/start.1650411372.txt.gz · Last modified: 2022/04/19 19:36 by nick
