solar.org / governance / SXP-GOV-2026-01
ARCHIVED · READ-ONLY Migrated here from proposals.solar.org. Voting closed 30 Jan 2026, 09:00 UTC. This was a non-binding validator signaling vote.
Rejected — quorum not reached

SXP-GOV-2026-01 — Optional Migration Framework & Transition Process

A validator and community signaling vote on whether to authorize the design and formalization of an optional, voluntary migration framework. The proposal was supported by every validator who voted, but too few validators participated to meet the 67% quorum, so it did not pass.

SUBMITTER
Nayiem Willems — on behalf of former Solar contributors and validator participants
VOTING WINDOW
27–30 Jan 2026 · 72h
SNAPSHOT HEIGHT
15,111,674
ELIGIBLE VALIDATORS
53
VOTING POWER
89.31M SXP
VOTE TYPE
Signaling · non-binding
Passing rules
Quorum required≥ 67%
participation 54.7% — below threshold
Approval required≥ 67% of YES+NO
approval 100% — met (ABSTAIN excluded)
The proposal cleared approval decisively but failed quorum: 29 of 53 validators cast a vote within the window. If quorum or approval is not met, the proposal is automatically rejected.
Tally 29 / 53 validators
OPTIONVALIDATORSVOTING POWER
YES2847.28M
NO00.00
ABSTAIN11.62M
NOT VOTED2440.42M
QUORUM (67% REQ)
54.7% not met
APPROVAL (67% REQ)
100% met
Vote method

Validators signaled with an on-chain transaction from their operator address during the voting window. One vote per validator; the first valid vote counts. Votes outside the window were ignored.

SEND 0.00000001 SXP TO
Sdao2USyAz9B6RBgZeFyNDePuQAxfzZZHE
EXACT MEMO
MONO-PROPOSAL:YES MONO-PROPOSAL:NO MONO-PROPOSAL:ABSTAIN
Full proposal text

Optional Migration Framework & Transition Process

Proposal ID SXP-GOV-2026-01 · Validator & Community Signaling Vote (Non-Binding, Auditable)
1. Executive summary

This proposal seeks validator and community approval to proceed with the design and formalization of an optional, voluntary migration framework for Solar (SXP) holders.

Solar remains operational; however, forward protocol development has slowed due to long-standing structural and technical constraints. Contributors and validators have requested a clear, orderly, and transparent path forward that prioritizes user protection, governance, and long-term sustainability.

This proposal does not execute a migration, does not change token economics, and does not force any user action. It authorizes only the next procedural step: formalizing and publishing a complete migration framework for review.

2. Current state of Solar
  • Solar (SXP) is operational and its ledger remains intact.
  • No protocol upgrades or supply changes are planned during this proposal period.
  • No forward-looking development roadmap is currently active.
  • There are no changes to user balances, validator state, or consensus rules.
3. Rationale

Over time, Solar's development velocity has become constrained by architectural limitations and unresolved structural dependencies. While the network itself is not stagnant, progress has been slower than contributors and validators consider sustainable. Key drivers for this proposal include:

  • Desire for clearer governance and accountability
  • Need for faster iteration and broader application support
  • Community demand for a credible forward path
  • Preservation of user trust through a transparent process
4. Scope of this proposal

This proposal requests approval to:

  • Proceed with the design, documentation, and publication of an optional migration framework
  • Continue testnet development and public testing of the new network
  • Prepare migration tooling, documentation, and security audits for review

This proposal does not:

  • Execute a token swap
  • Modify Solar's supply
  • Force participation
  • Bind exchanges or custodians
  • Commit to a final migration timeline
5. Migration principles (non-negotiable)

Any future migration framework must adhere to the following principles:

  • Optional and user-initiated
  • 1:1 ratio — no inflation, no dilution
  • No duplicated supply
  • Transparent eligibility rules
  • Audited tooling and infrastructure
  • Clearly defined migration window
  • Exchange participation is optional
6. Governance & voting method

This proposal uses an on-chain signaling vote by active validators (see the vote-method card above). Rules:

  • Votes must originate from the validator operator address
  • One vote per validator (first valid vote counts)
  • Snapshot of the active validator set is taken at proposal start
  • Votes outside the voting window are ignored

Passing criteria: quorum ≥ 67% of total active validator voting power participates (YES / NO / ABSTAIN); approval ≥ 67% of (YES + NO) voting power, with ABSTAIN excluded from the approval calculation. If quorum or approval thresholds are not met, the proposal is automatically rejected.

7. Outcome if proposal passes

If approved, the following steps would occur:

  1. Publication of the full migration specification
  2. Release of the whitepaper and detailed roadmap
  3. Completion and publication of security audits
  4. Public testing of migration tooling
  5. Announcement of proposed timelines
  6. Separate governance approval prior to any execution

No migration would occur without further explicit approval.

8. Outcome if proposal fails

If rejected:

  • No migration framework will be pursued at this time
  • Solar remains unchanged
  • No token actions occur
  • Contributors may continue independent work outside Solar
  • A future proposal may be introduced after further review
9. Risk disclosure
  • Market volatility may continue during the governance review period
  • Exchange participation is voluntary and independent
  • Technical risks are mitigated through audits and phased testing

This proposal is designed to reduce risk through process, not accelerate execution.

10. Conclusion

This proposal represents a governance-first, community-led approach to addressing Solar's future direction. It prioritizes transparency, user protection, and validator participation over unilateral action. All participants were encouraged to review the proposal carefully and vote according to their assessment.

Submitted by Nayiem Willems — on behalf of former Solar contributors and validator participants.
Integrity & anchoring
ANCHORED ON-CHAIN ✓

The proposal's canonical JSON (RFC8785-JCS) was hashed with SHA-256 and anchored on-chain. The hash recorded in the anchor transaction's memo matches the computed hash.

PROPOSAL HASH · SHA-256
2e43956672c6dda1c2066335a60a025be6aa364555eaf29f3996d5432c5e2295
Block height
15,111,836
Timestamp (UTC)
2026-01-26T12:15:12.000Z
From address
Sdao2USyAz9B6RBgZeFyNDePuQAxfzZZHE
Memo
SXP-GOV-2026-01|SHA256|2e43956672c6dda1c2066335a60a025be6aa364555eaf29f3996d5432c5e2295
Hash verified
✓ Matches computed hash
Independent verification
  1. Download the original proposal.json from the source repository.
  2. Compute the SHA-256 hash of the canonical JSON: openssl dgst -sha256 SXP-GOV-2026-01-canonical.json
  3. Compare the hash with the one displayed above.
  4. Verify the anchor transaction memo contains the same hash on Solarscan.
View signaling wallet on Explorer ↗ Source code (proposal.json) ↗ Outcome announcement ↗
Archived from proposals.solar.org · Last reviewed 2026-06-20
© The Solar Foundation · Maintained for transparency and continuity.
[email protected]