Alina Schanz

Worked with · 03 of 12Layer 2offchain.io

Offchain Labs

I had a paid research collaboration with the Offchain Labs team around work connected to Arbitrum and Ethereum infrastructure.

Relationship
Worked with
Company
The company that builds Arbitrum
Format
Paid research collaboration
Area
Arbitrum and Ethereum infrastructure
My part
Research and technical analysis

A defined problem

The engagement was structured around a defined technical problem rather than broad ecosystem research. I spent time getting into the system itself, understanding the assumptions and constraints around the problem, and separating what mattered at the infrastructure level from what could be inferred from surface-level network or market metrics.

Fig. 1Two views of the same problem

  1. From the outsideNetwork metricsMarket metrics
  2. At the infrastructure levelImplementation constraintsDeveloper behaviorCompatibility requirementsThe wider Ethereum environment
What surface metrics suggest, and what decides the answer once you are inside the system.

The work

A large part of my role was research-driven. I worked through the problem from several angles, mapped the dependencies around it, tested the assumptions we were working with, and turned that analysis into findings that could be discussed with the team. The goal was to make the problem more concrete before moving further into product or technical decisions.

Fig. 2From an open problem to a decision

  1. 01Several anglesWorking through the problem
  2. 02DependenciesMapped around it
  3. 03AssumptionsTested
  4. 04FindingsDiscussed with the team
  5. 05DecisionsProduct or technical

Close to the builders

What I found particularly useful about working directly with Offchain Labs was the proximity to the people building the underlying infrastructure. Questions that look straightforward from the outside can become much more complicated once implementation constraints, developer behavior, compatibility requirements and the wider Ethereum environment are taken into account.

How they work

The work also gave me a better understanding of how Offchain Labs approaches technical collaboration. Their public work follows a similar research-first pattern: identify an open problem, define its scope carefully, analyze possible approaches, and use the results to inform architecture or product decisions.

Fig. 3Research first

  1. 01IdentifyAn open problem
  2. 02ScopeDefined carefully
  3. 03AnalyzePossible approaches
  4. 04InformArchitecture or product decisions

My part

This was a standalone paid collaboration with the team. My contribution was centered on research, technical analysis and turning an open-ended infrastructure problem into something specific enough to reason about and use in further decision-making.

Fig. 4Open-ended to specific

Open-endedSpecific enough to decide

Schematic, not data

An open-ended infrastructure problem, narrowed until it is specific enough to reason about and decide on.

Materials

Public pages about the company and the programs around this work.

Offchain Labs on Medium Tandem Partner Studio The announcement of Tandem, the partner studio of Offchain Labs.