cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets: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:15_common:70_dualnets:start [2022/05/16 18:11] nick ↷ Page moved from cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start to cbdc:cbdc_omg:04_doc:15_common:70_dualnets:start |
cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start [2022/06/17 18:20] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 4.7 Dual Payment Networks ====== | ====== 4.7 Dual Payment Networks ====== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:start| Return to Common Elements]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:15_common:start| Return to Common Elements]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | 4.7 Dual Payment Networks | ||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </WRAP> | | ||
| ===== Overview ===== | ===== Overview ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start | Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start| Return to Top]] |
| : **Note:** Also see: | : **Note:** Also see: | ||
| - | * [[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:15_common:48_natsec:start]] | + | * [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start]] |
| - | * [[cbdc:private:cbdc_omg:04_doc:15_common:50_international:start]] | + | * [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start]] |
| - | * Answer to [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q04:start]] | + | * Answer to [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q04:start]] |
| The simplest way to add a U.S. CBDC would be to build a parallel payment transaction network to the existing [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:ach | Automated Clearing House (ACH) Network]]. The existing payment network would continue to function //"as-is"//, while the new real-time U.S. CBDC Network would handle payment transactions using the U.S. CBDC (probably a Stablecoin). | The simplest way to add a U.S. CBDC would be to build a parallel payment transaction network to the existing [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:ach | Automated Clearing House (ACH) Network]]. The existing payment network would continue to function //"as-is"//, while the new real-time U.S. CBDC Network would handle payment transactions using the U.S. CBDC (probably a Stablecoin). | ||
| - | : **Note:** The ACH has embarked on its own support for real-time transactions with [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:r:rtp | Real-Time Payments (RTP) Network]]. This should not be confused with the Stablecoin or other Crypto solution. | + | : **Note:** The ACH has embarked on its own support for real-time transactions with [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:r:rtp | Real-Time Payments (RTP) Network]]. This should not be confused with the Stablecoin or other Crypto solutions. |
| - | Both networks 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 | National 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. | + | Both networks 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. |
| - | However, it would also be possible for new financial intermediaries to startup but they would only be allowed to use the U.S. CBDC payment network. These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:private:cbdc_omg:04_doc:15_common:48_natsec:start | National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:private:cbdc_omg:04_doc:15_common:50_international:start | International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. | + | However, it would also be possible for new financial intermediaries to startup but they would only be allowed to use the U.S. CBDC payment network. These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start| National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start| International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. |
| - | The new U.S. CBDC network handles the real-time transactions requirements of the U.S. CBDC. This requires the: | + | The new U.S. CBDC network handles the real-time transaction requirements of the U.S. CBDC. This requires the: |
| <table> | <table> | ||
| Line 32: | Line 39: | ||
| ==== The Dual ACH/CBDC Payment Networks ==== | ==== The Dual ACH/CBDC Payment Networks ==== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start | Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start| Return to Top]] |
| 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 {{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. | ||
| Line 38: | Line 45: | ||
| <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> | ||
| Line 98: | Line 105: | ||
| ==== Only the CBDC Payment Network ==== | ==== Only the CBDC Payment Network ==== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start | Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets:start| Return to Top]] |
| Allowing new or existing Payment Networks to only use the new U.S. CBDC Payment Network is possible. See Figure {{ref>newOnlyPaymentNet}}. This allows for new and creative ways of having payment transactions. In this scenario, the new Intermediary would use the same new [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interface (API)]] as in the Dual situation, but in this scenario, all the transactions would need to be in U.S. CBDC. This means that any U.S. Dollars would have to be exchanged for U.S. CBDC before the transactions can take place. However, the New Intermediaries might allow accounts to contain U.S. CBDC. In this case, there would be no conversion required. | Allowing new or existing Payment Networks to only use the new U.S. CBDC Payment Network is possible. See Figure {{ref>newOnlyPaymentNet}}. This allows for new and creative ways of having payment transactions. In this scenario, the new Intermediary would use the same new [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interface (API)]] as in the Dual situation, but in this scenario, all the transactions would need to be in U.S. CBDC. This means that any U.S. Dollars would have to be exchanged for U.S. CBDC before the transactions can take place. However, the New Intermediaries might allow accounts to contain U.S. CBDC. In this case, there would be no conversion required. | ||
| Line 104: | Line 111: | ||
| The same situation occurs on the other end of the payment transaction. The recipient could level all or some of the transactions as U.S. Dollars or U.S. CBDC. | The same situation occurs on the other end of the payment transaction. The recipient could level all or some of the transactions as U.S. Dollars or U.S. CBDC. | ||
| - | : **NOTE:** These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:private:cbdc_omg:04_doc:15_common:48_natsec:start | National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:private:cbdc_omg:04_doc:15_common:50_international:start | International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. | + | : **NOTE:** These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start| National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start| International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. |
| <figure newOnlyPaymentNet> | <figure newOnlyPaymentNet> | ||
| - | {{ :cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:screen_shot_2022-04-20_at_10.32.48_am.png?700 |}} | + | {{ cbdc:04_doc:15_common:70_dualnets:screen_shot_2022-04-20_at_10.32.48_am.png?700 |}} |
| <caption>Theoretical Very Simplified single CBDC Network Concept.</caption> | <caption>Theoretical Very Simplified single CBDC Network Concept.</caption> | ||
| </figure> | </figure> | ||
| ===== Examples ===== | ===== Examples ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start | Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets: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}}. | + | 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 **Privacy Issues** are listed in Table {{ref>privacyReq}}. |
| <table privacyReq> | <table privacyReq> | ||
| - | <caption>Examples of **Privacy Desirements** identified during the White Paper Analysis conducted by the OMG</caption> | + | <caption>Examples of **Privacy Desirements** identified during the White Paper Analysis conducted by the OMG's CBDC WG</caption> |
| |< 100% 20% ->| | |< 100% 20% ->| | ||
| ^ Category ^ Desirements ^ | ^ Category ^ Desirements ^ | ||
| Line 128: | Line 135: | ||
| : **Note:** **''B''** = Benefit, **''P''** = Policy, **''R''** = Requirement, **''D''** = Design. | : **Note:** **''B''** = Benefit, **''P''** = Policy, **''R''** = Requirement, **''D''** = Design. | ||
| ===== Discussion of Examples ===== | ===== Discussion of Examples ===== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:start | Return to Top]] | + | [[cbdc:public:cbdc_omg:04_doc:15_common:70_dualnets: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 {{ref>privacyReqDiscussion}} 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]]. |
| <table privacyReqDiscussion> | <table privacyReqDiscussion> | ||
| Line 174: | Line 181: | ||
| </WRAP>| | </WRAP>| | ||
| ^ B0022 ^ Provide a CBDC that is:<WRAP> | ^ B0022 ^ Provide a CBDC that is:<WRAP> | ||
| - | : 1. [[cbdc:private:cbdc_omg:8_append:20_glossary:privacy-protected| Privacy-Protected ]] | + | : 1. [[cbdc:public:cbdc_omg:8_append:20_glossary:privacy-protected| Privacy-Protected ]] |
| - | : 2. [[cbdc:private:cbdc_omg:8_append:20_glossary:intermediated| Intermediated]] | + | : 2. [[cbdc:public:cbdc_omg:8_append:20_glossary:intermediated| Intermediated]] |
| - | : 3. [[cbdc:private:cbdc_omg:8_append:20_glossary:transferable| Widely Transferable]] | + | : 3. [[cbdc:public:cbdc_omg:8_append:20_glossary:transferable| Widely Transferable]] |
| - | : 4. [[cbdc:private:cbdc_omg:8_append:20_glossary:identity-verified| Identity-Verified]] | + | : 4. [[cbdc:public:cbdc_omg:8_append:20_glossary:identity-verified| Identity-Verified]] |
| </WRAP> | <WRAP> | </WRAP> | <WRAP> | ||
| Using the Dual Network Model for payment transfers should fulfill all these desirements. | Using the Dual Network Model for payment transfers should fulfill all these desirements. | ||
| - | : **NOTE:** These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:private:cbdc_omg:04_doc:15_common:48_natsec:start | National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:private:cbdc_omg:04_doc:15_common:50_international:start | International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. | + | : **NOTE:** These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start| National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start| International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. |
| </WRAP>| | </WRAP>| | ||
| Line 216: | Line 223: | ||
| </WRAP>| | </WRAP>| | ||
| ^ B0047 ^ Lower transaction costs | <WRAP> | ^ B0047 ^ Lower transaction costs | <WRAP> | ||
| - | At this point in time, it can only be conjectured that the transaction costs would be less. Often it is assumed that the [[cbdc:private:cbdc_omg:04_doc:15_common:45_privacy:start | Privacy]] and [[cbdc:private:cbdc_omg:04_doc:15_common:48_natsec:start | Security]] laws and regulations can be skipped when using a U.S. CBDC. This will most likely not happen. If the U.S. CBDC uses a Stablecoin, the cost is highly dependent on the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:p:platform | Platform]] chosen. See: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.k_consensus:start | Consensus Algorithms]] | + | At this point in time, it can only be conjectured that the transaction costs would be less. Often it is assumed that the [[cbdc:public:cbdc_omg:04_doc:15_common:45_privacy:start| Privacy]] and [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start| Security]] laws and regulations can be skipped when using a U.S. CBDC. This will most likely not happen. If the U.S. CBDC uses a Stablecoin, the cost is highly dependent on the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:p:platform | Platform]] chosen. See: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.k_consensus:start | Consensus Algorithms]] |
| </WRAP>| | </WRAP>| | ||
| ^ B0051 ^ Generate data about users’ financial transactions similar to the current Commercial Bank(( | ^ 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**. | 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> | + | )) and [[cbdc:public:cbdc_omg:8_append:20_glossary:nonbank_money]] | <WRAP> |
| The Dual ACH/CBDC network model would require all Intermediaries to collect the same kind of data on all transactions providing one degree of freedom between the End Users and the Government. | The Dual ACH/CBDC network model would require all Intermediaries to collect the same kind of data on all transactions providing one degree of freedom between the End Users and the Government. | ||
| </WRAP>| | </WRAP>| | ||
| Line 270: | Line 277: | ||
| Assuming that the current balance is acceptable, using the Dual Network Model for payment transfers would keep in place all existing Privacy and Security Laws and Regulations. The new Intermediaries would have to follow the same rules as the existing Intermediaries. | Assuming that the current balance is acceptable, using the Dual Network Model for payment transfers would keep in place all existing Privacy and Security Laws and Regulations. The new Intermediaries would have to follow the same rules as the existing Intermediaries. | ||
| - | : **NOTE:** These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:private:cbdc_omg:04_doc:15_common:48_natsec:start | National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:private:cbdc_omg:04_doc:15_common:50_international:start | International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. | + | : **NOTE:** These new financial intermediaries would **NOT** be released from following the existing Laws and Regulations of the traditional financial intermediaries. In other words, they would have to ensure the End User's privacy (both ends of the Payment Transactions. They would also have conform to all the [[cbdc:public:cbdc_omg:04_doc:15_common:48_natsec:start| National Security Laws and Regulations]]. If either End User in the Payment Transaction is not in the U.S., they would have to abide by all the [[cbdc:public:cbdc_omg:04_doc:15_common:50_international:start| International Laws and Regulations]]. This would mean these new Intermediaries would be subject to oversight and auditing. |
| </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> | ^ R0018 ^ Risk a CBDC could fundamentally change the structure of the U.S. financial system, altering the private sector and central bank:<WRAP> | ||
| Line 279: | Line 286: | ||
| </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> | ^ 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> | ||
| - | In the Dual ACH/CBDC Network model, U.S. Dollars in accounts or U.S. CBDC would still be treated as transfers. See the answer to [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q13:start]]. | + | In the Dual ACH/CBDC Network model, U.S. Dollars in accounts or U.S. CBDC would still be treated as transfers. See the answer to [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q13:start]]. |
| </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> | ^ 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> | ||
| Line 306: | Line 313: | ||
| 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#benefit_considerations| 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#risk_considerations| 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_considerations | Design Considerations]] ||| |
| </table> | </table> | ||
| <figure typesOfNodes> | <figure typesOfNodes> | ||
| - | {{ :cbdc:private:cbdc_omg:04_doc:15_common:70_dualnets:node_taxonomy.png?500 |}} | + | {{ cbdc:04_doc:15_common:70_dualnets:node_taxonomy.png?500 |}} |
| <caption> DIDO Node Taxonomy: Node Types </caption> | <caption> DIDO Node Taxonomy: Node Types </caption> | ||
| </figure> | </figure> | ||
| - | |||
| - | |||
| - | |||
| - | |||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
cbdc/public/cbdc_omg/04_doc/15_common/70_dualnets/start.1652739069.txt.gz · Last modified: 2022/05/16 18:11 by nick
