Skip to content

Add Litecoin Cash network support - #1341

Open
internauta1 wants to merge 1 commit into
MetacoSA:masterfrom
internauta1:add-litecoin-cash
Open

internauta1 wants to merge 1 commit into
MetacoSA:masterfrom
internauta1:add-litecoin-cash

Conversation

@internauta1

Copy link
Copy Markdown

Summary

Adds Litecoin Cash (LCC) network support to NBitcoin.Altcoins.

This adds mainnet, testnet, and regtest network definitions, including:

  • Network magic and P2P/RPC ports
  • Base58 address and extended key prefixes
  • Bech32 prefixes
  • Consensus parameters
  • BIP9 and buried deployment parameters
  • Genesis blocks
  • DNS seeds
  • Registration in AltcoinNetworkSets

Tests

Added tests covering:

  • Mainnet, testnet, and regtest genesis hashes
  • Network magic and default ports
  • Base58 and Bech32 prefixes
  • Legacy, P2SH-SegWit, and native SegWit address round-trips

Validated with:

dotnet test NBitcoin.Tests/NBitcoin.Tests.csproj -f net10.0 --filter "LitecoinCash|NoCrashQuickTest"

Result: 5 tests passed, 0 failed.

@NicolasDorier

Copy link
Copy Markdown
Collaborator

Is it this project? https://github.com/litecoincash-project/litecoincash

Sorry but 2 years nobody touched it, it's dead project.

@internauta1

Copy link
Copy Markdown
Author

Yes, that's the project, and you're right that the Core repository itself has been inactive for a long time.

The network is still running, though. I recently started working on rebuilding some of the surrounding infrastructure and integrations, including a public node, Electrum server, explorer/API and mining pool.

Part of the reason for this PR is exactly that: I'm trying to bring the LCC ecosystem infrastructure back into maintained software rather than pretending the old Core repository is actively developed.

I understand if the inactivity of the upstream Core repository is still a reason not to include it in NBitcoin.

@NicolasDorier

Copy link
Copy Markdown
Collaborator

@internauta1 at the minimum they need to maintain their core node. With current AI security attacks, a software untouched since 2 years is begging to be attacked. Once there is some effort in the community proving that at least the main team care, I don't feel it should be merged here.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants