-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Deploy seed nodes to assist p2p network discovery #3
Comments
I tried again with the current master to test the serverside bootstrapping, but it still has the same issue that the relay fallback causes an exception on the server. Thomas Bocek told me on the mailing list that he will look into the issue. There is also a warning with the signing for data protection. That seems to be another open bug, he will investigate. |
I'll investigate after I've got my akka prototype going. |
Probably we need to wait until Thomas has fixed the problem... cu, Am 22.08.2014 um 20:51 schrieb stevemyers [email protected]:
|
@cbeams Thanks Chris! I will try it on my own first, if I have troubles I will ping you... |
Good news from Thomas, he said we think he can fix the open problem with directSend (UPnP) until mid of the week. |
Hi Steve, Great! Good to have the master seeds connected. I will add a test where one peer connected to my server stores data and the 2. peer connected to your server read the data. Maybe we can extend later the tests in the way that we have a number of normal peers (5-10) running on the server and then check if shutdown of nodes will affect the DHT storage. It should automatically manage the storages, so a leaving node will be replaced by others. As long 1 node remains the data should be accessible. Do you have any ideas how we should go on with the directSend problem? I hope Thomas can fix it soon, he wrote that he thinks he can fix it until mid of the week, so chances are good that we get it soon. Otherwise probably its worth to dive deeper into tomp2p code, will probably be not the last problem and better to be not too dependent on the help of Thomas. Though that will be a time consuming adventure... but I think we need to go that path. What do you think? |
Good news: |
Trade process with relay mode works now. Offer storage + messaging! |
Added tests for add (used for offers to add an offer to a list), remove and all tests are green with relay. There are 2 small issues with incorreect success results, whcih i will report Thomas. I will update the our fork to the master head. |
Port forwarding is working again, dont know why it was not working before. Maybe my router behaves strange with UPnP? But there are still problems, DHT basically works but delivers wrong success flags, and directSend is still not working. If we dont get it working we can deactivate it so users can only connect directly or via relay mode (just as temporary solution). |
I deactivated port forwarding for the moment as that is not working correctly. In relay mode startup is slower but all works so far as I have tested. |
Step bisq-network#7 is needed before step bisq-network#3 or the later would fail. I suggest moving step bisq-network#7 to prerequisites chapter since that's what it seems to be.
Fix the path - after step #3 we are already in bitsquare/
Fixed p2shHeader attribute and added to another List
…ce-to-string Change API grpc.proto triggerPrice field to string [#3]
Motivation
Server-side seed nodes are necessary such that that first-time Bitsquare users can "bootstrap" into the p2p network, i.e. discover enough other nodes and communicate with them. From that point forward, clients maintain their own list of last-known-good peers, meaning that clients no longer rely on the seed nodes.
Next steps:
The text was updated successfully, but these errors were encountered: