From b58f923d2a8bd6037be7bb0302df6dd9c39245ed Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:12 +0100 Subject: [PATCH 1/9] Fix typos in documentation/index.md --- documentation/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/index.md b/documentation/index.md index 39d49e202..a42382167 100644 --- a/documentation/index.md +++ b/documentation/index.md @@ -56,7 +56,7 @@ Here you can find the introduction to the structure of the system and first step ## DIA Technical Structure -DIA is setup as a hybrid system with off-chain components for storing and proceccing large amounts of data and on-chain components providing data sources for financial smart contracts. Currently, Ethereum is used as smart contract plaform because of its widespread use and technical quality, but the DIA system is not limited to one blockchain technology. +DIA is setup as a hybrid system with off-chain components for storing and proceccing large amounts of data and on-chain components providing data sources for financial smart contracts. Currently, Ethereum is used as smart contract platform because of its widespread use and technical quality, but the DIA system is not limited to one blockchain technology. ### Centralized Backend From 1419e24263f96f317276c1c2ecbecd6a07c76a61 Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:14 +0100 Subject: [PATCH 2/9] Fix typos in documentation/api-1.md --- documentation/api-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/api-1.md b/documentation/api-1.md index b8b437c1a..c2fd1100f 100644 --- a/documentation/api-1.md +++ b/documentation/api-1.md @@ -99,7 +99,7 @@ _Remark:_ Careful! Successful responses can be rather large. Get value for a certain rate type. Example: [https://api.diadata.org/v1/interestrate/ESTER/2020-04-20](https://api.diadata.org/v1/interestrate/ESTER/2020-04-20) -Get rate values for a range of timestamps using optinal query parameters. +Get rate values for a range of timestamps using optional query parameters. Example: [https://api.diadata.org/v1/interestrate/ESTER?dateInit=2020-02-20&dateFinal=2020-04-16](https://api.diadata.org/v1/interestrate/ESTER?dateInit=2020-02-20&dateFinal=2020-04-16) Path Params: From a2e8d7eb96844ae0ff3992866cb26ea342505b4c Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:16 +0100 Subject: [PATCH 3/9] Fix typos in documentation/oracle-documentation/solana-oracle.md --- documentation/oracle-documentation/solana-oracle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/oracle-documentation/solana-oracle.md b/documentation/oracle-documentation/solana-oracle.md index 0b44c2b9f..c95280d1c 100644 --- a/documentation/oracle-documentation/solana-oracle.md +++ b/documentation/oracle-documentation/solana-oracle.md @@ -31,7 +31,7 @@ The workflow presented below represents the configuration of the DIA Solana Orac ### DIA Data Feeder -The feeder gets symbol price informaton available from DIA. +The feeder gets symbol price information available from DIA. 1. The feeder calls the API https://api.diadata.org/v1/quotation/\_symbol\_ with each asset obtained from the configured asset list. 2. For each symbol that the feeder calls to quote, it verifies that the data has been received correctly. If for some reason, the feeder does not obtain the data or the data is incorrect, it continues with the next symbol, and so on, until it ends with all the configured asset symbols. From da3b2db212bb215eac9b815b7576d2475a4753ee Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:21 +0100 Subject: [PATCH 4/9] Fix typos in documentation/oracle-documentation/randomness-oracle.md --- documentation/oracle-documentation/randomness-oracle.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/oracle-documentation/randomness-oracle.md b/documentation/oracle-documentation/randomness-oracle.md index cf64dbcbc..d63945ba5 100644 --- a/documentation/oracle-documentation/randomness-oracle.md +++ b/documentation/oracle-documentation/randomness-oracle.md @@ -91,7 +91,7 @@ contract DIARandomOracle { } ``` -Users can call `getLastRound()`to obtain the ID of the latest published round. To obtain the randomness of a certain round, users can call `getRandomValueFromRound(uint256 _round)`using the obtaines round ID. +Users can call `getLastRound()`to obtain the ID of the latest published round. To obtain the randomness of a certain round, users can call `getRandomValueFromRound(uint256 _round)`using the obtains round ID. The signature can also be requested by calling `getRandomValueFromRoundWithSignature(uint256 _round)`. @@ -190,4 +190,4 @@ Additionally, there are new risks introduced by using the oracle. | -------------------------------------- | ------------------------------------------------------------------------------------------------- | | Oracle stops serving data | Check that the oracle has recent updates in its history. | | Specific Round is missed by the oracle | Have your dApp use the next round if a certain round is unavailable (but later ones exist). | -| Oracle serves compromised data | Check the associated BLS signature provided by drand (Note: Currently not availabe on most EVMs). | +| Oracle serves compromised data | Check the associated BLS signature provided by drand (Note: Currently not available on most EVMs). | From 1dc2d086ce570e08f46dc3d8472aba322273fa99 Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:23 +0100 Subject: [PATCH 5/9] Fix typos in documentation/methodology/supplynumbers.md --- documentation/methodology/supplynumbers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/methodology/supplynumbers.md b/documentation/methodology/supplynumbers.md index dea67cbed..67c9d7785 100644 --- a/documentation/methodology/supplynumbers.md +++ b/documentation/methodology/supplynumbers.md @@ -25,7 +25,7 @@ For each coin we measure, we have different methodology to determine the circula | Ethereum Classic | [https://api.diadata.org/v1/supply/ETC](https://api.diadata.org/v1/supply/ETC) | The circulating supply of Ethereum is calculated exactly like in case of Ethereum. | Capped increase | | Litecoin | [https://api.diadata.org/v1/supply/LTC](https://api.diadata.org/v1/supply/LTC) | Litecoin is very similar to Bitcoin. One of the major differences is that the time between two blocks is 2.5 minutes instead of 10 in Bitcoin. To have a coin mining reward schedule similar to Bitcoin, the halving period was set to 840,000, i.e., four times the amount of Bitcoin. DIA runs a full Litecoin node to monitor the blockchain and determine the amount of currently available LTC by this formula: ![Image of Litecoin reward formula](https://latex.codecogs.com/png.latex?\large&space;s=\sum_{n=0}^{b}{\frac{50}{2^{\lfloor\frac{n}{840000}\rfloor}}}). | Capped increase | | Maker | [https://api.diadata.org/v1/supply/MKR](https://api.diadata.org/v1/supply/MKR) | Maker has a total supply of 1M tokens, around 27% are locked in in development fund \(0x7bb0b08587b8a6b8945e09f1baca426558b0f06a\). None of the coins were burned yet - they are kept at the address \(0x69076e44a9c70a67d5b79d95795aba299083c275\) | Fixed | -| Monero | [https://api.diadata.org/v1/supply/XMR](https://api.diadata.org/v1/supply/XMR) | Monero is mined over inifinite time. To determine the circulating supply, we run an instance of a Monero node and query this node periodically. In its internal RPC API, the function [get\_coinbase\_tx\_sum](https://getmonero.org/resources/developer-guides/daemon-rpc.html#get_coinbase_tx_sum) is used to retrieve the amount of mined coins. | Unlimited | +| Monero | [https://api.diadata.org/v1/supply/XMR](https://api.diadata.org/v1/supply/XMR) | Monero is mined over infinite time. To determine the circulating supply, we run an instance of a Monero node and query this node periodically. In its internal RPC API, the function [get\_coinbase\_tx\_sum](https://getmonero.org/resources/developer-guides/daemon-rpc.html#get_coinbase_tx_sum) is used to retrieve the amount of mined coins. | Unlimited | | NEM | [https://api.diadata.org/v1/supply/XEM](https://api.diadata.org/v1/supply/XEM) | NEM has a fixed circulating supply of 8,999,999,999 coins, that were created in the genesis event. | Fixed | | NEO | [https://api.diadata.org/v1/supply/NEO](https://api.diadata.org/v1/supply/NEO) | The circulating supply of NEO is determined by running a NEO node and monitoring the blockchain. Initially, there were 100,000,000 NEOs created. The NEO team has distributed 50,000,000 to its investors. The distribution of the remaining NEOs will happen over time. In order to determine how many are still locked by the developers, we watch their address [`AQVh2pG732YvtNaxEGkQUei3YA4cvo7d2i`](https://neotracker.io/address/AQVh2pG732YvtNaxEGkQUei3YA4cvo7d2i) and subtract the amount this address holds from the initial volume. | Capped release | | OmiseGo | [https://api.diadata.org/v1/supply/OMS](https://api.diadata.org/v1/supply/OMS) | Circulating supply is total supply, structure of issuing tokens: Sale \(65.1% of OMG issued\), Airdrop \(5% of OMG issued\) Private: OmiseGO reserve \(20% of OMG issued\), Team \(9.9% of OMG issued\), Other approach would be taking out what is locked [omise go reserve and team](https://etherscan.io/token/0xd26114cd6EE289AccF82350c8d8487fedB8A0C07#balances) for one year - although te wallets dont have same amount of [tokens as stated in whitepaper](https://cdn.omise.co/omg/officialguide.pdf) | Fixed | From fe866751d5f6ae2daf15b46573b452e310bb7fc3 Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:24 +0100 Subject: [PATCH 6/9] Fix typos in documentation/methodology/overnight-rates.md --- documentation/methodology/overnight-rates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/methodology/overnight-rates.md b/documentation/methodology/overnight-rates.md index 217d189ec..12c588407 100644 --- a/documentation/methodology/overnight-rates.md +++ b/documentation/methodology/overnight-rates.md @@ -62,7 +62,7 @@ Sources: [https://en.wikipedia.org/wiki/%E2%82%ACSTR](https://en.wikipedia.org/wiki/%E2%82%ACSTR) **Remark:** -In the DIA API we use the former abbreviation ESTER in order to avoid the special symbol €. Hence, an examplary API call looks like: +In the DIA API we use the former abbreviation ESTER in order to avoid the special symbol €. Hence, an exemplary API call looks like: [https://api.diadata.org/v1/interestrate/ESTER/2020-04-16](https://api.diadata.org/v1/interestrate/ESTER/2020-04-16) ## From 382d5e1af12e5127d9c6d3fa88be4f275d7c7d8f Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:26 +0100 Subject: [PATCH 7/9] Fix typos in documentation/methodology/traditional-assets/overnight-rates.md --- documentation/methodology/traditional-assets/overnight-rates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/methodology/traditional-assets/overnight-rates.md b/documentation/methodology/traditional-assets/overnight-rates.md index 5c5184797..f12df2bb6 100644 --- a/documentation/methodology/traditional-assets/overnight-rates.md +++ b/documentation/methodology/traditional-assets/overnight-rates.md @@ -71,7 +71,7 @@ Sources: [https://en.wikipedia.org/wiki/%E2%82%ACSTR](https://en.wikipedia.org/wiki/%E2%82%ACSTR) **Remark:** -In the DIA API we use the former abbreviation ESTER in order to avoid the special symbol €. Hence, an examplary API call looks like: +In the DIA API we use the former abbreviation ESTER in order to avoid the special symbol €. Hence, an exemplary API call looks like: [https://api.diadata.org/v1/interestrate/ESTER/2020-04-16](https://api.diadata.org/v1/interestrate/ESTER/2020-04-16) ## From 0c58eda99084bfb1c49a52ce326b35108963f37a Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:27 +0100 Subject: [PATCH 8/9] Fix typos in documentation/methodology/digital-assets/supplynumbers.md --- documentation/methodology/digital-assets/supplynumbers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/methodology/digital-assets/supplynumbers.md b/documentation/methodology/digital-assets/supplynumbers.md index 18ba15533..0e8807291 100644 --- a/documentation/methodology/digital-assets/supplynumbers.md +++ b/documentation/methodology/digital-assets/supplynumbers.md @@ -22,7 +22,7 @@ The corresponding Oracle for all below coins can be found [here](https://docs.di | Ethereum Classic | [https://api.diadata.org/v1/supply/ETC](https://api.diadata.org/v1/supply/ETC) | The circulating supply of Ethereum is calculated exactly like in case of Ethereum. | Capped increase | | Litecoin | [https://api.diadata.org/v1/supply/LTC](https://api.diadata.org/v1/supply/LTC) | Litecoin is very similar to Bitcoin. One of the major differences is that the time between two blocks is 2.5 minutes instead of 10 in Bitcoin. To have a coin mining reward schedule similar to Bitcoin, the halving period was set to 840,000, i.e., four times the amount of Bitcoin. DIA runs a full Litecoin node to monitor the blockchain and determine the amount of currently available LTC by this formula: ![Image of Litecoin reward formula](https://latex.codecogs.com/png.latex?\large&space;s=\sum_{n=0}^{b}{\frac{50}{2^{\lfloor\frac{n}{840000}\rfloor}}}). | Capped increase | | Maker | [https://api.diadata.org/v1/supply/MKR](https://api.diadata.org/v1/supply/MKR) | Maker has a total supply of 1M tokens, around 27% are locked in in development fund \(0x7bb0b08587b8a6b8945e09f1baca426558b0f06a\). None of the coins were burned yet - they are kept at the address \(0x69076e44a9c70a67d5b79d95795aba299083c275\) | Fixed | -| Monero | [https://api.diadata.org/v1/supply/XMR](https://api.diadata.org/v1/supply/XMR) | Monero is mined over inifinite time. To determine the circulating supply, we run an instance of a Monero node and query this node periodically. In its internal RPC API, the function [get\_coinbase\_tx\_sum](https://getmonero.org/resources/developer-guides/daemon-rpc.html#get_coinbase_tx_sum) is used to retrieve the amount of mined coins. | Unlimited | +| Monero | [https://api.diadata.org/v1/supply/XMR](https://api.diadata.org/v1/supply/XMR) | Monero is mined over infinite time. To determine the circulating supply, we run an instance of a Monero node and query this node periodically. In its internal RPC API, the function [get\_coinbase\_tx\_sum](https://getmonero.org/resources/developer-guides/daemon-rpc.html#get_coinbase_tx_sum) is used to retrieve the amount of mined coins. | Unlimited | | NEM | [https://api.diadata.org/v1/supply/XEM](https://api.diadata.org/v1/supply/XEM) | NEM has a fixed circulating supply of 8,999,999,999 coins, that were created in the genesis event. | Fixed | | NEO | [https://api.diadata.org/v1/supply/NEO](https://api.diadata.org/v1/supply/NEO) | The circulating supply of NEO is determined by running a NEO node and monitoring the blockchain. Initially, there were 100,000,000 NEOs created. The NEO team has distributed 50,000,000 to its investors. The distribution of the remaining NEOs will happen over time. In order to determine how many are still locked by the developers, we watch their address [`AQVh2pG732YvtNaxEGkQUei3YA4cvo7d2i`](https://neotracker.io/address/AQVh2pG732YvtNaxEGkQUei3YA4cvo7d2i) and subtract the amount this address holds from the initial volume. | Capped release | | OmiseGo | [https://api.diadata.org/v1/supply/OMS](https://api.diadata.org/v1/supply/OMS) | Circulating supply is total supply, structure of issuing tokens: Sale \(65.1% of OMG issued\), Airdrop \(5% of OMG issued\) Private: OmiseGO reserve \(20% of OMG issued\), Team \(9.9% of OMG issued\), Other approach would be taking out what is locked [omise go reserve and team](https://etherscan.io/token/0xd26114cd6EE289AccF82350c8d8487fedB8A0C07#balances) for one year - although te wallets dont have same amount of [tokens as stated in whitepaper](https://cdn.omise.co/omg/officialguide.pdf) | Fixed | From b6c01559e02469e24faa42b7f753479a6bd4c5db Mon Sep 17 00:00:00 2001 From: Naum Date: Thu, 20 Feb 2025 21:28:29 +0100 Subject: [PATCH 9/9] Fix typos in documentation/methodology/digital-assets/exchangeprices/README.md --- .../methodology/digital-assets/exchangeprices/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/methodology/digital-assets/exchangeprices/README.md b/documentation/methodology/digital-assets/exchangeprices/README.md index c445aabbd..71aa3e9b9 100644 --- a/documentation/methodology/digital-assets/exchangeprices/README.md +++ b/documentation/methodology/digital-assets/exchangeprices/README.md @@ -14,7 +14,7 @@ Thus, conversion between assets from incompatible blockchains is restricted to c ## Price Determination -The vast majority of recorded trades by DIA are between two crypto assets. Only a minority of trades against fiat currencies is recorded on CEXes. Nontheless, DIA reports all asset prices in USD, even for numerous assets where only crypto-crypto pairs exist. +The vast majority of recorded trades by DIA are between two crypto assets. Only a minority of trades against fiat currencies is recorded on CEXes. Nonetheless, DIA reports all asset prices in USD, even for numerous assets where only crypto-crypto pairs exist. To retrieve a USD price for each and every asset, DIA uses a _price estimator._ The price estimator is updated with every recorded trade. Each trade consists of a _base token_ and a _quote token_. The price of a quote token is measured in base tokens. Because the order in a trade of base token and quote token is arbitrary, USD is always considered as base token. Other fiat currencies are also always base tokens, except when measuring the [ECB exchange rates](../../traditional-assets/ecb-foriegn-exchange-data.md). An asset needs to be a quote token in at least one market for us to be able to determine a USD price.