Optional Migration Framework & Transition Process

Proposal ID: SXP-GOV-2026-01

This is an archived, read-only record of the governance vote. Voting ended 30 January 2026.
This is a signaling vote and is non-binding unless formally adopted through additional governance processes. The results represent validator sentiment only.
CLOSED
Voting Closed
30 Jan 2026, 09:00 UTC
Proposal REJECTED (quorum not reached)

Vote Tally

28
YES
47.28M SXP
0
NO
0.00 SXP
1
ABSTAIN
1.62M SXP
24
NOT VOTED
40.42M SXP
Quorum (67% required) 54.7% NOT MET
Approval (67% required) 100.0% MET

Voting Period

Start Time27 Jan 2026, 09:00 UTC
End Time30 Jan 2026, 09:00 UTC
Snapshot Height15,111,674
Total Validators53
Total Voting Power89.31M SXP

Vote Method

Validators signaled by sending exactly 0.00000001 SXP to:

Sdao2USyAz9B6RBgZeFyNDePuQAxfzZZHE

With one of these exact memos:

  • YES MONO-PROPOSAL:YES
  • NO MONO-PROPOSAL:NO
  • ABSTAIN MONO-PROPOSAL:ABSTAIN

SXP Governance Proposal

Optional Migration Framework & Transition Process

Proposal ID: SXP-GOV-2026-01
Status: Validator & Community Signaling Vote (Non-Binding, Auditable)

Voting Window: 72 hours
Start: 27 January 2026, 09:00 UTC
End: 30 January 2026, 09:00 UTC


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.

This proposal is introduced to address governance clarity and future direction in a structured manner.


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

A clean-slate Layer-1 architecture enables delivery of functionality and utility that is difficult to achieve under the current structure.


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

These principles are intended to protect users and exchanges alike.


6. Governance & Voting Method

This proposal uses an on-chain signaling vote by active validators.

Voting Method

Validators signal their vote by sending an on-chain transaction during the voting window:

  • Amount: exactly 0.00000001 SXP
  • To Address: Sdao2USyAz9B6RBgZeFyNDePuQAxfzZZHE

Memo (required, exact match)

  • MONO-PROPOSAL:YES
  • MONO-PROPOSAL:NO
  • MONO-PROPOSAL:ABSTAIN

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: YES ≥ 67% of (YES + NO) voting power
    (ABSTAIN excluded from 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 will 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 will 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 are 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)

Validator Votes (29 / 53)

Rank Validator Address Voting Power Vote Transaction Time (UTC)

Proposal Integrity

Anchored On-Chain ✓

Proposal Hash

Proposal IDSXP-GOV-2026-01
CanonicalizationRFC8785-JCS
Hash AlgorithmSHA-256
Proposal Hash2e43956672c6dda1c2066335a60a025be6aa364555eaf29f3996d5432c5e2295

Anchor Transaction

Transaction IDb8f80f27d9228473acf370f5c2f69b0437344ad97bcfea75924ec2f71bca267a
Block Height15,111,836
Timestamp (UTC)2026-01-26T12:15:12.000Z
From AddressSdao2USyAz9B6RBgZeFyNDePuQAxfzZZHE
MemoSXP-GOV-2026-01|SHA256|2e43956672c6dda1c2066335a60a025be6aa364555eaf29f3996d5432c5e2295
Hash in Memo2e43956672c6dda1c2066335a60a025be6aa364555eaf29f3996d5432c5e2295
Hash Verified✓ Matches computed hash

Independent Verification

Anyone can independently verify the proposal integrity:

  1. Download the original proposal.json from the source repository
  2. Compute 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 on Explorer Source Code