contracts VS bargeparse

> Who should use your site but others who also want to offer data asset funds? Why do you build the exposure for rugpullindex instead of directly creating the fund?

Good question. Initially, I went for building the fund product directly. Then I noticed that in my jurisdiction it's far from easy just launching a financial product. Additionally, one problem that I continue to have is that for the data assets curated on my site, an old version of Balancer contracts (V1) [3] is used which means each rebalance for 10 assets would come at a cost of > 100k gas * 10 assets.

I've thought of optimizing gas cost, but I haven't found a solution so far [1], [2]. The Ocean Protocol team had also promised to upgrade to Balancer V2 up until recently on their public roadmap website. But they've suddenly changed priorities and so now I'm doubting that those contracts will ever become upgraded...

> Your site could use a filter for various data markets.

What other data markets do exist? I'd definitely be happy to integrate other markets too.

> Right now, investing in the index is risky because competing data sets to core assets of the index could drive down its value fast.

I'm not sure I get what you're saying. Mind elaborating?

- 1: https://timdaub.github.io/2021/04/19/ethereum-web3-saving-ga...

- 2: https://rugpullindex.com/blog#IntroducingHoneybatcher

- 3: https://github.com/oceanprotocol/contracts/tree/main/contrac...

I don't have a startup but I did make a useful little Python library while at my previous job to help ease the pain with using argparse to make CLIs.

It's called bargeparse [1]. The idea is to define an entry point function and use its signature as a means to declare the CLI arguments & options. I was surprised at how well Python's syntax for function arguments works for this... especially the use of pos-only & keyword-only arguments to force a particular style.

[1] https://github.com/shangxiao/bargeparse