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 17:06] 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]] |
| - | See the answers to the section [[cbdc:private:cbdc_omg:04_doc:15_common:45_privacy:start]] and to the answer to [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q04:start]]. | + | : **Note:** See the answers to the sections: |
| + | * [[cbdc:public:cbdc_omg:04_doc:15_common:45_privacy: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 ACH Network. | + | 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 parallel transaction network to the ACH Network handling 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. | + | ===== Examples ===== |
| - | * Use of an energy-efficient Consensus Algorithm | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] |
| - | * Development of a bridge between the existing ACH Network and the new U.S. CBDC Network | + | |
| - | * Development of a new standardized 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. | + | For a list of desirements, see [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start#examples| Dual Payment Networks - Examples]] |
| - | <figure simpleCbdcFlow> | + | ===== Discussion of Examples ===== |
| - | {{ :cbdc:private:cbdc_omg:04_doc:20_comments:brp:q12:screen_shot_2022-04-19_at_12.58.12_pm.png?700 |}} | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q12:start| Return to Top]] |
| - | <caption>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 dual ACH/CBDC network.</caption> | + | 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]] |
| - | </table> | + | |
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
cbdc/public/cbdc_omg/04_doc/20_comments/brp/q12/start.1650402399.txt.gz · Last modified: 2022/04/19 17:06 by nick
