Enter your search text in the box above

Select a result to preview

202602241600-phoenix-labs

#org #system

🎯 Core Idea

Phoenix Labs is a research and development company focused on building decentralized finance products, with an emphasis on smart contract development. Phoenix Labs presents itself as an R&D company specializing in DeFi protocol development, and lists Spark Protocol (a DAI-centric lending protocol) as featured work.

In the Sky and Spark ecosystem framing, Phoenix Labs is a core contributor to Spark. Spark governance documentation explicitly lists nested contributors such as Phoenix Labs as eligible proposers for governance proposals.

Historically, Phoenix Labs was onboarded in Maker governance as an Ecosystem Actor with the goal of delivering Spark Protocol and maintaining it for 12 months. The Maker governance poll lists the intended team composition as business development, smart contract development, and developer relations.

Phoenix Labs is also described in Sky Fusion as an Ecosystem Actor created to introduce new decentralized products into the Maker ecosystem, with the idea that Maker governance administers smart contracts and can adjust parameters via polls. That page also notes an intention that Spark Protocol could transition to a Creator subDAO model once established.

One visible public member is Sam MacPherson, described as co-founder and CEO of Phoenix Labs. Public profiles also connect his prior experience to MakerDAO protocol engineering and his ongoing contributions to Spark.

How to interpret Phoenix Labs in practice

🌲 Branching Questions

➡ What is Phoenix Labs’ formal relationship to Spark and Sky (Ecosystem Actor, nested contributor, any stated responsibilities)?

Phoenix Labs appears in multiple places with slightly different labels:

A practical way to summarize the relationship is that Phoenix Labs is positioned as a core builder and maintainer for Spark, with governance-recognized status and an explicit link to the broader Maker or Sky ecosystem governance processes.

➡ What are Phoenix Labs’ concrete deliverables for Spark (what they built or maintain, and what does maintain mean in practice)?

The clearest formal deliverable statement comes from Maker governance onboarding: deliver Spark Protocol and maintain it for 12 months.

Public descriptions of the build include:

Maintain in practice usually includes:

If you want to evaluate maintenance quality, the signals are: frequency of protocol updates, incident response quality, and how changes are documented and routed through governance.

➡ What does Spark governance documentation imply about Phoenix Labs’ privileges and role as a nested contributor?

Spark governance documentation says proposals must be submitted in the Spark Prime section of the Sky forum and only eligible proposers can submit proposals. It lists two eligibility categories:

This implies nested contributors have elevated governance participation compared to ordinary community members who do not meet the token threshold. At the same time, the process still requires reviews and community voting:

So the privilege is about proposal submission access, not unilateral control.

➡ What does Maker governance say about Phoenix Labs’ onboarding, scope, and staffing structure over time?

The Maker governance poll for onboarding Phoenix Labs as an Incubating Ecosystem Actor provides a compact snapshot:

It also describes what happens if the poll passes: recognition as an Incubating Ecosystem Actor and inclusion in an upcoming executive vote.

This tells you Maker governance treated Phoenix Labs as a structured, funded delivery team rather than an informal volunteer group.

➡ Who are publicly identified Phoenix Labs members (names, background, roles), and what has each contributed to Spark and Sky?

Public information about individual members is limited.

The most visible named individual in public sources is Sam MacPherson, described as co-founder and CEO of Phoenix Labs. Decrypt also describes Phoenix Labs as being led by protocol engineer Sam MacPherson.

Outside of Sam MacPherson, the Maker governance onboarding poll lists functional roles rather than names. That suggests an intended team shape, but not a public roster.

If you want a reliable list of members, the highest-signal sources are likely:

➡ What is Sam MacPherson’s background and what has he publicly said about Spark and Phoenix Labs’ role?

Blockworks describes Sam MacPherson as co-founder and CEO of Phoenix Labs and associates him with MakerDAO protocol engineering.

In Decrypt’s coverage of Spark Lend and Phoenix Labs:

These statements are useful because they clarify a governance ownership boundary: Phoenix Labs builds and maintains, but governance owns and can ratify changes.

➡ How does Spark Lend relate to Aave v3, and what is the stated revenue-sharing arrangement involving Phoenix Labs?

Multiple sources describe Spark Lend as being built on Aave v3:

Sky Fusion describes a revenue-sharing agreement facilitated by Phoenix Labs. It states Phoenix Labs proposed a profit-sharing program allocating 10 percent of gross profits from DAI borrowings within Spark Lend to Aave.

The Aave governance forum post authored by the PhoenixLabs account provides specific implementation details:

This arrangement is a concrete example of how Phoenix Labs positions Spark as building on open-source primitives while creating explicit economic alignment with upstream protocol communities.

➡ How does the Creator subDAO transition idea affect Spark and Phoenix Labs’ long-term position in the ecosystem?

Sky Fusion’s Phoenix Labs page states that once the Creator subDAO model is established, Spark Protocol can be transitioned to one of them.

The Defiant frames Spark Protocol as a product of Maker’s broader restructuring plan into multiple subDAOs.

If Spark transitions into a Creator subDAO structure, it likely changes:

The practical question is whether Phoenix Labs remains a core builder within the new structure, or whether its responsibilities are partially absorbed by a dedicated Spark subDAO organization.

📚 References