Can Not connect to any peer in segnet4, Could I use other block chain? about lnd HOT 5 CLOSED

My local btcd node is still able to successfully connect to the segnet4 DNS seed. It has also been around since segnet was created, so its addrman is well populated. As a result I have no problem connecting to other nodes on segnet.

You might need to find/locate the address of an existing segnet node in order to bootstrap your bitcoind node.

Alternatively, you can use testnet as you suggested in the issue title.

from lnd.

@Roasbeef thank you, cound you give the ip address of some segnet node, or your peers.dat to [email protected] ?

from lnd.

@Roasbeef me too, [email protected]

from lnd.

For the most part, segnet is pretty much dead at this point. I've switched over primarily to using a local instance of simnet instead.

Now that Bitcoin Core has released version 0.13, there should be more segwit enabled peers on testnet now, so I'd recommend running the daemon in testnet mode for now. The daemon can be switched over to testnet mode by passing the --testnet flag on the command line, or setting testnet=1 in your lnd.conf.

from lnd.

Closing this issue as testing has now primarily moved onto Testnet3.

from lnd.