Frequently asked questions.

Straight answers about Core 5.0, the Binance agreement, the supply, the Solar Card, and what happens now. Answers labelled FOUNDATION STATEMENT are the Foundation's account, presented for context and not yet independently confirmed; the other parties have not responded publicly. Where an answer is established by the published Token Swap Agreement, the clause is cited.

Core 5.0 & the agreement
Why couldn't Solar upgrade to Core 5.0?

Core 5.0 was roughly 90% through testnet — the barrier was never technical. Under the Token Swap Agreement, the Foundation could not change the mainnet (cl. 5b) or carry out any token/mainnet swap or integration (cl. 5c) without Binance's prior written consent. A new chain is exactly that kind of change, so Core 5.0 could not be deployed independently.

Binance's consent was, in the Foundation's account, conditioned on signing a new agreement that required cancelling the agreed monthly timelock and sending all remaining 18,000,000 SXP at once, accepting personal liability — and with no guarantee Core 5.0 would even be listed. See the full Core 5.0 breakdown →

Why didn't the Foundation just sign the agreement?

The terms were one-sided and personal. Solar and an individual would be jointly and severally liable (cl. 5e) and would indemnify Binance, while Binance's own total liability was capped at US$10,000 and Binance could terminate at any time without cause. In return there was no commitment to list or support Core 5.0. FOUNDATION STATEMENT

As the resignation statement put it, the request “looked polite on the surface but was structured in a way no reasonable person could sign.” Signing would also have meant breaking a community-protecting timelock — which the Foundation considered ethically wrong. Read the agreement →

What was the “timelock,” and why does breaking it matter?

A 2023 arrangement set a measured release of 31,200,000 SXP at 600,000 SXP per month (agreement §4). That monthly schedule — a timelock — protected the market and holders from a sudden flood of supply. By the later agreement's effective date, 13,200,000 SXP had been released and 18,000,000 remained.

The Core 5.0 terms would have cancelled that schedule and required all 18,000,000 SXP at once (cl. 5a). Abandoning a protection the community was relying on, in a single transfer, was something the Foundation was not willing to do. FOUNDATION STATEMENT

What were the conditions described as “non-negotiable”?

In the Foundation's account, the recurring non-negotiables were: Binance's consent required for any upgrade or swap; the treasury wallet treated as Binance's property; SXP utility and fees — including card processing fees — removed or withheld; personal liability on top of corporate liability; and acceleration of the remaining token release. Together they left no room to operate or innovate independently. FOUNDATION STATEMENT

Supply & treasury
What is the “duplicated” or inflated supply?

The verifiable part (on-chain). SXP began as a single ERC-20 on Ethereum with a 300,000,000 hard cap. Today, near-full SXP supplies exist in parallel across chains: the Ethereum contract holds ~285.4M (Etherscan); a separate “Binance-Peg” BEP-20 on BNB Smart Chain holds ~289.7M, with its supply hard-coded and no mint function, deployed 5 Oct 2020 — after Binance's July 2020 acquisition (BscScan); and the native Solar mainnet now reports ~684M (api.solar.org). The 2023 migration was lock-based, not burn-based — the EVM tokens were locked, not destroyed, and native SXP was minted 1:1 on top. So roughly ~575M SXP still exists on Ethereum + BSC alongside the ~684M native, even though the official line was that 480M would migrate 1:1 and “supply would not be increased.” Two near-full ~285–290M supplies, from a token that began as one 300M ERC-20, are the concrete basis for the “duplicated supply” concern. Every figure above is independently checkable on the explorers linked.

The Foundation's position (not independently confirmed). That this parallel BSC supply was created and distributed via Binance-operated infrastructure, and that the treasury sat outside the Solar team — as set out in the January 2026 Project Status Update. Binance has not publicly responded, and no independent forensic analysis has tied the BSC supply to specific Binance-controlled addresses. We present the on-chain facts and our interpretation; readers can verify and form their own view. FOUNDATION STATEMENT

One honest clarification: not all supply growth is “duplication.” Most of the 480M→684M increase is ordinary, disclosed Solar mainnet forging inflation (~39M SXP/year, no protocol cap) — routine block rewards, not minting from thin air. The duplication concern is specifically the parallel EVM supply described above.

Who controls the treasury?

Under the published agreement, the relevant wallet and the SXP held within it are stated to belong to Binance, with the Solar Parties holding no legal or beneficial ownership (cl. 5d). In the Foundation's account, this is a treasury that was originally meant to be the project's, and whose transfer was a condition of the 2022 mainnet support. See the agreement →

Why couldn't the Solar Card launch?

A ticker catch-22. Binance's position was that the SXP / “Swipe” intellectual property belonged to Binance, so the Foundation was not permitted to use SXP as the card ticker — but it was also not allowed to change the ticker. With neither option open, a compliant card product could not ship. FOUNDATION STATEMENT

Migration & Monolythium
Why not just force everyone to migrate to a new chain?

Because a forced migration would inherit Solar's legacy problems — everything tied to the Binance arrangements, including the disputed/duplicated supply. Importing those issues into a new network would simply move the problem, not solve it.

So instead of forcing anything, the Foundation proposed an optional, voluntary migration framework through governance — SXP-GOV-2026-01. It was non-binding and non-executing; it only sought permission to design such a framework for later review.

Was a move to Monolythium proposed — and what happened?

Yes. A voluntary, opt-in migration path was put to a validator vote (SXP-GOV-2026-01, 27–30 Jan 2026). It was rejected on quorum: 28 validators voted YES, 0 NO, 1 abstained — 100% approval among votes cast — but only 54.7% of validator voting power participated, below the 67% quorum required. Nothing was forced and nothing proceeded.

Is Monolythium the “new SXP”? Do holders get an airdrop?

No. Monolythium is a separate, independent project that inherits no Solar assets, governance, or obligations. SXP holders receive nothing automatically. Be wary of anyone claiming there is an airdrop or an official “migration” — none has been initiated, endorsed, or executed.

For holders & the network
Is the Solar network still running?

Yes — in maintenance-only mode. Block production continues through independent validators, and the Foundation maintains seed infrastructure on a best-effort basis. There is no active development team and no further protocol updates are planned. Live status →

Is my SXP safe? Can I still move or withdraw it?

Self-custodied SXP and the network continue to function; verify balances on Solarscan. Exchange support has narrowed — Binance ended SXP spot trading on 1 April 2026 — so use the remaining venues and always confirm the deposit network is Solar mainnet. This is not financial advice.

Why did Binance delist SXP?

Binance announced the delisting on 18 March 2026, with spot trading ceasing on 1 April 2026, citing its standard periodic review criteria. South Korean exchanges had delisted earlier (March 2025). See the timeline →

Why was the founder personally named in the agreement?

The agreement named an individual alongside the Foundation, with joint and several liability (cl. 5e) — i.e., personal exposure on top of the entity's. That personal-liability structure was one of the central reasons the agreement was not signed. See the agreement →

Why was the Foundation silent until now?

The arrangements were bound by confidentiality — the agreement's own terms are confidential. The Foundation carried that silence to avoid harming the parties involved. The decision to publish this record was made in the interest of transparency, accepting the associated risk, after extended public criticism made silence untenable.

Can someone else take over Solar?

Yes. Solar is open-source and remains open for any credible organization, foundation, or contributor better positioned to steward it. No Solar assets, code, governance authority, or infrastructure have been transferred to anyone. If your team is interested, contact [email protected].

This page is an information record published by The Solar Foundation. It is not financial, investment, or legal advice. Statements established by the published agreement cite the relevant clause; other statements are the Foundation's account, presented for context and not independently adjudicated. Nothing here is an accusation of wrongdoing by any party.
© The Solar Foundation ← Home