Solar November 2025 - Update #1

Project Status

This week’s focus centered on two main fronts: continued progress on Solar Core 5.0 development and active communication with Binance regarding the SXP treasury wallet and other long-standing matters following the Swipe acquisition. As many in the community know, concerns have grown over monthly transactions from the treasury wallet while the total SXP supply increased from about 289 million to 520 million during Swipe’s 2021 duplication. Much of this supply was distributed on the Binance platform. Holders have long believed the treasury was intended for ecosystem growth, marketing, and team development, not for external custody.

Lack of clear communication about the card-processing-fee promises and the silent transfer of the treasury wallet during Binance’s full acquisition of Swipe has left open questions for both holders and other exchanges reviewing SXP’s history. Many want to understand what happened to the original commitments and why the treasury funds were absorbed without a public statement from Swipe, Binance, or Solar. At that time, several agreements were accepted in order to ensure mainnet support and listing, even as expected development funding and partnership integration were never realized. Later, after the team secured limited resources to keep the project going, we were informed that the Solar.org domain would need to be purchased independently for approximately USD 1 million—another challenge for a project already without treasury access.

We understand the community’s frustration and agree that transparency is essential. We are now in open and constructive dialogue with Binance to clarify these matters, align on facts, and establish a balanced framework for the future. Development continues on schedule while these talks progress.

Solar Card V3 Testing

The Solar Card V3 update has now been pushed to testing on Android and iOS. Existing users have received notifications to update the app and sign in again. This version introduces IBAN account functionality, allowing users to make and receive bank transfers.

Once the testing phase is complete, we will proceed with the full V3 release to enable IBAN access for all users. The following stage will activate new components within the app, including support for physical Solar Cards.

Solar Core 5.0 - Code Changes

• •
  Implemented Solar consensus engine with validator management at round boundaries
• •
  Replaced Avalanche codec with JSON serialization in ValidatorDB for improved debugging visibility
• •
  Configured pebbledb to align with Avalanche’s memory-first state-management approach
• •
  Adjusted validator-update mechanism for static-validator testing phase
• •
  Modified genesis block generation to include the active validator set at initialization
• •
  Restored asynchronous block-acceptor queue for state-commit processing
• •
  Refined windower configuration to isolate network-timing behavior
• •
  Integrated debugging instrumentation for state-availability tracking
• •
  Streamlined validator-update mechanism by disabling round-boundary transitions during static-validator testing
• •
  Optimized state-persistence pipeline aligning pebbledb configuration with Avalanche’s memory-first architecture
• •
  Enhanced block-production timing confirming 2-second empty-block generation
• •
  Refined consensus-engine selection using a lightweight dummy engine during development
• •
  Implemented targeted debugging instrumentation in vm.go for state-availability tracking

Architectural Progress

• •
  Established ValidatorDB as the bridge between infrastructure and consensus layers (without P-Chain)
• •
  Documented bootstrap block-insertion patterns and validator-update requirements
• •
  Validated compatibility between Avalanche’s acceptor pattern and Solar’s modular architecture
• •
  Deployed dummy consensus engine for development testing phase
• •
  Confirmed timer-based block production maintains 2-second intervals without transactions
• •
  Separated execution-layer validator state from consensus-layer management
• •
  Validated vanilla Avalanche compatibility in core components (genesis.go, blockchain.go)
• •
  Confirmed timer-based block production operates independently of the transaction mempool

Key Discoveries

• •
  Located state-dereferencing behavior at block height 38 when StateHistory = 32 attempts to process block 6
• •
  Mapped trie-persistence lifecycle through a 4096-block memory cache before disk commit
• •
  Distinguished between HasState() disk checks and StateAt() memory-cache queries
• •
  Traced validator flow from infrastructure through ValidatorDB to consensus layer
• •
  Identified codec-manager behavior across module boundaries in Go replace environments
• •
  Documented asynchronous state-commit patterns in the execution layer
• •
  Found versioning mechanism in StoreRoundBoundary affecting deserialization
• •
  Pinpointed block 38 state-dereference issue under StateHistory = 32
• •
  Fully mapped state-persistence lifecycle from memory cache through 4096-block commit interval
• •
  Cataloged integration points requiring Solar-specific modifications

Summary

Development on Solar Core 5.0 continues to advance quickly, with major progress on consensus-layer stability and validator management. At the same time, the team has entered open discussions with Binance to bring clarity to community concerns about the treasury wallet, card-fee commitments, and legacy acquisition issues.

These conversations are constructive and ongoing. Together with the rollout of Solar Card V3 and preparations for the new mainnet, they mark the next phase in Solar’s mission to build a transparent, community-driven ecosystem backed by real-world utility.