Skip to content
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

[feat] Add CJDNS support along with Bitcoin 23 update #65

Open
kn0wmad opened this issue Apr 26, 2022 · 2 comments
Open

[feat] Add CJDNS support along with Bitcoin 23 update #65

kn0wmad opened this issue Apr 26, 2022 · 2 comments
Assignees
Labels
Enhancement New feature or request Needs Scoping Requirements are not fully defined Needs Triage Not enough information to determine priority P4 - Community Issues that we would accept PRs for but will not dedicate internal resources to

Comments

@kn0wmad
Copy link
Contributor

kn0wmad commented Apr 26, 2022

Good stuff... https://github.com/bitcoin/bitcoin/blob/23.x/doc/cjdns.md

@kn0wmad kn0wmad added Enhancement New feature or request Needs Triage Not enough information to determine priority Needs Scoping Requirements are not fully defined labels Apr 26, 2022
@chrisguida
Copy link
Contributor

neat, will do

@kn0wmad
Copy link
Contributor Author

kn0wmad commented May 13, 2022

Upon investigation, it seems this would need CJDNS support as an OS feature. Is this as simple as install/config in EOS (as is done with Tor), then add a CJDNS interface for Bitcoin, or is this a more significant undertaking? @dr-bonez

The most obvious immediate hurdle is that joining the CJDNS network requires manually finding your first peer. Start9 could be this peer, but that does not seem ideal, in case S9 dropped off the network.

@kn0wmad kn0wmad added the P4 - Community Issues that we would accept PRs for but will not dedicate internal resources to label Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Needs Scoping Requirements are not fully defined Needs Triage Not enough information to determine priority P4 - Community Issues that we would accept PRs for but will not dedicate internal resources to
Projects
Status: No status
Development

No branches or pull requests

2 participants