cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q20: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:dsn:q20:start [2022/05/16 18:11] nick ↷ Page moved from cbdc:private:cbdc_omg:04_doc:20_comments:dsn:q20:start to cbdc:cbdc_omg:04_doc:20_comments:dsn:q20:start |
cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q20:start [2022/06/17 19:29] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Question: 20. How could a CBDC be designed to achieve transferability across multiple payment platforms? Would new technology or technical standards be needed? ====== | ====== Question: 20. How could a CBDC be designed to achieve transferability across multiple payment platforms? Would new technology or technical standards be needed? ====== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:dsn:start| Return to CBDC Benefits, Risks, and Policy Considerations ]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:20_comments:dsn:start| Return to Design Considerations ]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | Question: 20. How could a CBDC be designed to achieve transferability across multiple payment platforms? Would new technology or technical standards be needed? | ||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </WRAP> | | ||
| ===== Question ===== | ===== Question ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] |
| * **How could a CBDC be designed to achieve transferability across multiple payment platforms?** | * **How could a CBDC be designed to achieve transferability across multiple payment platforms?** | ||
| Line 10: | Line 17: | ||
| ===== Answer ===== | ===== Answer ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] |
| - | By using a system designed roughly as outlined in section [[cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start]], much of the current infrastructure would remain in place and to **achieve transferability across multiple payment platforms** would be very little different than the current system. | + | By using a system designed roughly as outlined in section [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start]], much of the current infrastructure would remain in place and to **achieve transferability across multiple payment platforms** would be very little different than the current system. |
| Table {{ref>theoretComponents}} provides the system components of a very simplified, theoretic ACH / CBDC network. Figure {{ref>simpleCbdcFlow}} graphically shows a theoretical, very simplified, dual ACH-CBDC Network Concept. A newly developed Application Programming Interface (API) and a specialized bridge going between the existing ACH Network and the new U.S. CBDC network would allow the existing platforms to work fairly seamlessly. | Table {{ref>theoretComponents}} provides the system components of a very simplified, theoretic ACH / CBDC network. Figure {{ref>simpleCbdcFlow}} graphically shows a theoretical, very simplified, dual ACH-CBDC Network Concept. A newly developed Application Programming Interface (API) and a specialized bridge going between the existing ACH Network and the new U.S. CBDC network would allow the existing platforms to work fairly seamlessly. | ||
| Line 31: | Line 38: | ||
| <figure simpleCbdcFlow> | <figure simpleCbdcFlow> | ||
| - | {{ :cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:screen_shot_2022-04-20_at_2.53.28_pm.png?700 |}} | + | {{ cbdc:04_doc:15_common:70_dualnets:screen_shot_2022-04-20_at_2.53.28_pm.png?700 |}} |
| <caption>Theoretical Very Simplified Dual ACH-CBDC Network Concept.</caption> | <caption>Theoretical Very Simplified Dual ACH-CBDC Network Concept.</caption> | ||
| </figure> | </figure> | ||
| ===== Examples ===== | ===== Examples ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q20: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 **achieving transferability across multiple payment platforms** are listed in Table {{ref>transReq}}. | + | The "desirements" specified in [[https://www.federalreserve.gov/publications/files/money-and-payments-20220120.pdf | White Paper]] and identified by the [[cbdc:public:cbdc_omg:04_doc:12_summary:start | OMG's CBDC WG White Paper Analysis]] as **achieving transferability across multiple payment platforms** are listed in Table {{ref>transReq}}. |
| <table transReq> | <table transReq> | ||
| - | <caption>Examples of **achieving transferability across multiple payment platforms** identified during the White Paper Analysis conducted by the OMG</caption> | + | <caption>Examples of **achieving transferability across multiple payment platforms** identified during the White Paper Analysis conducted by the OMG's CBDC WG.</caption> |
| |< 100% 20% ->| | |< 100% 20% ->| | ||
| ^ Category ^ Desirements ^ | ^ Category ^ Desirements ^ | ||
| Line 53: | Line 60: | ||
| ===== Discussion of Examples ===== | ===== Discussion of Examples ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q20:start| Return to Top]] |
| - | Table {{ref>ezOfUse}} 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]] which apply to **achieving transferability across multiple payment platforms**. | + | Table {{ref>ezOfUse}} provides discussion points for each of the "desirements" identified by the [[cbdc:public:cbdc_omg:04_doc:12_summary:start | OMG's CBDC WG White Paper Analysis]] which apply to **achieving transferability across multiple payment platforms**. |
| <table ezOfUse> | <table ezOfUse> | ||
| Line 89: | Line 96: | ||
| The Dual ACH/CBDC Networks would require the new infrastructure for the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programmer Interface (API)]], the bridges, and the building out of a Distributed Network of Nodes to handle the CBDC transactions and [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.k_consensus:start | Consensus]]. The network of nodes might have any number of node types. Figure {{ref>typesOfNodes}} describes the taxonomy of DIDO Node Types. See [[ https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:1.2_views:3_taxonomic:3_node_tax:start | OMG DID-RA Node Taxonomy]] for a discussion on the different kinds of nodes. | The Dual ACH/CBDC Networks would require the new infrastructure for the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programmer Interface (API)]], the bridges, and the building out of a Distributed Network of Nodes to handle the CBDC transactions and [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.k_consensus:start | Consensus]]. The network of nodes might have any number of node types. Figure {{ref>typesOfNodes}} describes the taxonomy of DIDO Node Types. See [[ https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:1.2_views:3_taxonomic:3_node_tax:start | OMG DID-RA Node Taxonomy]] for a discussion on the different kinds of nodes. | ||
| </WRAP>| | </WRAP>| | ||
| - | | **''B''** = [[cbdc:private:cbdc_omg:04_doc:12_summary:start#benefits| Benefit Considerations ]] ||| | + | | **''B''** = [[cbdc:public:cbdc_omg:04_doc:12_summary:start#benefits| Benefit Considerations ]] ||| |
| - | | **''P''** = [[cbdc:private:cbdc_omg:04_doc:12_summary:start#policy_considerations| Policy Considerations]] ||| | + | | **''P''** = [[cbdc:public:cbdc_omg:04_doc:12_summary:start#policy_considerations| Policy Considerations]] ||| |
| - | | **''R''** = [[cbdc:private:cbdc_omg:04_doc:12_summary:start#risks| Risk Considerations ]] ||| | + | | **''R''** = [[cbdc:public:cbdc_omg:04_doc:12_summary:start#risks| Risk Considerations ]] ||| |
| - | | **''D''** = [[cbdc:private:cbdc_omg:04_doc:12_summary:start#design| Design Considerations]] ||| | + | | **''D''** = [[cbdc:public:cbdc_omg:04_doc:12_summary:start#design| Design Considerations]] ||| |
| </table> | </table> | ||
cbdc/public/cbdc_omg/04_doc/20_comments/dsn/q20/start.1652739073.txt.gz · Last modified: 2022/05/16 18:11 by nick
