addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
addnode=node.biblepay-explorer.org
Don't recommend this, the second and third node are both dead, and the first node line isn't needed, it's already hard coded in the wallet.
For syncing issues, I would try going to the last pages of http://explorer.biblepay.org:3001/network , finding 1.1.2.1+ IP addresses and then in the console window type:
The problem with the node.biblepay.org being the master, it is contributing to the sync/crash issues.
Since it was down, many users were unable to use the client. this is a huge centralization issue
Lesson: if you want to take down bbp only go after 1 node.
This would only affect new nodes. After a node connects for the first time, it keeps a list of possible peers so even if the original master is down it can keep on working.
And this is not a "problem" of BBP, it happens with all Bitcoin-like coins.