search

Multibit-Legacy / multibit-hd

Deprecated Bitcoin Wallet
https://multibit.org/blog/2017/07/26/multibit-shutdown.html
Other
169 stars 124 forks source link

added internal dnsseed for intranets #832

Closed ubermorgen closed 8 years ago

ubermorgen commented 8 years ago

A simple way to add support for multibit on intranets that have a bitcoind node running inside the LAN but no internet access. Just create a dnsseed.internal address in your internal DNS tree that points to the bitcoin node.

MultibitHD should probably have support to configure peers explicitly as multibit classic did, but it seems that functionality is not present yet - and even if it was having an internal DNS seed is a fairly easy way to configure it and is also a very easy change to make with no major downsides.

jim618 commented 8 years ago

We use connections to multiple peers in various places to establish the quality of the transactions being sent and being seen. For instance a tx is only considered properly sent when it has been reflected back from several other peers. Also a tx's confidence is based on having been seen by multiple peers.

Tx confidence affects things like whether change is spendable which has a dramatic effect on usability.

The peer configurability was dropped deliberately in MultiBit HD as we don't want people to configure for a single (or 2, or 3) peers and then see this different behaviour appear.

gary-rowe commented 8 years ago

Closing this as we won't be pulling this change.