Algovera | Algovera: Building a Decentralized Hub for Data Scientists in Web3 | Round 161

OceanDAO Round 16
#1

Project Name

Algovera

Project Description

We are a community of data scientists making it easier to build, co-own and monetize AI apps in Web3. We describe Algovera in three layers: (i) community, (ii) tools/libraries/integrations, and (iii) commercialisation. We onboard data scientists to Web3, train them to use tools such as wallets, the Ocean marketplace, Compute-to-Data (C2D), run weekly data science hacking sessions and run a grants program for funding data science teams. We are integrating many technologies such as data marketplaces, decentralized storage and compute, data science libraries and DAO infrastructure to make it easier to build, co-own and monetize AI apps in Web3. Finally, we provide consultancy services to data providers and domain experts to create useful applications on top of raw data.

Final Product

A Web3 AI marketplace with tools, libraries and integrations that make it easy to build, collaborate and monetize AI apps.

Core Team

Richard Blythman

Hithesh Shaji

Keaton Kirkpatrick

Jakub Smékal

Proposal One Liner

Consolidating our tools, libraries and integrations into a decentralized hub (a customised provider) for data scientists working in Web3

Proposal Description

We’re starting to consolidate our to our tools, libraries and integrations into a decentralized hub (dHub) to make it easier for data scientists to work in Web3. This involves modifying Ocean Provider with new functionality such as data encryption (and later decentralized storage and ML ops). We will also continue to develop our custom JupyterLab compute environment by integrating decentralized storage and access control. Furthermore, we are continuing to grow the number of AI projects within the Algovera community with 5 more to be onboarded this month and also continuing freelance work with at least one new client.

Grant Deliverables

Tools/Libraries/Integrations

  • [ ] Proof of concept for modifying Ocean Provider to also encrypt data
  • [ ] Integrate Estuary API with Algovera’s custom JupyterLab to facilitate easier access to decentralized storage for data scientists
  • [ ] Integrate Lit Protocol with Algovera’s custom JupyterLab to facilitate decentralized access control with storage
  • [ ] Complete architecture diagram for Algovera stack
  • [ ] Proof of concept for using dHub to create and modify assets in an Algovera backend (first on GitHub, e.g. in Algovera Creations repo, custom backend in future)
  • [ ] Design process for signing in to Algovera to gain access to services
  • [ ] Initial report on plans for integrating IPFS node with Ocean Provider
  • [ ] Initial report on plans for integrating ML ops tools such as Kubeflow with Ocean Provider

​Commercial

  • [ ] Run training of medical image classification and EEG classification on custom Ocean provider to assess issues experienced with Ocean C2D during freelance and hackathon work with clients
  • [ ] Kickstart consultancy work for at least one new client

Community

  • [ ] Create Snapshot spaces for voting for Round 2
  • [ ] Create and distribute Reputation NFTs (ERC1155) for voting on grants
  • [ ] Plan and announce Algovera Demo Day #1 in our metaverse HQ where we will showcase the exciting projects in the Algovera ecosystem
  • [ ] Run weekly reading group meetings/juntos
  • [ ] Outreach at ETH Amsterdam

Value Add Criteria

  1. Usage of Ocean


Data scientists are natural data consumers. Creating further tools, libraries and integrations (and making it easier for data scientists to onboard to Web3) will help to increase consume volume of data and algorithm tokens. Funding more data science projects will result in more new projects and assets using Ocean. Completing freelance work will help to develop raw data into algorithms and insights.  

Funding Requested

20000

Wallet Address

0x823351c03A99b4820793675760f4A64F5ccA9089

#2

Project submitted deliverables:

  • [✓] Proof of concept for modifying Ocean Provider to also encrypt (and decrypt) data (encrypt, store, decrypt flow for an asset class, notebook demo, additions to data provider class)
  • [✓] Integrate Estuary API with Algovera’s custom JupyterLab to facilitate easier access to decentralized storage for data scientists (code, pip package)
  • [✓] Integrate Lit Protocol with Algovera’s custom JupyterLab to facilitate decentralized access control with storage (standalone app that integrates lit with estuary: code and app)
  • [✓] Complete architecture diagram for Algovera stack
  • [✓] Proof of concept for using dHub to create and modify assets in an Algovera backend (code, video)
  • [✓] Design process for signing in to Algovera to gain access to services
  • [✓] Initial report on plans for integrating storage with Ocean Provider
  • [✓] Initial report on plans for integrating ML ops tools such as Kubeflow with Ocean Provider
  • [✓] Run training of medical image classification and EEG classification on custom Ocean provider to assess issues experienced with Ocean C2D during freelance and hackathon work with clients
  • [✓] Kickstart consultancy work for at least one new client (face anonymisation with DataUnion)
  • [✓] Create Snapshot spaces for voting for Round 2
  • [✓] Create and distribute Reputation NFTs (ERC1155) for voting on grants (blog announcement)
  • [✓] Plan and announce Algovera Demo Day #1 in our metaverse HQ where we will showcase the exciting projects in the Algovera ecosystem
  • [✓] Run weekly reading group meetings/juntos (discord channel)
  • [✓] Outreach at ETH Amsterdam (e.g. coworking space, DeSci day)
#3

Admin:

Hi,

Thank you for submitting another update for your previous proposal! Your Grant Deliverables have been reviewed and look to be in good condition.

We have also looked at your Project Standing, it looks to be in good condition and ready to apply for another grant.

We would like to thank you for your positive contributions to the Ocean Ecosystem and I look forward to reviewing future proposals from your project.

All the best!
Your OceanDAO Team

#4

^^ This link and its deliverable do not match. Is there a different process flow link that you meant to include for signing in to Algovera ?

#5

^^This does not have public access for community members to view

#7

^^ Can you link to the relevant part of the code library