Solar

<h2 id="header-0">TL;DR</h2>
<ul>
 <li>Core 5.0: Built on proven Avalanche components—but not a clone. We’re integrating Solar’s Delegated Proof-of-Stake (DPoS) governance with Avalanche’s Snowman++ consensus for speed and reliability.</li>
 <li>Security: We identified and removed state-level threat actors discovered during the final audit phase of Tymt and Solar Card. No funds were lost, no user systems were affected, and no keys or private data were ever in danger.</li>
 <li>Products: Solar Card V3 (IBAN + bank transfers) is in its last audit; physical cards are already printed. Tymt v2.2.2 is live internally with 100+ playable titles.</li>
 <li>Governance: Ongoing discussions with Binance regarding the Swipe treasury wallet and card utility lost during the acquisition period.</li>
 <li>Foundation: The 5 % block-reward allocation will again be used for growth instead of burned.</li>
 <li>Community: We’re reviving social media and Telegram activity, starting with an AMA after testnet release and another after Solar Card launch.</li>
 <li>Cadence: Weekly Dev Diaries—what we solved, why it was hard, and what’s next. No timelines. Just proof of work.</li>
</ul>
<h2 id="header-1">Why We Chose an Avalanche-Class Foundation</h2>
Solar isn’t another copy-paste blockchain.
We’re taking the most reliable parts of Avalanche’s open-source framework—its audited, production-grade Snowman++ consensus—and combining them with Solar’s unique DPoS voting model.
This hybrid gives us sub-second finality and strong third-party auditability without losing the community governance that defines Solar.
We were close to finishing our own Core 5.0—written largely from scratch—but auditing something that original was enormously expensive and difficult. By adopting Avalanche’s proven consensus components, we gain:
<ol>
 <li>Reliability tested in real-world conditions.</li>
 <li>Lower audit costs and access to established audit partners.</li>
 <li>Cross-reference security with Avalanche’s active engineering teams.</li>
 <li>Performance parity with the fastest networks in existence.</li>
</ol>
It isn’t copying; it’s evolution built on solid engineering.
<h2 id="header-2">The Focus</h2>
Solar Core 5.0 fuses Avalanche-class performance with delegated voting governance.Token holders vote, and the top 53 by vote weight validate the network.
<h2 id="header-3">The Challenge</h2>
Avalanche assumes validators pre-stake before launch. Solar elects validators dynamically through on-chain voting. Our task is to make Avalanche’s consensus recognize vote-weighted validators in real time—without breaking its guarantees.
<h2 id="header-4">The Current Approach</h2>
We’re building a Validator Registry Bridge—a secure, pruning-safe middle layer that synchronizes vote data with consensus.
<ul>
 <li>Execution Layer (Solar-EVM/SVM): tracks candidates and vote weights.</li>
 <li>Consensus (SolarchainGo): runs Snowman++ and requires the active validator set.</li>
 <li>Bridge Layer: merges both into a deterministic registry resilient to reorgs.</li>
</ul>
<h2 id="header-5">Status</h2>
<ul>
 <li>Network boots and produces blocks.</li>
 <li>Connectivity thresholds and registry synchronization being tuned.</li>
 <li>Phase 0: genesis validator set.</li>
 <li>Phase 1: fully vote-driven validator rotation once registry validation is complete.</li>
</ul>
No promises—just progress.
<h2 id="header-6">The Security Incident</h2>
During the final audit—when Tymt and Solar Card were practically ready for release—our engineers discovered irregular backend behavior and overlapping logins from different developer accounts. The investigation revealed coordinated infiltration linked to Lazarus Group infrastructure.
Here’s what we found:
<ul>
 <li>Impersonation of developers to collect duplicate payments — one person working behind multiple “identities.”</li>
 <li>Links from backend systems to external addresses intended to monitor prices, validate information, and potentially redirect URLs.</li>
 <li>These changes were limited to backend code in Tymt, discovered during the audit phase before deployment.</li>
 <li>None of it went live — everything was caught in time.</li>
 <li>The backend has since been fully rebuilt with a new architecture, hardened access control, and enhanced code review policies.</li>
</ul>
Most importantly:
<ul>
 <li>No funds were lost.</li>
 <li>No user data, wallets, or systems were compromised.</li>
 <li>No private keys or transaction data were ever in danger.</li>
</ul>
This infiltration affected Tymt and, to a small extent, Solar Card through shared developers, but Solar Core 5.0 was never touched. It resides in a completely separate and isolated GitHub organization.
The discovery came after years of building—right before final audit and release. That’s what made it so painful.
<blockquote>
 You can’t imagine how it feels when you’ve spent years promising to deliver something. A product built with heart, with passion, with years of code and belief. To finally reach a point where it works—where it’s real—and then watch the final audit collapse under the weight of that discovery. The impact is intense. Unexplainable. But it didn’t end us; it sharpened us.
</blockquote>
We’ll publish a full threat report outlining the infiltration methods, forensic details, and how we secured every system moving forward.
<h2 id="header-7">The Human Side — Leadership and Limits</h2>
<blockquote>
 There’s a limit to how much any person can absorb, even the ones who believe they can take anything. For years I thought burnout was something that happened to other people. I saw myself as the entrepreneur who could fix every crisis, rally every team, and turn any situation around. But when you’re fighting constant setbacks, nearing completion, and suddenly discover state-level actors sabotaging your work—during the final audit—it shakes you. We were days away from celebrating a finished product when we uncovered the infiltration. The timing couldn’t have been crueler. That moment broke my pace. What followed was a high-functioning burnout—not giving up, but running on fumes. I kept going quietly, maybe too quietly, while trying to fix everything. This isn’t an excuse. It’s context. Because even at our lowest point, we never stopped. We audited, rebuilt, secured, and are now finishing what we started—with more resilience and clarity than before.
</blockquote>
<h2 id="header-8">Product Updates</h2>

<h3 id="strong-solar-card-v3-final-stretch-strong">Solar Card V3 — Final Stretch</h3>
<ul>
 <li>IBAN &amp; Bank Transfers: Fully integrated.</li>
 <li>Physical Cards: Already printed and with the supplier.</li>
 <li>Audit: In progress and running smoothly. Once complete, we move straight to release.</li>
 <li>Next Step: Final formalities and app-audit sign-off.</li>
</ul>
After launch, marketing ignites at full strength—real product, real momentum.
<h3 id="strong-tymt-the-launcher-strong">Tymt — The Launcher</h3>
<ul>
 <li>Internal v2.2.2 with 100+ playable titles.</li>
 <li>Proton compatibility, Steam linking, controller mapping ready.</li>
 <li>Streaming/casting layer underway for multi-screen play.</li>
 <li>Backend completely rebuilt following the audit, stronger and more scalable than before.</li>
</ul>
<h3 id="strong-solar-core-5-0-the-network-strong">Solar Core 5.0 — The Network</h3>
<ul>
 <li>Validator Registry Bridge integration ongoing.</li>
 <li>Health thresholds and consensus connectivity tuning.</li>
 <li>Weekly Dev Diaries will track each milestone.</li>
</ul>
<blockquote>
 Together, Solar Core 5.0, Solar Card, and Tymt form a complete, interoperable ecosystem—our own financial, gaming, and infrastructure triangle—each one powering the others.
</blockquote>
<h2 id="header-9">Treasury and Binance Discussions</h2>
Following community requests, we’ve opened active discussions with Binance about the Swipe treasury wallet and card utility that were lost during the acquisition phase.
Goals:
<ul>
 <li>Secure transparency regarding the treasury.</li>
 <li>Explore compensation or partnership frameworks benefiting Solar holders.</li>
</ul>
We’ll update you as soon as talks allow.
<h2 id="header-10">Foundation Funds and Marketing Return</h2>
By protocol, the Solar Foundation automatically receives 5 % of all block rewards. Historically these funds have supported development, operations, and marketing.
When marketing activities were paused, we chose to burn those ongoing foundation rewards instead of letting them accumulate.
Now that Solar Card V3, Solar Core 5.0, and Tymt are nearing completion, we are ending the burns and re-utilizing the foundation funds for their intended purpose:
<ul>
 <li>Scaling marketing and exchange outreach.</li>
 <li>Strengthening community campaigns and events.</li>
 <li>Funding integrations, partnerships, and global visibility.</li>
</ul>
The goal: push Solar back into the spotlight, climb CoinMarketCap rankings, and re-establish Solar as an industry-leading blockchain powered by real products and real progress.
<h2 id="header-11">Community Engagement and AMAs</h2>
We’re reigniting social channels and direct communication:
<ul>
 <li>Telegram &amp; X activity resumes with regular updates.</li>
 <li>AMA #1: right after the testnet release.</li>
 <li>AMA #2: following the Solar Card V3 launch and physical-card rollout.</li>
</ul>
Transparency and accessibility are the priorities going forward.
<h2 id="header-12">The Road Ahead</h2>
<ul>
 <li>Dev Diary #1: Validator-bridge + node-health report.</li>
 <li>Threat Report: full disclosure of infiltration findings.</li>
 <li>Solar Card V3: audit completion + launch.</li>
 <li>Marketing reboot + AMAs.</li>
 <li>Binance dialogue: updates when permissible.</li>
</ul>
No hype—just execution.
Solar Network isn’t fading. It’s evolving.We were blindsided in the final audit, took the hit, rebuilt stronger, and kept every product moving. The silence is over. The work speaks for itself now.
— Nayiem, CEO at Solar Network

Solar Network: Architecture Pivot, Security Lessons, and What’s Next

Table of Contents

Solar

Other articles published on Oct 27, 2025

Join our free newsletter for daily crypto updates!