The link at the top of the thread is not current, as mentioned by
@BrianM . The correct link, (as of this posting) is:
https://github.com/BitcoinUnlimited/BitcoinUnlimited/issues
@theZerg could you update the link in post #1 to match the issues link for the current default branch. If my HCI courses taught me anything it's that users want instant gratification, no scrolling! Also, if you or
@solex could perma-sticky this post (or a locked post with just the URL so we don't end up with multiple pages). IMO, if there is any type of semi-formal bug/issue reporting procedure for an active project like this, it's paramount to make that procedure clearly and permanently visible to users/guests.
Thanks!
----------------------------------------------------------------------------------------------------------------------
Also, just FYI, already posted on GitHub (
Issue #65), added possible single-line issue which may be the cause of:
1. The client's ability to connect to more than the hard coded limit of 8 outgoing nodes by specifying more than the recommended 8 "-addnode" lines in bitcoin.conf
2. A possible reason why users may never be able to achieve the "-maxconnections" specified if they also specify "-addnode" parameters at the command line and/or in bitcoin.conf. In the extreme, but unlikely case, this could possibly prevent all inbound connections.