Guide

Litecoin forks explained: code ancestry, chain splits and AuxPoW

A source-led history of selected Litecoin relationships: code derivatives, later rebases, ledger inheritance and merged mining, with corrected dates and explicit evidence limits.

Litecoin forks explained: code ancestry, chain splits and AuxPoW
On this page

Dotted-underlined terms open a quick definition. Close it to keep reading.

“A fork” can mean a project that reused Litecoin code, a competing chain sharing Litecoin's earlier ledger, a change in algorithm or an auxiliary relationship. Those events have different consequences for balances, validation and security. Treating them as one complete family tree produces misleading dates, unsupported ancestry and imaginary supply changes.

This is a source-led guide to selected relationships, not a census of every project derived from Litecoin. It replaces the previous “complete family tree” and “95% died” claims with linked project records, a dated timeline and explicit limits. Current market-cap rankings, “dead” labels and allegations about individual projects are not carried forward without the evidence needed to establish them.

Four different events are often called a fork

Classify the relationship before drawing an arrow
EventWhat changes?What does not follow automatically?
Code derivativeA project reuses and modifies source codeShared transaction history, balances or mining work
Chain splitTwo histories share a ledger up to a boundary and then divergeContinued equivalence of the new units, rules or security
Algorithm transitionA network changes the accepted proof-of-work constructionA new independently traded asset or copied holder balances
Auxiliary proof of workA chain accepts a supported proof using compatible parent workOne common ledger or identical block-acceptance targets

There is also an ordinary temporary competition between valid chain tips, after which follow the valid chain with the appropriate accumulated work. That can cause a reorganization without creating a separately supported currency. Our consensus guide explains that chain-selection case.

A software rule change is another layer of description. “” can refer to incompatible ; a durable market split additionally requires people and infrastructure to keep supporting different histories. Neither a GitHub repository copy nor an edited ticker proves that such a split happened.

Litecoin's 2011 dates describe different milestones

The founder's announcement thread starts on 9 October 2011. A separate 12 October launch notice schedules the public start for 13 October at 03:00 GMT. The first post was later edited, so its current body should not be treated as an untouched copy of everything readers saw on the initial publication date.

The reviewed mainnet genesis construction uses timestamp 1317972665, corresponding to 7 October 2011 at 07:31:05 UTC. A timestamp encoded in a genesis header, a code publication, an announcement and a public mining start are different events. The earlier article collapsed them into one “launched on October 7” claim.

Litecoin is a Bitcoin-derived implementation with different proof-of-work and issuance parameters. This revision does not repeat the unsupported claim that its 2011 launch was based on Bitcoin Core 0.6. Pinning the precise early upstream code revision requires contemporaneous repository evidence; a modern repository's ancestry is not enough to backdate a later release.

For the present protocol mechanics, the Scrypt guide and integer subsidy schedule link the reviewed code. Their modern parameters do not establish what every early derivative inherited at its launch.

Selected relationships supported by the linked records

Different relationship types; no current project-health or valuation ranking
Project or releaseSupported relationshipEvidence and boundary
FeathercoinThe project's account describes development from LitecoinProject history and NeoScrypt description; not an independent chain-health test
Luckycoin Client 1.0.1The historical README describes a Litecoin-derived client with random bonus blocksHistorical repository; not a claim about all later code revisions
Dogecoin Core 1.10.0The project documents a 2015 rebase onto Bitcoin with Litecoin changes reappliedDogecoin's development account; not a new Dogecoin ledger in 2015
Litecoin CashThe project states a Litecoin ledger split at height 1,371,111 on 18 February 2018Launch description, including a 10:1 distribution ratio; project account, not a fresh node reconstruction

The rows intentionally do not all mean “direct fork of Litecoin's latest code.” They preserve which kind of evidence supports which relationship. A project statement can establish what its authors describe; verifying exact shared commits or reconstructing a chain boundary is a further task.

Many additional names appeared in the earlier table. Removing an unsupported status or valuation for one of them is not a finding that the project succeeded, failed or never existed. It means this revision has not assembled enough project-specific evidence to publish that judgment. A selective, evidenced map is more useful than a purported complete list with incompatible definitions.

Code history is a versioned graph, not one permanent parent label

A project can begin from one implementation, import a component from another and later rebase its maintenance branch onto a newer upstream. Its can continue while the implementation history changes. Repository hosting adds another complication: a GitHub “forked from” badge reflects that repository's hosting relationship, not a complete reconstruction of a currency's technical origins.

Luckycoin provides a concrete example. The old Client 1.0.1 README describes a Litecoin-derived client. A much later Luckycoin Core 5.0.0 release description says its code builds directly on Dogecoin Core 1.14.9. Those statements concern different versions. They cannot be reduced to one timeless arrow or used to conclude that the later upstream must have existed before the older client.

Draw nodes as named releases or revisions and label arrows as source reuse, component import or ledger inheritance. Record dates and evidence for each edge. This avoids apparent circular ancestry when projects later borrow from one another, and it keeps a modern rewrite from being mistaken for the launch code.

For an exact code comparison, preserve the two revisions, inspect shared history and changed consensus parameters, and distinguish imported files from independently implemented behavior. A similar README, a mining algorithm name or matching menus cannot replace that comparison.

Dogecoin's documented rebase is different from a new chain launch

Dogecoin's official development account states that the team re-forked its implementation from Bitcoin beginning with Core 1.10.0 in 2015, reapplying Litecoin changes. This explains why a current source tree can contain substantial Bitcoin ancestry while retaining Litecoin-related changes. It does not imply that existing DOGE balances were replaced with Litecoin balances in 2015.

Popular family diagrams often compress Dogecoin's early ancestry into a short chain of names. This article does not independently reconstruct every intermediate early source release. The relationship table therefore uses the version-specific rebase the project documents, instead of asserting an unverified direct-parent edge for the original release.

An implementation history also does not justify dismissing later maintenance as “zero innovation.” Development can involve parameter changes, consensus integrations, networking fixes, tests and security work even when much of the foundation is inherited. Assess specific changes and records rather than using ancestry as a substitute for evaluating the software.

Dogecoin AuxPoW: release in August, activation in September

The Dogecoin maintainers' retrospective timeline records the release of 1.8.0 on 24 August 2014 and activation of at mainnet height 371,337 on 11 September 2014. The earlier article repeatedly described merged mining as active since August, confusing the software release with the chain activation.

AuxPoW is a validation mechanism, not a transfer of DOGE balances into Litecoin's ledger. Compatible work is connected to an auxiliary commitment and checked against the auxiliary chain's rules. An accepted auxiliary proof need not correspond to a simultaneously accepted parent . The chains retain separate targets, block histories and rewards.

The merged-mining guide and Scrypt walkthrough explain the commitment and target relationship using versioned code. The additional work of constructing, validating and submitting auxiliary material still requires software and operations. Calling it “no additional cost” without a boundary is too strong, even though the expensive search work can be shared.

Pool revenue and an individual miner's received payout are different quantities. A pool may convert rewards, charge fees or impose separate payout terms. Shared mining compatibility alone does not guarantee that every contributing miner receives both assets or that current pool shares match across the two chains.

An algorithm change is a property of a particular network

Feathercoin's project description identifies NeoScrypt as its proof-of-work construction and describes its Litecoin origin. That is evidence for a changed technical design; it does not imply that NeoScrypt is interchangeable with Litecoin's fixed computation. Hardware compatibility must be checked against the actual accepted proof.

An algorithm transition can require coordinated validation changes within a continuing network. Whether it produces a separately supported chain split depends on adoption and continued operation under incompatible rules. Counting every algorithm change as another new currency would inflate a “fork family” census without identifying a new population of assets.

Likewise, an -resistance objective is a design objective, not a permanent empirical guarantee. Current profitability, available hardware and resistance to specialization require dated evidence. This revision does not infer that a network is safe, unsafe or economically viable merely from the algorithm name.

Litecoin Cash illustrates ledger inheritance

Litecoin Cash's launch page describes a split at Litecoin height 1,371,111 and a distribution of ten LCC units per eligible LTC. It also describes the initial post-split move to mining. This is materially different from starting an independent genesis ledger with copied wallet code.

The ratio does not create ten additional LTC on the Litecoin chain, multiply a holder's Litecoin balance or guarantee an equivalent market value. It describes the other chain's initial distribution rule. The project's later website also describes additional mining features, so a launch-era algorithm summary should not be presented as a complete account of every later rule.

This article did not run an LCC node, reconstruct the split set, test current replay protection, execute a claim or assess current access. The source is used for the project's stated launch mechanism. Its marketing claims about fees, performance and fairness are not adopted as our independent findings.

A historical distribution is not a reason to expose current keys

Checking eligibility and performing a claim are separate tasks. A third-party claim tool can ask for material that also controls original-chain funds. Never treat a familiar project name or a historical snapshot date as authentication for a website requesting a live or .

A safe investigation starts with the chain and asset identity, eligibility boundary, exact software source, validation behavior and replay implications. Moving original-chain funds alone does not establish that an unknown claim program is safe: , other accounts and exposed backups can remain relevant. This article provides no claim workflow and recommends no third-party claim service.

Use the backup identification study and cold-storage recovery process to understand what a secret can authorize. A public may help inspect a ledger boundary; it is not equivalent to signing authority. Preserve that distinction when evaluating old fork announcements.

Why a “95% failed” statistic needs a defined population

A failure percentage needs a reproducible inclusion rule, a list of qualifying projects, an observation date and an operational definition of failure. Does “fork” include indirect descendants, abandoned repositories, temporary split chains and every algorithm transition? Are renamed or relaunched projects counted once or several times? The denominator changes with those choices.

The numerator also needs a rule. No recent release, no observed blocks, no reachable peers and no supported market are different observations. They need not occur together. Failure to contact an explorer does not prove that a chain has stopped, while a surviving homepage does not prove that a usable validating network exists.

The earlier 95% figure had no such preserved population and is withdrawn. We do not replace it with another confident percentage from the same incomplete list. The downloadable source ledger records only the selected relationships this revision actually discusses, along with their evidence type and limits.

Evaluate current operation separately from historical origin

Different observations support different current-state claims
EvidenceWhat it can supportWhat it cannot establish alone
Repository and release artifactA specified source or binary release existsThe live chain is advancing or the release is secure
Dated validated chain observationsA tested chain reached the recorded boundaryIndependent miner ownership or future availability
Reachable service or explorerThat service answered at the checked timeA complete node population or consensus verification
Market listing and executable liquidityA defined venue and trading condition at a timeUniversal sellability, a historical peak or network security

A additionally depends on price and a defined circulating supply. A last-trade quote in a thin market is not a measurement of how much every holder could receive. Historical peak values need dated price and supply records, rather than an attractive number copied into a permanent table.

This revision makes no current “dead,” “zombie” or universally “alive” classification for the selected projects. It also does not turn a maintainer's product description into a measured transaction volume, security budget or user count.

Ancestry does not establish motives or a fraud finding

Source reuse can support compatibility, experimentation, rapid development or a changed design. It can also be used in misleading promotions. Which explanation applies to a particular project requires evidence about that project's conduct, not merely that it reused open-source code.

The previous account assigned broad pump-and-dump motives and made categorical scam accusations without supplying the records needed to support each claim. Those assertions are removed. A source-led history can describe a documented launch, code choice, disclosure or enforcement finding while distinguishing the author's statement from an independently established result.

For the same reason, success should not be defined by a chosen market-cap ranking and then used to prove technical merit. Adoption, trading attention, continued maintenance, payment usefulness and resistance to attacks are different outcomes. A historical narrative should choose its outcome before selecting the examples that appear to explain it.

Code inheritance does not transfer a security guarantee

Copying code does not copy independent operators, accumulated work, review practices, operational funding or a tested recovery ecosystem. A changed consensus parameter can also invalidate assumptions that were safe in the upstream setting. Conversely, a failure in a derivative does not by itself prove that Litecoin's unchanged rules caused it.

Do not treat surviving software ancestry as evidence of uninterrupted historical safety. A claim such as “no consensus failure in fourteen years” needs an incident definition and a documented historical investigation. This revision performs neither and does not use that absolute claim to infer the quality of every related network.

Our decentralization guide separates coordination, ownership, reachable infrastructure and development evidence. That framework is more useful for assessing a network than assuming its parent's reputation or a derivative's price settles the security question.

A timeline with the milestone type attached

Selected milestones; dates do not imply current operating status
Date or boundaryMilestoneEvidence scope
7 October 2011Timestamp encoded in Litecoin's mainnet genesis constructionHeader timestamp, not public launch time
9 October 2011Litecoin announcement thread beginsForum publication metadata; post later edited
13 October 2011, 03:00 GMTScheduled public launchFounder notice posted on 12 October
24 August 2014Dogecoin 1.8.0 software releaseMaintainer retrospective
11 September 2014; DOGE 371,337Dogecoin AuxPoW activationMaintainer retrospective; separate from release
2015; Dogecoin Core 1.10.0Documented implementation rebase onto BitcoinProject development account
18 February 2018; LTC 1,371,111Litecoin Cash's stated ledger-split boundaryProject launch description

A stronger historical reconstruction would add immutable source revisions, original announcement captures, validated chain identifiers and independent for each disputed boundary. The table preserves what the reviewed records support without implying that all those further checks were performed.

Sources, corrections and limits

The downloadable source ledger distinguishes versioned code, project descriptions, forum notices and a maintainer retrospective. A project describing its own history is primary evidence for that account; it is not an independent evaluation of every marketing claim on the same page.

This revision changes the article from an allegedly complete census to selected documented relationships. It corrects the 2011 milestone distinction and the Dogecoin release-versus-activation dates, explains later code rebases, removes unsupported market-cap and failure-rate figures, and separates historical distributions from present-day key security. No new fork-node synchronization, asset claim, audit or exhaustive repository genealogy was performed.

Original URL and publication date are retained so existing links continue to work. Requests for a correction should identify the specific relationship, release or chain boundary and provide the relevant original record through our corrections process.

Frequently asked questions

Is this a complete list of every Litecoin fork?

No. It is a selective source-led guide. A complete census would need a fixed inclusion rule, a preserved project population and explicit handling of indirect descendants, renamed projects and later rebases.

Does copying Litecoin code give LTC holders new coins?

No. Source reuse alone does not copy the ledger. A separate chain's distribution rules must explicitly establish eligibility at a particular boundary, and any resulting units belong to that other network.

Did Litecoin's public launch happen at its genesis timestamp?

Those are different milestones. The reviewed genesis construction uses a 7 October 2011 timestamp; the announcement thread began on 9 October, and the founder's notice scheduled the public start for 13 October at 03:00 GMT.

Did Dogecoin AuxPoW activate when 1.8.0 was released?

No. The maintainers' timeline records the release on 24 August 2014 and mainnet activation at height 371,337 on 11 September 2014.

Can one current repository identify every original ancestor?

No. Later rebases, component imports and hosting relationships can differ from launch history. Attach release versions, dates and evidence to each claimed source-code relationship.

Does an old distribution justify entering my seed into a claim site?

No. A historical eligibility rule does not authenticate a tool requesting signing secrets. This article provides no claim procedure and does not recommend exposing a live Litecoin backup to another project.

Method and data

Downloadable data or code.

Content review recorded: 2026-10-21. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.

Sources saved with the review:

See the article body for source links and any downloadable materials. Editorial method · Corrections · Report an issue

Jarosław Wasiński
Editor-in-chief · Financial markets and Litecoin education

Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.

Background, selected work and editorial responsibility →

Founder of MyBank.pl Financial education and market analysis Named editorial responsibility