SAEP-05: Modify Delegate Framework - November 17, 2025

Spark's Operational Facilitator has placed a proposal into the voting system on behalf of nested contributor Phoenix Labs.

Review

The Spark community can hereby express support or opposition to the following changes, as described by the author of the proposal:

Summary

This proposal is submitted by Phoenix Labs in its role as a nested contributor as defined in Spark Artifact A.6.1.1.1.2.2.2.2.1.2.1.1.1. It recommends edits to the Spark Artifact to (1) authorize the Spark Foundation to onboard Delegates directly, (2) establish fixed six-month Delegate appointments administered by the Spark Foundation with mandatory re-approval or automatic offboarding at term end, and (3) introduce Delegate compensation. These changes simplify operations, clarify accountability, and ensure consistent resourcing of the Delegate function. The fixed-term & re-approval model begins January 1, 2026.

These changes update the following artifact sections:

• A.6.1.1.1.3.1.3.4 — Delegate Onboarding
• A.6.1.1.1.3.1.3.5 — Delegate Offboarding
• A.6.1.1.1.3.1.3.6 — Incentives & Compensation
• A.6.1.1.1.3.1.3.8 — Registry of Delegates

Background

Today, the Spark Artifact defines only a Bootstrapping Phase for Delegates (A.6.1.1.1.3.1.3.4.1) with application prerequisites (A.6.1.1.1.3.1.3.4.2), but it does not establish an ongoing, term-based appointment and renewal process, nor compensation (A.AG1.3.1.3.6 currently states none). As Spark transitions out of bootstrapping, this gap creates ambiguity around who appoints Delegates, when renewals occur, and how performance is reviewed and resourced.

This proposal replaces the temporary bootstrapping construct with a clear process for onboarding, fixed terms, mandatory re-approval at each term end with automatic offboarding absent re-approval, and standardized delegate compensation. The term structure begins on January 1, 2026, with all existing Delegates approved; the first term ends on June 30, 2026, with re-approval effective July 1, 2026.

Proposal Details

Delegate Onboarding Controlled by the Spark Foundation

• The Spark Foundation may onboard a new Delegate at its discretion.
• Minimum required inputs remain the same: Delegate wallet address; identity and contact information; signed acceptance of A.6.1.1.1.3.1.3.3 — Delegate Responsibilities.
• The Spark Foundation performs identity verification, collects conflict disclosures, and performs sanctions and undue risk checks.
• The Operational Facilitator updates the Registry of Delegates upon receipt of an onboarding notice from the Spark Foundation.

Delegate Fixed Terms, Renewal, and Start Date

• Beginning January 1, 2026, all Delegates are appointed to fixed six (6) month terms by the Spark Foundation.
• At each term end, a Delegate must be re-approved by the Spark Foundation to continue.
• If re-approval is not granted by term end, the Delegate is automatically offboarded.
• Term windows align to calendar half-years: Jan 1–Jun 30 and Jul 1–Dec 31.

Delegate Compensation

• Each Active Delegate is compensated USD 4,000 per calendar month.
• Compensation is administered by the Spark Foundation from its approved operating budget and paid monthly in arrears, prorated for partial months and subject to the Delegate remaining in good standing and meeting responsibilities in A.6.1.1.1.3.1.3.3 — Delegate Responsibilities.
• Compensation does not alter or waive any performance-related offboarding grounds.

Justification

• From bootstrapping to process. Converts a one-time bootstrapping setup into an immediate, ongoing appointment/renewal mechanism administered by the Spark Foundation.
• Predictable cadence with a clean cutover. Anchoring re-approvals to Jan 1 / Jul 1 establishes clarity while skipping Jan 1, 2026 avoids churn during transition; July 1, 2026 becomes the first checkpoint for everyone.
• Resourcing without complexity. A flat USD 4,000/month stipend supports sustained performance while preserving straightforward operations.
• Clear consequences. Automatic offboarding at the designated re-approval date if not re-approved prevents drift and maintains quality.

Conflicts of Interest

Phoenix Labs discloses no material conflicts of interest.

The proposed Spark Artifact changes can be found in the following pull request: https://github.com/sky-ecosystem/next-gen-atlas/pull/113

Outcomes

• If "For" receives the most votes, the proposal will be approved. The associated pull request will be merged into Spark's artifact. When required, the listed changes will proceed to implementation by the relevant actors.
• If "Against" receives the most votes, the proposal will be rejected. No changes will be implemented.