Solana Classic is a fresh SVM ledger aimed at art, NFTs and memes

A chain with a mission and one validator

Solana Classic is described as an open-source blockchain putting meme and NFT communities at the centre of its products and roadmap, with the stated goal of building an open development community focused on how far art, NFTs and memes can go. The project says it is bringing together developers, artists and communities who care about this category so that its future gets sustained attention and focused development.

The project page lists the pieces, a website, a story page, a playground, a live roadmap, a whitepaper and a developer page, and the repository is MIT licensed with Rust as the primary language. The last push was on 2026-10-18, and there are no GitHub releases.

What is running today is stated without hedging. Devnet is live, and the Solana Classic team currently runs its single validator, described as the computer that checks and records transactions. One validator means a devnet you can use for experiments and a chain that is not a distributed system in any meaningful sense yet. The README is explicit on that point as well, since the mainnet and the proposed one to one bridge are not live, and tSOC on devnet is a separate test asset with no monetary value or conversion rights.

The project also states it has no affiliation to the Solana Foundation.

The README spends a lot of space on what it does not promise

That candour is the distinguishing feature of the document, and it is worth reading in order because the disclaimers are unusually specific.

A blockchain cannot guarantee honest teams or successful projects, and the commitment is to sustained focus and work that people can inspect. Many technical tools can already be built on Solana, and Classic's purpose is an independent development direction dedicated to this category, rather than a claim that every improvement requires a new chain. The underlying SVM can still run other applications, while the ecosystem priorities stay focused on this category. And on the proposals, the README says the products should emerge from the developers, artists and communities who show up and build, that the playground is a first place to experiment and this repository is an open place to contribute, and that the proposed disclosure and funding ideas in the whitepaper are contributions to that discussion and not delivered features.

Read as a whole, the position is that a community is what chooses a chain's priorities, not that a new chain is technically necessary. The historical comparison the README draws makes the same point with two precedents.

The disagreement that produced the chain

The project's origin is a specific public disagreement, and the README quotes it directly. On 27 July 2025, Solana co-founder Anatoly Yakovenko wrote that memecoins and NFTs are digital slop and have no intrinsic value, and the README links the original post and contemporaneous reporting, and notes that he also compared them with mobile-game loot boxes.

The README's reading of that exchange is that it made a cultural gap visible, and that the creativity, shared identity and relationships the community came for deserve to be taken seriously. It wants a place where those participants feel supported through the tools, funding priorities and continuing work around them.

The mission statement that follows is narrower than the quote invites. The project says that belief does not make every token valuable, and gives it a reason to build better tools and expect more from the people launching projects, with its own products and ecosystem priorities focusing on art, NFTs, memes and their communities. The longer argument lives in the whitepaper, under a section titled a focused home for memes and NFTs, and the README links to that document in the repository.

For a reader deciding whether to pay attention, the useful detail is the context. The disagreement is about where the Foundation's public-facing agenda points, with capital markets named as part of it, and the answer is to build elsewhere.

A fresh ledger, not a fork of Solana

The README's comparison table sets three projects side by side, and the third row is the one that matters for evaluating the technical claim.

Bitcoin Cash is described as the outcome of Bitcoin's scaling debate leading to a chain split in 2017, with the community choosing to keep everyday electronic payments affordable through more on-chain capacity. Ethereum Classic is described as participants rejecting the ledger intervention following the DAO hack in 2016, with the community choosing to continue the original chain without that intervention. Solana Classic is framed as wanting memes and NFTs to have a consistent place at the centre of the roadmap, bringing together developers, artists and communities focused on the future of art, NFTs and memes.

The README then draws the distinction that matters, saying the inspiration is a community choosing what its network should stand for, and that the technical histories are different. Bitcoin Cash and Ethereum Classic diverged from existing ledgers, while Solana Classic starts with a fresh independent ledger using Solana's open-source engine. It does not copy Solana balances, transfer existing NFTs automatically, or give SOL holders a claim to SOC.

So the honest description is a new chain, not a fork, built on the same virtual machine. The name and the SVG engine lineage are shared with Solana, the state and the token are not.

The token, the devnet asset and the bridge that is not live

The token section is short and its caveats are the point. The official token contract address on Solana mainnet is given as:

Nuhksmxq3AZ6ZrzVHshKnQd8QTTRSXCb7a6AU7oMsoc

with links to view SOC on Solscan and a token details page on the project site.

The caveat follows immediately. Solana Classic mainnet and the proposed one to one bridge are not live, and tSOC on devnet is a separate test asset with no monetary value or conversion rights. So there are two distinct things in the README, a mainnet contract address for a token whose mainnet is not live, and a devnet test asset that explicitly carries no value.

For anyone evaluating the project, the honest question is what a bridge would mean when it is not the same thing as the automatic transfer of existing NFTs. The README is clear that it is not: Solana Classic does not copy Solana balances, does not transfer existing NFTs automatically, and does not give SOL holders a claim to SOC. A project described this way starts from zero, and every asset on it has to be created on it.

A monorepo with the operations tooling in it

The repository is large for a project at this stage, and the top level explains why. There are `apps/` and `packages/` for the pnpm workspace, `engine/`, `bridge/`, `mainnet/`, `wallet/`, `config/`, `infra/`, `developers/`, `docs/`, `evidence/`, `roadmap/`, `scripts/` and `tests/`, plus `CONTRIBUTING.md`, `SECURITY.md`, `THIRD_PARTY_NOTICES.md` and a `vercel.json` with a `playwright.config.ts`.

The package manifest shows what the team considers worth automating. The scripts cover a development entry point through `tsx scripts/dev.ts`, separate web and API development, a web build, linting, type checking, unit, integration and end to end tests, and then a set of operational checks with telling names: `doctor`, `chain:smoke`, `ops:restart-check`, `ops:backup-check`, `ops:atomic-check`, plus `test:load` and `test:soak`. There are release scripts as well, `release:check` and `release:packet`.

The stack is modern and pinned hard: Node 24.x, pnpm 10.34.7, TypeScript 5.9.3, tsx 4.23.15, vitest 5.0.4, Playwright 1.64.0 and eslint 10. The runtime dependencies are small, `@solana/web3.js` at 1.99.0 plus two internal workspace packages, `@solana-classic/config` and `@solana-classic/chain`, with a text encoder package that looks like a Web3 polyfill.

A chain project that ships restart checks, backup checks, load tests and soak tests in the same repository as its client is treating itself as infrastructure, which is the right instinct and a fair amount of work.

Editorial conclusion

Adopt Solana Classic if you want to experiment on a devnet built for a specific community, and if you are comfortable with a chain that has one validator, no live mainnet and no announced bridge. Do not adopt it for anything that needs mainnet tokens, existing NFT balances or a bridge from Solana, since the README says plainly that the mainnet and the proposed one to one bridge are not live and that there is no automatic transfer of NFTs. Verify first what is running today, namely the devnet and its single validator, what the playground wallet does, and what the disclosure and funding ideas in the whitepaper mean for a builder, since the project states they are contributions to a discussion and not delivered features.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. solana-classic/solana-classic on GitHub