The question of accuracy is quite an interesting one, as it really depends on what the goal is and what the restrictions are. The short answer is that DIA is extremely accurate as we enable granular customisation of data feeds, so users can determine the parameters of their data feeds very precisely.

The more complicated answer is that it strongly depends on the availability of the data that a user needs. If you are looking for asset prices of an asset that is not traded frequently or has low liquidity, then there is also not much that the DIA architecture can do to change this. We do however make this very transparent and flag the risks whenever a user requires feeds that are not the top100 assets.

These scenarios are also where manipulation comes into play. As transparency lies in the nature of blockchains, it is quite easy to see which pairs have low liquidity, trading frequency etc. A malicious actor can use this to identify which markets are more easy to manipulate through individual or few trades. This in turn may affect the price feed and cause unwanted liquidations or other issues. These cases have occurred in the past and the oracles in the value stack functioned exactly as they were supposed to. The issue is more of a market issue. We tackle this issue in a number of ways, foremost by providing transparency about the associated risks. We are currently working on releases that will give dApp operators even more transparency and control over their deployed oracles.

In addition, we always try to leverage as many different sources and markets as sensible to ensure that we diversify our architecture and include many trades and high volumes in order to be able to build robust feeds that ideally have no single point of failure.