EngRes Team Summit

Day 2

October 26, 2022

EngRes Team Summit

Lightning Talks

October 25, 2022

Today’s Schedule

9:00 - Why Roadmapping (this way) - Juan

9:30 - PL Network Roadmapping Tool (WIP) - Reid

9:40 - Draft 2023 Goals and Metrics - Molly

10:00 - Working Session: Team Roadmaps (1.5h)

11:30 - Break ☕️

11:45 - 2023 Roadmap & Priorities

• Critical System Stewardship (25 min)
• Team & Network Growth (10 min)
• Compute (15 min)
• Storage & Retrieval (10 min)

12:45 - Closing Thank You’s

13:00 - Lunch 🥘

Why Roadmapping (this way)

October 26th, 2022

PL EngRes WG

Throughout PL’s history, we’ve experimented with dozens of planning tools and roadmaps.

Throughout PL’s history, we’ve experimented with dozens of planning tools and roadmaps.

Teams always have different requirements, nuances, and preferences => teams need different tools for their own work.

Throughout PL’s history, we’ve experimented with dozens of planning tools and roadmaps.

Teams always have different requirements, nuances, and preferences => teams need different tools for their own work.

And, we’ve arrived at a set of requirements for inter-team & user-focused roadmaps.

And, we’ve arrived at a set of requirements for inter-team & user-focused roadmaps.

Key Guiding Principle: � Roadmaps have diff. purposes → different Zoom Levels

Zoom 1

Zoom 2

Zoom 3

Zoom 4

We’ve arrived at a fine-tuned set of requirements for inter-team & user-focused roadmaps.

Zoom 1

High-level plan

User Roadmap

Zoom 2

Zoom 3

Engineering breakdown

Orients and aligns stakeholders against valuable progress indicators

​

(other teams/startups can plan against quarter-year scale milestones)

User Roadmap

Need a way to integrate & cross-ref

Need a way to externalize plan, progress, & dependencies publicly

Inspiration

Communicates wider themes & milestones across upcoming improvements, easily sharable in public talks!

Key requirement: 1 slide, visual, in time.

Sub-Ecosystem Roadmap

This, but machine readable

& Interlinkable

In a convenient, easy to use, familiar way (github issues)

Roadmapping Tool

October 26th, 2022

PL EngRes WG

Prompt

2023 Goals & Metrics

October 26th, 2022

PL EngRes WG

EngRes 2023 Strategy

PLv9 Principles

• Optimize & Scale
• If you don’t measure it, you can’t improve it: Instrument & measure our product flow success rate & top errors (esp for storage/retrieval failures + gaps)
• Real user impact or it doesn’t count: Ship breakthrough alpha networks, and productionize them relentlessly with early adopters

​

• Focus on End-user Product UX
• Remember, we’re aiming for AWS: We need an excellent, enterprise-quality user+dev experience!
• Design for modularity: many permissionless solns

​

• Strengthen the connectivity of the network
• Double down on network-native development: Work in public, share knowledge, and accelerate other network teams
• Grow the network!

For EngRes

• Optimize & Scale
• Double down on what’s working, change what’s not
• Optimize systems (impact metrics)
• Scale products operations
• Ship breakthroughs to production, and drive usage

​

• Focus on End-user Product UX
• Instrument products to optimize for UX
• Feedback loops: (metrics + qualitative feedback) → excellent product UX

​

• Strengthen the connectivity of the network
• Relationships, Office Hours, work weeks
• Events: conferences, etc
• Knowledge: work openly and collaboratively

2023 Goals

1. Grow critical team + network systems safely + robustly (IP Stewards + NetOps + FilDev)
1. <Catalyze growth of additional IPFS clients and implementations>
2. <Create a robust, automated benchmarking system for libp2p mapping performance gaps>
3. <IPFS & Filecoin Network + Infra security / uptime>
4. <IPFS usage grows 10x (developers, end users, dependent projects)>
5. <cut costs to centralized web2 services by 50% (use our tech!)>
6. <Filecoin chain state is stored and served from filecoin>
7. <Drand, libp2p, and testground gain XX new network adopters each>
8. ??

2023 Goals

• Level up team & network capabilities (EngRes Team Leads)
• <Hire L6 EMs, R&D leads, team leads, senior TPMs, etc to scale leadership>
• <Ensure no team has bus factor <2 (either hire, or cancel the project)>
• EngRes takes leadership in growing the implementer & developer communities by 50% (ex through participation in key events)
• <level-up org capabilities around performance + error benchmarking, metrics, and automation>
• <Hire product & eng team for IPC>
• ??

2023 Goals

• Hyperscale fast retrievals (Bedrock + RetMkts + IPFS Gateway)
• Saturn & Station achieve 100K+ active retrieval nodes
• Saturn integrates with IPFS Gateways to drop TTFB without $$
• <end to end retrieval measurement, testing, reputation, and incentives>
• Boost and lotus-miner support data onboarding to over 500 TiB / node?
• Boost and indexers make >75% of all data stored in Filecoin retrievable from gateway, saturn, kubo
• ??

2023 Goals

• Drive adoption for computation (ResDev + FVM + FilDev)
• FVM M2(.1&2) with >1K smart contracts from >1K devs shipped on Filecoin mainnet
• Transact 200M FIL via smart contracts (“total value managed” / locked into deals)
• <## users of L2 Filecoin capabilities like retriev.org, onchain.storage, etc>
• <ship IPC to Filecoin mainnet & drive adoption>
• <ship Bacalhau GA & drive adoption>
• <Experimental POC of IPVM MVP>
• ??

Working Session:

Team Roadmaps

October 26th, 2022

PL EngRes WG

☕️ Coffee Break…

Next session starts in 15 min

🗣Icebreaker Topic:

Who is doing something cool you hope to collaborate with or support next year?

​

​

PL EngRes Project Roadmaps

October 26th, 2022

Molly Mackinlay

🗺 Roadmap Presentations

EngRes 2023 Strategy

EngRes 2023 Strategy

EngRes 2023 Strategy

IPFS Stewards: 2023 Priorities

@Reid

• Strengthen/Grow IPFS Contributors Community
• New contributor guides, first issue guides, docs, etc.
• Strong issue and PR triaging and review SLAs
• Hire additional community engineers to support contributors
• Fully Transition to Dynamic Content Routing Selection:
• Complete the transition to Delegated Routing/Reframe on Gateways
• Ship dynamic content routing defaults in protocol/Kubo
• Catalyze Growth of Additional Clients and Implementations:
• Enable verifiable retrieval from Gateways to “Light Clients” (e.g. browser)
• Kubo-as-a-Library for use by new clients
• Create First-Class IPFS Protocol Specs and build out protocol evolution framework/process
• Develop IPFS KPIs
• Establish KPIs to measure product perf and community health
• Deliver KPI automation/dashboards

IPFS Stewards: 2023 Roadmap

@Reid

IPFS Stewards: 2023 Roadmap

@Reid

ProbeLab: 2023 Priorities

@yiannis

Area 1: Verify correct operation and optimize core stack protocols - focus: DHT, Gossipsub

Importance: Improve user-perceived QoS, help optimize other implementations

• M1.1: Justify the role and importance of Hydra boosters
• M1.2: Justify and optimize the DHT aborts/timeouts
• M1.3: Verify the correct operation of Gossipsub in the Filecoin network

Area 2: Improve and productionize our Monitoring & Measurement Infrastructure

Importance: The ecosystem can easily consume our results and re-use our tools

• M2.1: Deploy and visualise our measurement tools in a public and re-usable platform
• M2.2: Thunderdome is user-friendly and automatically tests new kubo releases

Area 3: Improve libp2p privacy guarantees

Importance: Satisfy long-standing community and user request

• M3.1: Ship the Double-Hashing improvement for reader privacy
• M3.2: Investigate and develop techniques for writer privacy, and Tor/Onion integration

🔒 Secure

Building on libp2p improves an application's security posture. We minimize vulnerabilities and act rapidly to address and report issues.

🥽 Specified

We thoroughly specify the libp2p framework and its suite of supported protocols, independent of language or implementation. Through specifications, we coordinate and drive future developments.

🪨 Stable

Releases do not unknowingly break deployed features. We maintain cross-version compatibility across libp2p releases and implementations. Deprecations are well-communicated.

🚀 Performant

We ensure comparable performance to widely used protocols on the Internet. We avoid performance degradations in new releases.

libp2p Tenets 🏛️ - libp2p is:

@marten-seemann

These tenets form the foundation for features and initiatives in implementation roadmaps.

As a result, we generally prioritize filling any gaps in these tenets above other work.

libp2p: 2023 Priorities

📡 Connectivity: expand libp2p ecosystem 🤝 browsers

Why:

• Enable building new types of apps, reimagine existing ones (Glif ← WebTransport → FIL node)
• Reduce user confusion, user reliance, and maintenance cost by deprecating outdated solutions (webrtc-star, webrtc-direct)
• Enable Wasm use cases (make libp2p run anywhere)

🏎 Performance: prove libp2p is fast, make it even faster

Why:

• Educate users, inspire confidence in libp2p, answer why users should build on libp2p as compared to HTTP
• Show users libp2p is on par with HTTP in real-world network conditions
• Speed up users and decrease TTFB for apps built on libp2p

⚙️ Interoperability: prove libp2p is interoperable

Why:

• Ensure users that building in the libp2p ecosystem is seamless
• Show users that different libp2p implementations, versions, supported protocols interoperate reliably
• Show the world that building on libp2p means building on solid foundations:

well tested, battle-hardened, & backwards compatible software

​

@marten-seemann

libp2p: 2023 Roadmap

• 📡 Connectivity: Include browsers in the libp2p ecosystem
• use WebTransport to enable new use cases (upload to Filecoin from the browser)
• Deliver WebRTC
• browser nodes can connect to Go / Rust nodes
• browser nodes can connect to other browser
• ⚙️ Interoperability: Prove libp2p is interoperable
• Guarantee that libp2p is the reliable basis for multi-billion dollar networks
• 🏎 Performance: Prove libp2p is fast
• Speed up connection establishment (faster TTFB)
• Support better transports (QUIC in rust-libp2p.)
• Create a performance dashboard showing that libp2p is on par with HTTPS (throughput)

​

@marten-seemann

Q4

Q1

Q4

Q1

Q4

Q4

libp2p: 2023 Priorities

📡 Connectivity: expand libp2p ecosystem 🤝 browsers

How:

• Deliver WebRTC, enable browser ⇄ browser and browser ⇄ rust-libp2p node connectivity.
• Chromium browser nodes can already connect to go-libp2p nodes using WebTransport.
• Add first class Wasm support in rust-libp2p

🏎 Performance: Prove libp2p is fast

How:

• Benchmark implementations in Testground and generate a public performance dashboard.
• Reduce connection establishment time, dial more efficiently, support better transports (QUIC in rust-libp2p.)

⚙️ Interoperability: prove libp2p is interoperable

How:

• Validate all Go, Rust and JS libp2p releases against each other by testing their supported transports, muxers, and security protocols (using Testground.)
• Generate nightly public Chromium-like test results dashboard.

@marten-seemann

libp2p: '22 Q4-'23 Q1 Roadmaps 🗺

@marten-seemann

libp2p/test-plans/master/ROADMAP.md

χ

The test-plans roadmap is complementary to the Go, Rust, and JS roadmaps.

It aims to encompass the stability and performance tenets of the libp2p team. Projects outlined here are shared priorities of the different implementations.

libp2p: '22 Q4-'23 Q1 Roadmaps 🗺

@marten-seemann

go-libp2p/master/ROADMAP.md

js-libp2p/master/ROADMAP.md

rust-libp2p/master/ROADMAP.md

IP JS: 2023 Priorities

1. PL is making space for additional IPFS implementations, including in JS. To this end, we are renaming js-ipfs. As with Kubo, we will have a collaborative process around deciding on the new name.
2. We will design and build a new IPFS-in-JS implementation (codename “Pomegranate”) incorporating all of our learnings over the last 8 years. Defining attributes include a web-first isomorphic API (so it can run in browsers, Electron, Node.js, Deno, Bun), an ergonomic JS-developer-first API (decoupled from Kubo), and TypeScript/ESM from day one.
3. We will leverage new browser-friendly p2p transports ike WebTransport and WebRTC.
4. We will support delegated routing and Reframe endpoints.

@Alex

IPFS-in-JS: 2023 Priorities

202211 - communicate the IPFS-in-JS state

• Problem to solve: right now very few in EngRes or outside of it know what’s the direction for IPFS-in-JS and how they can help. This affects project resourcing, project recruiting, and IPFS adoption in general.
• Done state: IPFS Camp 2022 presentation, blog post, community vote and communication about new IPFS-in-JS implementation name.

​

202212 - Double team capacity

• Problem to solve: currently the IPFS-in-JS effort has less than one full-time SWE who is also splitting time with js-libp2p.
• Done state: accepted offer for an additional full-time engineer.
• Why: extra hands are needed for designing, planning, and executing on IPFS-in-JS. Even if we outsource development, help is needed to review and guide the development work.

@achingbrain

IPFS-in-JS: 2023 Priorities

202301 - “Pomegranate” execution plan

• Project scope, milestones, success criteria, communication channels, and working group are all established.
• Public community can follow along with and contribute to “Pomegranate”.

​

2023Q1 - “v1” of “Pomegranate” released

• Users can add and get files.
• Packaging, publishing, testing, CI/CD, etc. are all setup.

​

2023Q2 - EngRes ceases maintaining “legacy js-ipfs”

@achingbrain

• Increase developer velocity & decrease onboarding friction:
• (1) Keep Critical Systems Running
• Pay off tech debt of ipfs-desktop, ipfs-webui, ipfs-companion
• Increase developer velocity
• Decrease onboarding burden for new contributors
• Using the latest dependencies (ipfs and not) and following the latest paradigms will encourage more adoption and increase velocity further.
• Increase adoption & usage of Ignite products by X%:
• (2) Growing Team & Network
• Develop & Implement UX strategy
• Increase team headcount
• UI Refresh
• 🌠 🎑💫 Distributed web3 hosted WebComponents
• The web3 way to do re-usable, reliable, scalable, self-verifiable components for building the UIs of the future.

IPFS GUI and Tools team → IG&T → Ignite: 2023 Priorities

@russell

• IPFS Companion will:
• Be updated to support Manifest V3. V2 extensions will be marked unlisted June 2023, so this is time-sensitive work.
• Get a code cleanup, including the removal of ~4k lines of dead code.
• Get a UX revamp and onboarding improvements.
• IPFS Desktop & webui will:
• Keep pace with Kubo feature development.
• Be decoupled from js-ipfs, which has made it extremely difficult to adopt Kubo features that don’t make sense and/or aren’t implemented in js-ipfs.
• WebTransport and DAG CAR support.
• Diagnostic tooling overhaul.
• Public Gateway Checker will:
• Get a UI overhaul for better consistency with the other GUIs, alongside new visibility for metrics like DAUs and gateway check success percentages.

Ignite: 2023 Roadmap

@russell

IPLD: 2023 Priorities

@rvagg

Core Priorities: Resourcing, team-rebuilding, forming an aligned, cross-language IPLD vision and tooling

Important work items:

Lotus & Actors: 2023 Priorities

• 🦉Critical System Stewardship: Continue to keep the network operational.
• 🐩Growing Team & Network: Help onboarding human being
• 🐱Engineering Three Tracks

@jennijuju

1️⃣ Driving research to production

• Protocol opportunities discoveries -> FIPs
• Collaborate with FIP authors to bring research efforts to production
• Ship the FIPs & continue to steward network upgrades (with fun codenames and memes.)

​

2️⃣ Define the identity of Lotus as a client implementation

• Define the users & uses cases
• Engineering efficiency: simplify and cleanup the code base

​

3️⃣ Robust Storage: Modular Lotus Miner

• Re-architect and modualize lotus-miner to enable easy deployment for large scale enterprise level Storage providers

Lotus & Actors: Drive research to production

@jennijuju

1️⃣ Driving research to production

Q4 2022 🦈Filecoin v17 Shark Upgrade

Q1 2023 💙Filecoin FEVM Upgrade

Q2 2023 🗄️User Programmable Storage Markets

Q3 2023 🛰️ Excellence Programmable Storage Markets: Halo2, User Cron & beyond

2️⃣ Define the identity of Lotus as a client implementation

Q1 2023 Hardening Lotus Code Base: Drop EOL-service code

Q2 2023 Lotus Client Experience: Easy deployment, Filecoin client API standard, Light Client

3️⃣ Robust Storage: Modular Lotus Miner

Q4 2022 🔁Flexible Scheduler

Q1 2023 🧷 Standalone Sealing Manager Process

Q2 2023 🪄 Updatable Storage

Q3 2023 🧑‍🔬 Redundant Proving System

Fil-Infra: 2023 Priorities

• Filecoin Core Infrastructure will continue to scale and decentralize
• Lotus Lightweight Chain Snapshots
• Official launch with Lotus Shark upgrade (Q4 2022)
• Snapshot artifact storage decentralization and redundancy (Q2 2023)
• Lotus Bootstrap Node and Disputer Decentralization
• Develop Impact Evaluators and Service Level expectations (Q1 2023)
• Lotus Gateway (api.chain.love)
• Improved Horizontal Scaling and Website (Q4 2022)
• Lotus Build Artifact Pipeline
• Lotus Build Artifact Dashboard and Reporting (Q4 2022)
• Lotus release pipeline re-architecture, validation, and observability (Q1 2023)
• Web3 GitOps Platform will accelerate application productionization
• General Availability (Q1 2023)
• Next Generation Lotus Devnets will lower the bar of entry for creating new Devnets
• Devnet Deployment Automation and Tooling For CI Integrations and Easy Devnet Creation (Q2 2023)

@ognots

PLAY ME

Sentinel: 2023 Priorities

🌺 Lily (Filecoin Chain Indexer)

• Lily ready for FVM adoption in Lotus/Filecoin.
• Extracted chain states as IPLD objects to serve as IDL for consumers.

💾 PLDW (PL Data Warehouse)

• Full blockchain data available in BigQuery
• Include off-chain data in BigQuery
• Filecoin data validation / quality check

👫 Community

• Collaborate with partners to run and improve Sentinel/Lily nodes

@birdy

CryptoEconLab, Core Protocol WG: 2023 Priorities

@tom

Main Objectives:

• O1: Prepare gas economy for scalability and feature upgrades
• O2: Sustain health of Filecoin's economy and escalate issues early
• O3: Develop capacity to power new research and quickly form views on economic policies

Key Milestones for next 6 months:

• M1: Propose Baseline minting to be rebased with a QAP parameterization (12/2022)
• M2: Spec released for Interplanetary Consensus economic design (11/2022)
• M3: Propose an upgrade of Filecoin gas model to support FVM (12/2022 - 1/2023)

Drand: 2023 Priorities

Area 1: Refactor codebase to support next stage of development

Importance: Increase confidence in codebase, reduce risk of incidents and downtime

• M1.1: Refactor the most central parts of the ceremony, aka DKG, to enable resilient, seamless and stable async ceremonies
• M1.2: Deploy unchained randomness and higher frequency beacons on mainnet
• M1.3: Filecoin switches to that network (through FIP process)
• M1.4: Have Timelock Encryption on FVM

Area 2: Drive Community Engagement: Create easier onboarding for developers and users of drand

Importance: Increase drand adoption

• M2.1: drand hackathon
• M2.2: howto guides and regular blogposts
• M2.3: ProtoSchool tutorial(s)

Area 3: LoE Engagement

Importance: Create team spirit and more active involvement of the 16+ partners

• M3.1: Materialize incentives for LoE partners

@yiannis

Docs: 2023 Priorities

• Q1: Internationalization (i18n) & localization (l10n)
• Kickstart translation efforts to translate content across all sites.
• Adapt documentation to particular locales by engaging project communities.
• Q2: Organize & Improve UI/UX
• Implement a sleek and composable base layer for doc sites to better present content and create meaningful educational flows.
• Deploy CI/CD to improve efficiency and reduce manual doc maintenance.
• Beautify content through universal assets such as diagrams.
• Q2: Enable robust OSS contributions
• Initiate a contributors hub that includes style guides, conventions and templates, and reduce overall friction for doc contributions.
• Implement a pipeline for content curation.
• Q4: Initiate DaaS:
• Transform the docs team as a docs service provider.
• Unify and standardize docs site tooling and infrastructure.
• Implement a decentralized docs static site generator.

@jennijuju

EngRes 2023 Strategy

Level-up EngRes Team Growth: 2023 Priorities

• Hire important L5 and L6 managers and org leads to help scale our leadership team
• Invest in new Leveling system that we can share with the PL Network
• Create new WGs for Private data, and scale how existing RetMkts / CoD WGs can connect their participants with network development (roadmaps)
• New network alignment tools and forums (EngRes Roadmapping tool, sync/async Leads summits)

@momack

Growing the Team and Network

October 26th, 2022

PL EngRes WG

EngRes Events: 2023 Priorities

• 📰Communicate
• Send out newsletters with news, upcoming events, statistics

​

@yuni

CryptoEconLab, Ecosystem WG: 2023 Priorities

@dave

Main Objectives:

• O1: Establish CEL as defining global leader in Cryptoeconomics
• O2: Increase PLN Understanding of Cryptoeconomics (of Filecoin)
• O3: Ensure Filecoin Governance has Effective Mechanisms and Cryptoeconomics

Key Milestones for next 6 months:

• Quarterly CryptoEconDays are the largest and most productive event in Cryptoeconomics (3/2023)
• Cryptoeconomic educational workshops delivered across the PLN (3/2023)
• Mature publication channels for content from CEL researchers (2/2023)
• Publish state of knowledge report on Economic Governance in Web3 (12/2022)

IPDX: 2023 Priorities

@galargh

Testground is THE distributed/decentralised systems testing platform

User Goals

1. Testground is delightful to use => 1K users
2. It is easy to delegate large scale test plans to Testground as a Service => 1M CI test plan runs
3. Testground meets all libp2p’s network simulation needs => 1B CI test case runs

Project Requirements

• We have Testground stability dashboard
• We follow high-quality software development and project management standards

​

We work together

• We bridge the gap between teams on software development excellence
• GitHub Management backs periodic GitHub access audits
• GitHub Actions can be monitored at scale
• We excavate the pain points IP Stewards endure

​

You can count on us

• Unified CI had 2 major releases

IPDX: 2023 IPDX Roadmap

@galargh

IPDX: 2023 Testground Roadmap

@galargh

EngRes 2023 Strategy

Storage and Retrieval

October 26th, 2022

PL EngRes WG

Bedrock: 2023 Priorities

Bedrock is a Team of (Platform) Teams

1. Retrieval Protocols + Boost - Reliable and performant retrievals to increase user adoption.
2. Indexer - Content discovery so that public data can be found and retrieved through IPFS and Filecoin with web2 speed
3. Boost - Scaling data onboarding so that more useful data is stored on the network leading to more case studies leading to more user adoption
1. 🤔Constant Question: How can we enable more compelling case studies of data storage and data serving through Filecoin?
2. 🚘Will work across teams to help drive retrieval incentives.
3. 🤝Will work closely with other teams to enable� (1) Network Growth team to bring on more SP’s and clients,� (2) Retrieval Markets team to serve content and� (3) CoD team to read and write data.

​

@jacob / lauren

Retrieval Markets WG: 2023 Priorities

What are the 1-3 main areas your team is focused on next year, and why are they important to the wider PLN / networks?

• Grow the RMWG and communicate the progress
• Deploying retrieval networks (dCDNs).
• The reliable, performant and economic retrieval of data stored on Filecoin will close the loop in the Filecoin economy’s value flow, and enable mass adoption.
• Designing cryptoeconomic incentives for retrievals.
• The right mechanism design for retrieval will lead to Storage Providers providing a great retrieval story as well as causing the emergence of thousands of points of presence in dCDNs. FVM will unlock many possibilities here.
• Data transfer protocols.
• Improvements in Bitswap, Graphsync, WebRTC, WebTransport will unlock new performance gains in dCDNs.

@patrickwoodhead

Saturn: 2023 Priorities

What are the 1-3 main areas your team is focused on next year, and why are they important to the wider PLN / networks?

• Grow the Saturn L1 Network to 200 Nodes
• The Saturn L1 network is the first step towards CDN-class performance to retrieve data stored on Filecoin.
• Launch a useful L2 Network
• If we can build a performant and reliable L2 network then millions of new people will be able to contribute to the Filecoin economy by downloading Station.
• Accelerate IPFS Gateway Traffic
• Increase the performance of the IPFS gateway for users globally and reduce infrastructure costs.
• Onboard Content Publisher Customers
• This is the first step towards Saturn’s business model. Eventually all rewards for Saturn node operators will come from Content Publishers accelerating their data with Saturn.

@ansgar

Station: 2023 Priorities

• What are the 1-3 main areas your team is focused on next year, and why are they important to the wider PLN / networks?
• We are researching a VM / runtime isolation layer for Station modules, so that untrusted code can be run on desktops worldwide. This drastically increases the number of potential peers for CoD, Saturn, etc.
• We are developing resource management so that above mentioned work doesn’t negatively impact the user experience of using their machine
• We are improving the module integration story, so that Station becomes a simple integration target for developers who want to put their on/off-chain code into users’ hands, without needing to create UI for it
• What are the key milestones your groups is pushing towards in 2023?
• Public launch with Saturn module paying out FIL rewards for CDN acceleration
• Runtime isolation strategy
• Bacalhau module for CoD

@Miro

CryptoNet Lab: Storage Product 2023 Priorities

@nickle

CryptoNet Lab: Storage Product 2023 Priorities

@nickle

FIPs

Storage Protocols

CryptoNet Lab: Storage Product 2023 Priorities

@nickle

Bifrost: 2023 Priorities

• Main Objectives:
• Keep our ipfs gateway running well - keep TTFB < 5s and five 9s uptime
• Improve our ipfs gateway performance - Decentilized CDN for lower latency
• Make our ipfs gateway better and ready to share our best practice to the community

​

• Key Milestones:
• Badbits denylist web service - Allow better collaboration and publishing of badbits lists and minimize disruption when deploying updates to the blocking service. Q4,2022
• AAP (ex Ansible Tower) - Bring a robust and stable process for deploying custom Kubo or ipfs-cluster builds to select servers as self-service. Q4, 2022
• Running Nomad - Enable scheduled deployment for Kubo, allows live config-reloads without a full deployment Q1,2023
• Saturn integration - More consistent and lower latency for IPFS gateways by integrating with the Saturn CDN. Q1,2023

@jesse

DAG House: 2023 Priorities

• Main objectives
• 📈Grow a ton, with 10% weekly (active, paid, overall) user growth from when pricing was introduced
• ⚛️Nucleate, building on top of the growth of the product, and have major loose ends tied off (e.g., sustainable plan for NFT.Storage)
• What are the key milestones your groups is pushing towards in 2023?
• 🏃‍♂️💨Offer fast reads of data stored on web3.storage through the w3link gateway at a low cost to us (est timeline: Dec 2022)
• 🤝Roll out UCAN-based APIs to the web3.storage and NFT.Storage products
• 📏Instrument metrics (esp. in w3up) we need to inform our efforts and grow effectively
• …?
• ⚛️Nucleation into an independent entity
• 🤝Consumption-based pricing + giving users the option to pay less to store cold data on Filecoin
• Whitespace (depends on market needs)
• Potential contenders: 😎Private data, 🤝integrations (e.g., Fission, Socket Supply), 🪣UCAN-based buckets, 💰cost optimizations, 🖥️UCAN-based compute interface

@dchoi

EngRes 2023 Strategy

FVM: 2023 Roadmap

@raulk

Prios:

​

1. Committed to shipping FEVM to mainnet on Feb 8th ‘23.

​

• Tighten the scope of M2.2 in Jan ‘23. Minimal, incremental, secure upgrades.

​

• Parallelized focus on Wasm developer experience. SDKs, IDLs, sandbox, etc. through community.

​

• Continued activation and support of dev communities through Foundry, hackathons, talks, scalable educational resources, forums, etc.�
• Hiring hiring hiring SWEs.�
• Be ready for upcoming protocol upgrades like IPC.

​

• Be ready for network breakthroughs like Retrieval Markets, CoD, and more.

FilCrypto: 2023 Priorities

• Delivering Halo2 to Filecoin Mainnet!
• zk-Snarks proving system developed by Electric Coin Company, developers of Zcash
• Eliminates trusted setup of current Groth16 proving system
• Halo2 will coexist alongside Groth16
• Q4 2022: Functional compatibility between Halo2 & Groth16, CPU + GPU accelerated, API available to begin Filecoin client integration
• Q1 2023: circuit optimizations + benchmarking, recursive proofs, FIP draft, code audits, refine API
• Q2 2023: Ship Halo2: Production quality, API finalized, FIP Approval
• Q3 2023: Halo2 circuit optimizations, L2/L3 applications, smart contracts, chain snapshot/bootstrap

@shawnrader

Consensus Lab: 2023 development roadmap

Basic Milestones and Priorities (IPC, EC)

Consensus Lab: upcoming IPC milestones

• M1 - Spacenet launch with Mir consensus framework and first BFT consensus (22Q4)
• A running Lotus-based testnet will enable users to experiment with Mir consensus, with support for FEVM actors. Dev teams will be able to early-test Mir consensus combined with FEVM and Lotus, sharing a single network with others.
• M2 - Interplanetary Consensus integration in Spacenet (23Q1)
• Applications will be able to deploy custom subnets on Spacenet and use them to meet new performance of functionality requirements. Applications like Saturn and Bacahlau can start experiment with their own subnets.
• M3 - IPC integration into mainnet Filecoin + ability to launch Mir-based PoS subnets (23Q3)
• IPC gets deployed into Fileocin mainnet, with full technical and cryptoeconomic models. It unlocks additional capacity and functionality, making it possible to run applications that are a poor fit for mainnet consensus (cost, latency, etc.)

Consensus Lab: 2023 research roadmap [WIP]

☺️ Familiar

Our users want to focus on great new solutions, not rebuilding things that already worked elsewhere. We must meet them where they are to bridge the gap and help them adopt Compute over Data. This means providing them tools and platforms that feel both familiar and better than their existing solutions.

🔒 Secure

Data being run on a Compute over Data network is often among the most important company’s have. We must meet and exceed our user’s security expectations. These include:

• Secure at Rest
• Secure in Transit
• Secure in Execution.

🪨 Reliable

Customers have high expectations for Compute over Data platforms about performance, uptime and completion of jobs. Beyond just ensuring a “number of 9s”, we must also deliver a platform that is stable from release to release, has stated upgrade and compatibility policy, and has been thoroughly tested for stated supported configurations.

🏷️ Best Price/Performance

Compute over Data platforms have price/performance ratios that are extremely well understood. For a given job, we must be able to meet or beat these measurements for the vast majority of use cases.

CoD Tenets 🏛️ - Bacalhau is:

@aronchick

CoD: 2023 Roadmap

@aronchick

End Users

Compute Providers

CoD: 2023 Roadmap

@aronchick

End Users

Compute Providers

CryptoEconLab, Layer 2 WG: 2023 Priorities

@maria

Main Objectives:

• Filecoin storage continues to grow in response to the creation of new use-cases and applications
• Build robust and safe markets capable of delivering fast retrievals of content stored on Filecoin
• Ensure compute markets are incentivized to deliver efficient computation over Filecoin

Key Milestones for next 6 months:

• Monitor incentives for Saturn L1 network [Retrievals] (1/2023)
• Explore strategies to decentralized Saturn incentives and enable L2 payments [Retrievals] (3/2023)
• Ship Atlas MVP and build community around geospatial data [Retrievals + Storage + Compute] (3/2023)
• Perform initial exploration of incentives design for Compute over Data [Compute] (1/2023)

CryptoNet Lab: Research & Compute 2023 Priorities

@nickle

CryptoNet Lab: Research & Compute 2023 Priorities

@nickle

FIPs

Medusanet.xyz

CryptoNet Lab: Research & Compute 2023 Priorities

@nickle

Applied Research

EngRes 2023 Strategy

@molly

👏

👏

👏

👏

👏

👏

👏

Thank you to all our presenters!

Closing Thank You’s

October 26th, 2022

Molly Mackinlay

@molly

👏

👏

👏

👏

👏

👏

👏

🍿 your thank you’s!

@molly

Meeting Rooms Day 2

@katalia

Room: Chiado I & II (Breakout Room #1+2)

Time: All Day

Team: ENGRES TEAM SUMMIT

​

​

Room: Chiado III (Breakout Room #3)

Time: 2-7pm

Team: CRYPTONET

​

​

Room: Lapa I (Breakout Room #4)

Time: 9am-2pm

Team: EngRes Team Breakout

​

Room: Castelo IV

Time: 2-4pm

Team: People Managers Sync

​

Room: Alfama II

Time: 2-5pm

Team: NetOps Team Summit

​

​

Room: Lapa II (Breakout room #5)

-Time: 9am-2pm

Team: EngRes Team Breakout

-Time: 2-7pm

Team: FilDev

​

Meeting Rooms Day 2

@katalia

ENGRES TEAM SUMMIT

ENGRES TEAM SUMMIT

CRYPTONET

NETOPS TEAM SUMMIT

-EngRes Team Breakout �-Bedrock

-EngRes

Team

Breakout �-FilDev

Unconfs

Reminder

Unconfs

Reminder - Launchpad

Located at The Vintage Hotel Lisbon

🥘 Lunch Break…

​

🖖EngRes People Managers - please be back in 1 hour

​

​

🗣Icebreaker Topic:

Who or what has made a positive impact in your life this year? How are you going to pay it forward?

​

​

People Manager Sync

October 26th, 2022

Steve Loeppky

Template Slide

EngRes Team Summit

Roadmap Presentations

October 25, 2022

​

EngRes Team Summit

Roadmap Presentations

October 25, 2022

​

​

Template Slide