-
Notifications
You must be signed in to change notification settings - Fork 54
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
myNode integration #80
Comments
I am familiar with MyNode's software design, so I can take this up. However, I would like to know if we want to install it as Docker image or as node project. |
If it is possible I'd be in favor of using the Docker images. Just because it'd be more comfortable to make adaptions as the project progresses. However, I am not familiar with myNode, so they might already have a JoinMarket install and we'd just need the UI. What are your thoughts on this @abhiShandy and @secondl1ght? |
myNode currently has JoinInBox, im not familiar with implementation either but is it possible to use the same joinmarket backend they are using for that? |
I think Joininbox is a set of Shell scripts which installs JM among other utilities. We can add this web-UI to that script and then launch both the JM daemon and web-UI using a systemd service. |
@secondl1ght You can definitely hook up Jam to an existing joinmarket instance that has the |
@abhiShandy I would say once the next Jam release happens (which should be soon) with some bug fixes let's get the myNode integration happening after that. Once v0.0.4 is released let's get Jam out to the myNode users! Even the current version seems to be working very well overall on the other node implementations so it looks like it is ready. |
I think we are ready for myNode with the latest release! Would love to see Jam on there. |
Any update on this? |
I can look into it this weekend. |
Let me know if there is something we can do on our side to move this forward @abhiShandy 🙏 |
Created a draft PR: mynodebtc/mynode#710 |
@secondl1ght reached out to the myNode team already, see mynodebtc/mynode#628
The text was updated successfully, but these errors were encountered: