New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support different xud networks #781

moshababo opened this Issue Jan 7, 2019 · 1 comment


None yet
2 participants
Copy link

moshababo commented Jan 7, 2019

At the moment network config property is default to testnet, and its only usage is to derive the lnd macaroon file path.

This property usage need to be extended to support different xud networks (mainnet/testnet/simnet/regnet), where peers from different networks shouldn't be connected.

mainnet and testnet can refer to the underlying blockchains public networks, while simnet can refer to the xud controlled network. I'm not sure about regnet.

Each network will have a distinct value to be used in the wire protocol (following the values in bitcoin), both to identify the packet/peer origin network and as the socket stream delimiter (same as in bitcoin):

Network Magic value
mainnet 0xD9B4BEF9
testnet (bitcoin testnet3) 0x0709110B
simnet 0x12141C16
regnet 0xDAB5BFFA

@moshababo moshababo added this to the 1.0.0-alpha.9 milestone Jan 7, 2019


This comment has been minimized.

Copy link

kilrau commented Jan 7, 2019

And i believe we need to additionally separate per coin. bitcoin testnet, litecoin testnet, different eth testnets

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