Rugpullindex.com Round 8 proposal

OceanDAO Round 8
#1

rugpullindex.com Proposal R8

1000×300 3.96 KB

Fact Sheet

:globe_with_meridians: Website: https://rugpullindex.com
:round_pushpin: Address: 0x005241438cAF3eaCb05bB6543151f7AF894C5B58
:e-mail: Email: tim (at) daubenschuetz (dot) de
:de::bahrain: Residence: Germany, Bahrain
:building_construction::mega: Category: We’re active as builders but we also do outreach via our blog
:chart_with_upwards_trend: Metric: Network revenue

Our Product

2780×1756 386 KB

:globe_with_meridians: Website: https://rugpullindex.com
:1234: Stats: https://plausible.io/rugpullindex.com
:mega: Pitch: “Informed investment automation through data analysis and algorithmic ranking”

Executive Summary

rugpullindex.com helps data scientists and investors to make better decisions when buying data online. Our thesis is that markets are proxies for assets’ qualities.

On-chain markets present a huge untapped source of market insight ready to be harvested. By measuring and highlighting the qualities of OCEAN’s data sets, we improve the market’s overall health and performance.

Our long-term goal is to build a scalable and decentralized investment insights platform.

Track Record

  • We received funding in OceanDAO R2, R3, R4, R5, R6, R7.
  • For more reliable runway projections, we convert most of our OCEAN incomes of the OceanDAO into USDC: R2, R3, R4, R5, R6.1, R6.2, R7.1, R7.2
  • To improve financial transparency we’re publishing a cash-basis accounting statement from 2021-08-02: document

Web Analytics

Jan 2021 Feb 2021 Mar 2021 Apr 2021 May 2021 June 2021 July 2021
Unique visitors 254 538 468 462 841 720 3900
Pageviews 302 737 764 758 1300 1100 5000
Outbound clicks (abs & percentage) 0 0 0 17 (6.9%) 274 (17.7%) 365 (25.1%) 375 (7%)

Notes:

  • Our website analytics are public.
  • Outbound clicks are tracked since 2021-04-26.

Achievements in Round 7

  • For our API customers, we released a new product: A shared API to an Ethereum Erigon full node.
  • We spent some time on distribution/sales and making our website look more professional. A detailed update is in our blog.
  • We improved the accuracy of our Gini coefficient calculation.
  • We’ve implemented more JSON-RPC methods in eth-fun (eth_call). There’s interest from the ETH community.
  • We’re consulting @realdatawhale during their technical hiring process.
  • We’re gradually scaling our operations. There are now two people working on the project; maybe there’ll be three soon? We’ve started an RPI handbook to improve scalability.
  • We published a market positioning analysis to inform future branding and UI updates to RPI. The analysis also looks at comparable index tokens and smart contract products to understand how the RPI data token index product will relate to the existing RPI (data insights) product.

Roadmap

  • Rebuild RPI crawler using the Erigon API; Crawler should have more throughput and actuality; We’ll start crawling Balancer V1 pools.
  • Serve as much data as possible to the OCEAN community for building DATA&DEFI apps.
  • Measure & optimize more; API usage & website conversion rates
  • Identify additional metrics that will be shared on Rug Pull Index. This work is being actioned following our user research findings. Explanations of what these metrics are and why they are important will be created and shared on the RPI blog to attract new RPI users and make RPI a more valuable resource for existing users.

We’re more excited than ever to be working on building an investment automation platform for the DATA&DEFI ecosystem.

Funding Requested & ROI

We calculate our funding requests based on a public methodology. Exchange rates on 2021-08-03 from coingecko:

Ticker Value
OCEAN/EUR 0.42
OCEAN/USD 0.5
EUR/USD 1.19

Here are the amounts we’re requesting:

Position OCEAN USD EUR
Software engineering 17523.80 8758.4 7360
Servers: Hetzner CX11 and AX101 399.76 199.80 167.9
Average funding error† 2637.88 1318.41 1107.91
SUM 20561.44 10276.61 8635.81

† We’re trying to statistically reduce the difference between EUR amount requested and EUR amount received (caused by the volatility of OCEAN/EUR). Check our methodology to learn more.

ROI Calculation

Formula: chance = ROI/(bang/buck)

Statement: Our chance of success to reach at least an ROI of 1 is 2.5%.

Summary: We believe that by consistently shipping and re-evaluating our approach through each oceanDAO round, we’re incrementally increasing our chance of success. For a detailed calculation on ROI, check our post in Round 6.

Team

Tim Daubenschütz

Background: My “About” page and CV

Scott Milat

Please Vote For Us Because…

  • rugpullindex.com delivers reliable market insights 24/7.
  • We give you transparent insights into our proceedings by writing blog posts, by shipping regularly, and opening up our accounting.
  • Our work informs the Ocean Core team’s product development cycle.
  • You’re helping us to make a living and bootstrap a real crypto startup <3
2 Likes
[rugpullindex.com] Improving Data Trading Safety
[rugpullindex.com-R11] Improving Data Trading Safety
[rugpullindex.com] Improving the Data Economy's Safety
#2

I can confirm that Tim helped us tremendously in vetting potential blockchain developers & teams that applied to transform ALGA into a Web3 dApp. Tim’s blockchain experience, his thorough background checks and technical questions over a total of 6 interviews (5 hours) helped us to make a decision that we’ll hopefully be able to announce soon!

We’re also exploring to integrate the API that RugPull-Index provides, since it stores pool pricing data since January / 2021.

We’ve already integrated the RPI analysis in a test version of our current beta application.

You’ve got our vote! :whale:

3 Likes
#3

Great work and collaboration with the community. You got my support. Thanks a lot Tim and crossing fingers for this round.

1 Like
#4

@AlexN @idiom-bytes

  • [x] Rebuild RPI crawler using the Erigon API; Crawler should have more throughput and actuality; We’ll start crawling Balancer V1 pools.

The crawler has been rebuilt using the Erigon API. We’ve done loadtests on Erigon and we’re confident that we’ll be able to make up to 1000 req/s. We haven’t managed to crawl all Balancer V1 in existence pools but we’ve started trying to understand what that task entails. In case we decided to crawl all Balancer V1 pools; we’ll have to raise further funds in a future round.

  • [x] Serve as much data as possible to the OCEAN community for building DATA&DEFI apps.

These are our website stats since August 3, 2021 (the last time we received funding):

Screen Shot 2021-10-01 at 20.06.52
Screen Shot 2021-10-01 at 20.06.522034×1006 154 KB

Our website and API were continuously online. We’ve addressed all problems that arose as fast as possible. In fact, we even mitigated a hard fork of the Ethereum main chain and the website continued to be up even when there was 200 people simultaneously online when we hit the Hacker News front page:

Screen_Shot_2021-09-27_at_16.29.10
Screen_Shot_2021-09-27_at_16.29.101704×436 86.1 KB

  • [x] Measure & optimize more; API usage & website conversion rates
  • [x] Identify additional metrics that will be shared on Rug Pull Index. This work is being actioned following our user research findings. Explanations of what these metrics are and why they are important will be created and shared on the RPI blog to attract new RPI users and make RPI a more valuable resource for existing users.

I’ll mark these tasks as done though I guess we could have done more targeted work to solve it. All throughout August and September Scott and I had repeated conversations on which direction we want to take the company towards. As we both concluded: We first needed to figure out what we’re actually doing before we commit to any metrics. So here’s what we’ve done until now:

  • We’ve identified shared goals that we have with the project
  • We have further investigated offline how I can incorporate a company; We still have a lot of unknowns and doubts though so it could take more time.
  • We have done some initial work to understand what it takes from a technical perspective to measure our metrics.
  • We’ve spent some time elaborating on all personas that interact with rugpullindex and what their motivations are; We now have a good overview of who we want to serve.
  • I’ve written a couple of blog posts that also address some questions we’ve asked ourselves in the process:

Finally; We now have developed first drafts for what we think is an exciting vision and mission for the rug pull index. We have internal documents that do a good job outlining what it is, but to publicize it; I think it’d be advisable for us to re-iterate. I’ll close this deliverable for now though.