dido:public:ra:1.1_intro:1_problem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.1_intro:1_problem [2020/05/31 00:04] char |
dido:public:ra:1.1_intro:1_problem [2022/06/07 16:35] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 1.1 Problem ====== | ====== 1.1 Problem ====== | ||
| - | [[dido:public:ra:1.1_intro|return to Introduction]] | + | [[dido:public:ra:1.1_intro:start|return to Introduction]] |
| - | As of June 12, 2018, there were 1,628 Cryptocurrencies available, with a total market cap around $300 Billion(( Coin Market Cap, "Cryptocurrency Market Capitalizations," 3 December 2017. [Online]. Available: https://coinmarketcap.com/all/views/all/. [Accessed 3 December 2017]. | + | As of March 2022, there were around 10,400 Cryptocurrencies available, with a total market cap of around $2 Trillion down from an all-time high of almost $3 Trillion in November od 2021(( |
| + | __Market capitalization of Bitcoin from April 2013 to July 28, 2021(in billion U.S. dollars)__, | ||
| + | Statista, | ||
| + | Accessed: 29 July 2021, | ||
| + | [[https://www.statista.com/statistics/377382/bitcoin-market-capitalization/]] | ||
| ))<sup>,</sup>((D. Palmer, "Market Cap Hits All-Time High," 23 August 2017. [Online]. Available: https://www.coindesk.com/150-billion-total-cryptocurrency-market-cap-hits-new-time-high/. [Accessed 20 November 2017]. | ))<sup>,</sup>((D. Palmer, "Market Cap Hits All-Time High," 23 August 2017. [Online]. Available: https://www.coindesk.com/150-billion-total-cryptocurrency-market-cap-hits-new-time-high/. [Accessed 20 November 2017]. | ||
| - | )). DIDO implementations and interest in them are currently in the technology Hype Cycle as defined by Gartner. | + | )). DIDO implementations and interest in them are currently in the Positive Hype part of the technology [[dido:public:ra:xapend:xapend.a_glossary:h:hype_cycle]] as defined by Gartner.((Understanding Gartner's Hype Cycles, |
| + | 30 May 2003, | ||
| + | Alexander Linden, Jackie Fenn, [[https://www.bus.umich.edu/KresgePublic/Journals/Gartner/research/115200/115274/115274.html]])). | ||
| - | **<todo @nick> Where in the cycle?</todo>** | ||
| <figure> | <figure> | ||
| - | {{ dido:public:ra.1.intro:figure_2.png?400 |}} | + | {{ :dido:public:ra:1.1_intro:screen_shot_2022-06-07_at_1.21.18_pm.png?500 |}} |
| - | <caption>Gartner Group Hype Cycle | + | <caption>Number of cryptocurrencies worldwide from 2013 to Feb 2022 [[https://www.statista.com/statistics/863917/number-crypto-coins-tokens/]]</caption> |
| - | </caption> | + | |
| </figure> | </figure> | ||
| - | **<todo @julie> 1st sentence 'motivating the RA' - attributes motivation to inanimate object. Can you reword? -- done -- check if you like </todo>** | + | <figure> |
| + | {{ :dido:public:ra:1.1_intro:screen_shot_2022-06-07_at_1.26.50_pm.png?500 |}} | ||
| + | <caption>Market capitalization of Cryptocurrenies from 2018 to 2022. (( | ||
| + | Matt Williams, | ||
| + | __Total Cryptocurrency Market cap back at $2 trillion, Bitcoin price may breakout__, | ||
| + | Business2Community, | ||
| + | 22 March 2022, | ||
| + | Accessed: 7 June 2022, | ||
| + | [[https://www.business2community.com/crypto-news/crypto-market-cap-recovers-to-2-trillion-02460846]] | ||
| + | ))</caption> | ||
| + | </figure> | ||
| - | **<todo @julie> 'it is unknown' in mid-paragraph - classic passive wording, can you fix? - my wording. agree that something like "we don't know" would be more active but not appropriate for a doc like this. so I think the way it is must remain. </todo>** | + | The naming of the Hypecurve is new, but the understanding of the hype curves has a long history. |
| - | A major concern motivating the need for a Reference Architecture (RA) is the lack of a comprehensive mechanism to evaluate all the risks associated with DIDO implementations (especially cryptocurrencies). Many of the risks to DIDOs are common to distributed computing and have already been identified and addressed using risk mitigators in existing processes, procedures, and standards. An example is vulnerabilities in source code. However, it is unknown how rigorously these risk mitigators have been applied to DIDOs, if at all. Specifying a Reference Architecture and cross-referencing its components to a set of existing standards establishes the following: | + | : //There is a famous story, we don’t know if it’s true, about how in the late summer of 1929, a shoe-shine boy gave Joe Kennedy stock tips, and Kennedy, being a wise old investor, thought, “If shoeshine boys are giving stock tips, then it’s time to get out of the market.” So the story says Joe Kennedy sold all of his stocks and made a killing...(( |
| + | Olivia B. Waxman, | ||
| + | Time, | ||
| + | 24 October 2019, | ||
| + | Accessed: 29 July 2021, | ||
| + | [[https://time.com/5707876/1929-wall-street-crash/]] | ||
| + | ))// | ||
| + | |||
| + | <figure> | ||
| + | {{ :dido:public:ra:1.1_intro:screen_shot_2021-06-14_at_7.51.16_am.png?700 |}} | ||
| + | {{ :dido:public:ra:1.1_intro:screen_shot_2021-06-14_at_7.51.03_am.png?700 |}} | ||
| + | <caption>Gartner Group Hype Cycle | ||
| + | </caption> | ||
| + | </figure> | ||
| + | |||
| + | A major concern and part of the motivation behind the creation of a Reference Architecture (RA) is the lack of a comprehensive mechanism to evaluate all the risks associated with DIDO implementations (especially cryptocurrencies). Many of the risks to DIDOs are common to distributed computing and have already been identified and addressed using risk mitigators in existing processes, procedures, and standards. An example is vulnerabilities in source code. Unfortunately, no statistics are available regarding how rigorously these risk mitigators are applied to DIDOs, if at all. Specifying a Reference Architecture and cross-referencing its components to a set of existing standards establishes the following: | ||
| * An actuarial framework for assessing risks associated with existing products | * An actuarial framework for assessing risks associated with existing products | ||
| * Metrics for evaluating, comparing, and selecting existing products | * Metrics for evaluating, comparing, and selecting existing products | ||
| * A roadmap for future standard implementation, enhancement, and development | * A roadmap for future standard implementation, enhancement, and development | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/1.1_intro/1_problem.1590897842.txt.gz · Last modified: 2020/05/31 00:04 by char
