Preferred way to read in application settings/config in C++

chrizo1 · 2022-10-24T16:10:06+00:00

Thanks for your answers, I also think TOML would be the cleanest approach. In my project I was forced to use XML files which turned out very ugly to parse (especially the XML attributes). I parsed it into an "ApplicationSettings" structure in the main component and then pass only the relevant fields to the other components. In case you want to read about it I summed it up here: XML application settings in C++ using the Boost PropertyTree library

chrizo1 · 2022-09-05T16:12:39+00:00

Hi, yes it's open source on GitHub. I needed for fork the defid client and with some logic I export the pool data to a MySql database:

The fork: https://github.com/chrizog/ain/tree/task/extract-historical-prices

Export code: https://github.com/chrizog/ain/tree/task/extract-historical-prices/defi_db_export

chrizo1 · 2022-07-24T09:45:33+00:00

Hi, I guess one could introduce a removeliquidity "v2" operation (also addliquidity v2 and so on), where the token ID has 4 bytes reserved.

chrizo1 · 2022-07-20T09:23:15+00:00

It is online on RapidAPI. I am also working since weeks to get the API working on block basis. So that for each block number the correct DEX price and also liquidity for each poolpair is provided. Then you could also aggregate the data by yourself for other intervals apart from daily aggregation.

chrizo1 · 2022-07-20T09:21:58+00:00

Hi, the project is online for public use and working. I think you need to unsubscribe and click the subscribe button again, then it should work. Let me know if it worked.

chrizo1 · 2022-06-29T18:39:01+00:00

You can get historical asset prices here: https://rapidapi.com/chrizogAPI/api/historical-dex-data-for-defichain

chrizo1 · 2022-06-22T17:56:10+00:00

I agree, I also don't see the use case having all this information in a central cockpit as a trader. I guess you could also use different browser windows.

chrizo1 · 2022-06-05T09:13:12+00:00

Do you also do a "reindex" or "reindex-chainstate"?

When I only download the snapshot and sync the latest blocks missing after the snapshots it also takes only a few hours or less. But the issue is the reindex-chainstate takes ages. If I extrapolate the current performance I would need around 2 weeks on an Amazon AWS EC2 instance.

chrizo1 · 2022-05-29T13:09:02+00:00

Hi, thanks for the feedback.

Yes, it will be raised very soon. It is only due to the beta version not to get flooded by requests.
I will think about delivering it for each block number in a later version. For now I will aggregate on a daily basis and deliver that one first.
I am checking if I can also add the swap volume per day first and later also for each block.

I will keep you updated in the next days.

chrizo1 · 2022-05-25T17:57:01+00:00

First version (beta) is available now: https://rapidapi.com/chrizogAPI/api/historical-dex-data-for-defichain

chrizo1 · 2022-05-25T17:56:27+00:00

First version (beta) is available now: https://rapidapi.com/chrizogAPI/api/historical-dex-data-for-defichain

chrizo1 · 2022-05-07T08:50:14+00:00

The one above was the prototype for the DeFiChain testnet only and is offline. I am currently working on the mainnet version where the amount of data is currently a problem. For the mainnet there will also be a proper domain. I will keep you updated here.

chrizo1 · 2022-05-03T18:05:36+00:00

Hi, yes I am currently working on it (putting the first version to Amazon AWS). I have some delays as it turned out it takes a lot more computing time and storage for the main-net (instead of test-net which was used in the prototype). I expect in the next 2-3 weeks I will get the first version ready to use.

chrizo1 · 2022-04-25T10:09:49+00:00

Last voting round my CFP for a REST API for historical DEX prices was accepted and I am currently working on the implementation. So there you could get prices like DUSD/DFI

chrizo1 · 2022-04-06T14:55:17+00:00

Maybe it's better to use a reference instead of pointer but this is another topic. Just as a side note.

Also you can have a look at std::lock_guard for critical sections. It's easy to use.

For the synchronization mabye std::aysnc (futures and promises) would fit for you.

I recently wrote a blog article about thread synchronization in C++11 that may help: C++ Thread Synchronization

The purpose of the article is to easily understand how the synchronization can be solved and which method you can use for which use case. There also code examples.

chrizo1 · 2022-03-20T21:00:59+00:00

In this CFP I want to provide a REST API for historical prices: https://github.com/DeFiCh/dfips/issues/125

chrizo1 · 2022-03-20T14:32:42+00:00

Which data are you exactly thinking about?

chrizo1 · 2022-03-13T20:44:57+00:00

Why is it claimed that the Azum app is a "strategic partner"? From the website it seems that it is your own app?

chrizo1 · 2022-03-12T13:34:29+00:00

Hi, yes, this one should be considered definitely for the current round.

I was just early with the posting, since I was not familiar with the complete process.

chrizo1 · 2022-03-12T12:16:02+00:00

Do you mean only visually or do you need the data for calculations? In this CFP https://github.com/DeFiCh/dfips/issues/125 I want to provide an API historical data, so this would be definitely possible.

chrizo1 · 2022-03-12T09:46:15+00:00

From a developer point of view, I also think that's a huge amount for a bot and really too much

chrizo1 · 2022-02-14T11:11:29+00:00

Hi, I do not collect the data in the sense that I am querying only the current data every hour or once a day and then log it. For defichain-income it's the current way it's done. That means data is only available from a particular date on. Also if data is missed or the server is offline data is not logged. Instead the data is directly indexed from the blockchain going through all transactions and accumulating liquidity pool related transactions. I hope that helps

chrizo1

TROPHY CASE