List view
This reflects a major upgrade to our data sourcing, where we want both: - dlt data sources that replicate into our data lake - Trino data connectors that connect to other query engines directly
No due date•2/2 issues closed- No due date•4/4 issues closed
We'd like to introduce a convenience layer for improving the Python developer experience for data scientists. Should be as easy as 1. import pyoso 2. set API key 3. read metrics from a data frame
No due date•11/11 issues closedI think there are 3 categories of costs: 1. Scalable to zero costs (e.g. compute cluster) 2. Scalable to min costs (e.g. API DB, frontend) 3. Fixed costs (e.g. storage)
No due date•12/12 issues closedWe already have metrics by project. However, we may want to be training ML models that can approximate a function (e.g. retro active impact, Vitalik's preferences, etc). We have everything we need to do this, let's write up some docs and tutorials
No due date•11/11 issues closedComplete all deliverables related to this [Foundation Mission Request](https://github.com/ethereum-optimism/ecosystem-contributions/issues/244#issue-2483588436)
Due by January 15, 2025•8/8 issues closedFirst step on the path to being a critical service. We need just 90% of availability to start. What is the minimum we need to do to get there? Let's define 1x"9" as both service availability and data quality To start, the service offering being: - When anyone from the team triggers a dbt job, results get reflected in mart models as exposed by the API 1x9 = 3 days a month outage
No due date•14/14 issues closedOur existing docs are a huge step forward from what we had before, but still falls short. It's highly technical and it assumes people already know where to find the article they need to do a thing. ("Feels like a collection of blog posts") When we are ready to improve the contributor journey, we should overhaul the docs around a set of journey / intents. I want to XYZ, how do I do it? Javi suggested that we look at the [Deno docs](https://docs.deno.com/) for inspiration
No due date•14/18 issues closedBack at it again! Speaker applications and registration is open now
No due date•3/3 issues closedWe are long overdue with better landing pages for aspects of our product, case studies, use cases, etc. This epic covers a bunch of new landing pages we want to ship on the OSO website
Due by October 21, 2024•10/10 issues closedWe want to transition more of the data pipeline to: sqlmesh on top of Trino over Iceberg on GCS. This on the way to deprecate the use of dbt. We should build this out of band without breaking the existing dbt pipeline. Plan is to grow the existing sqlmesh pipleine until it is a superset of the dbt pipeline, then swap.
No due date•42/42 issues closedFull spec for [onchain builders](https://www.notion.so/Retro-Funding-Metrics-Spec-Onchain-Builders-v2-b3e99d057aa6444aa902c0ecf25b5168?pvs=4) and [devtooling](https://www.notion.so/Retro-Funding-Metrics-Spec-Developer-Tooling-cddd76fe04c64560a7f2c9fe2e6b86d6?pvs=4) - Feb 13th: Project enrollment opens - Feb 27: End of enrollment period to qualify for the first measurement Retro Funding: Onchain Builders rewards projects that drive cross-chain asset transfers, enabled through interop, by growing the onchain economy across eligible OP Chains. 1. **Expected impact on the Intent**: Drive cross chain asset transfers by growing the onchain economy and the adoption of interop among onchain builders 2. **Eligibility**: Projects are eligible who have deployed their own contracts on supported OP Chains. To claim a contract, the deployer address of the contracts needs to sign a message in the Retro Funding sign up. Contracts deployed by factories are attributed to the factory deployer. Detailed eligibility criteria will be published by the Foundation near the start of the program. 3. **Evaluation Algorithm**: The first iteration of the evaluation algorithm will be selected by Citizens before the start of the mission. Impact will be rewarded within the following topics: 1. Growth in Superchain adoption 2. High-quality onchain value (e.g., TVL) 3. Interoperability support and adoption 4. **Measurement Date**: Monthly, starting in February See full spec [here](https://www.notion.so/Retro-Funding-Programs-in-Season-7-1365831e345280ae9f42ecc19793754d?pvs=4).
Due by March 17, 2025•91/91 issues closedWhat has been the impact of the Retro Funding so far? What improvements should be made in 2025?
Due by November 18, 2024•5/5 issues closedIndexing and joining data from SBOMs, package metadata, deps.dev histories, and package servers
Due by February 7, 2025•11/11 issues closedRetroactive Public Goods Funding (Retro Funding) 6 will reward contributions to Optimism Governance, including governance infrastructure & tooling, governance analytics, and governance leadership.
Due by November 19, 2024•8/8 issues closedThe processes, rituals, institutions in place to organize and scale the Kariba Data Collective into the data/insight marketplace that we've been discussing in the Superchain
No due date•20/24 issues closedRetroactive Public Goods Funding (Retro Funding) 5 will reward contributors to the OP Stack, including core Ethereum infrastructure that supports or underpins the OP Stack, advancements in OP Stack research and development, and tooling which supports its accessibility and usability.
Due by October 21, 2024•16/16 issues closedIn order to show value we will need more evidence of efficacy. We need to be tracking any *funded metric* for all time with time series data, for both funded projects and the counterfactual
No due date•42/42 issues closedOnchain metrics for the Superchain SUNNY awards https://docs.google.com/document/d/14fwrdIROtAav1U36k3kB_6C-cHpdzzGFqNvZrqOGlGY/edit?usp=sharing
Due by October 17, 2024•12/12 issues closedInitial public datasets (e.g. Superchain/Goldsky, Farcaster, Gitcoin, EAS, etc) on https://docs.opensource.observer/docs/integrate/overview/ served from a BigQuery Analytics Hub Data Exchange.
Due by November 20, 2024•32/32 issues closed[Spreadsheet](https://docs.google.com/spreadsheets/d/1B_5MiL7850-5v6hTriSGpfAvRKTZJdmLVk51mg8m_0I/edit?gid=0#gid=0)
Due by November 18, 2024•5/5 issues closed- No due date•21/22 issues closed
- Due by July 26, 2024•26/26 issues closed
We are looking to do more in clickhouse, including - sqlmesh pipeline - user-generated projects/collections/metrics
Due by October 2, 2024•21/21 issues closedEcosystem Health Overview
No due date•31/32 issues closedGet all the data needed for RF4 impact metrics and API users.
Due by July 26, 2024•94/94 issues closedWe want a richer metrics driven web app, to include: - Collections view, broken out by sectors (e.g. Dex, gaming etc), and ecosystem (e.g. Superchain, Arbitrum) - Projects page that's more succinct - Artifacts page that's more succinct - Metrics directory - Dataset directory This should also be a community hub where members of the community knows exactly how to contribute to each phase
Due by November 18, 2024•35/35 issues closedWe want modelers to be able to easily make SQL queries from whereever they are. Currently, we expect them to do their own thing in BigQuery, but we may want to consider either: - Some way to do basic query/exploration in OSO - Some way to query a community Clickhouse from whereever they are (e.g. Colab, Hex, etc)
No due date•7/7 issues closedBacklog of Blockchain data related issues
Due by May 10, 2024•9/9 issues closedSet up docs, tutorials, and onboarding for data collective members to join the first Data Challence.
Due by June 12, 2024•10/10 issues closedAdd funding events from different sources to OSO. These include onchain flows (to project addresses from grant providers and Drips), web2 data sources (eg, open collective), and potentially static dumps from foundations.
No due date•29/29 issues closed