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.

Sign up for GitHub

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

Jump to bottom

Support for Tor Network in CKB #4656

Open
eval-exec opened this issue Sep 22, 2024 · 2 comments
Open

Support for Tor Network in CKB #4656

eval-exec opened this issue Sep 22, 2024 · 2 comments
Assignees
@eval-exec
Labels
m:network t:enhancement Type: Feature, refactoring.

Comments

@eval-exec
Copy link
Collaborator

eval-exec commented Sep 22, 2024 •
edited
Loading

Feature Request

Is your feature request related to a problem? Please describe.

Bitcoin supports the Tor network. I believe CKB should support it as well.

Describe the solution you'd like

Bitcoin's implementation includes starting/connecting a tor server and using the Tor server's control socket API to create an onion service. Similarly, I propose adding flags to CKB such as -proxy=ip:port (need #4473) , -onion=ip:port, -onlynet=onion, -torcontrol=, and -torpassword.

I am considering the following approach like Bitcoin:

  1. Start a Tor server that listens on port 9050. (Or enable tor's control socket API on 9051, then let CKB use the tor socket API tor create onion service self)
  2. Run CKB using a proxy to operate behind the Tor network: ./ckb run --proxy=127.0.0.1:9050.

Describe alternatives you've considered

There is a Tor implementation in Rust called arti, but I am concerned that it may not be production-ready.
@eval-exec eval-exec added the t:enhancement Type: Feature, refactoring. label Sep 22, 2024
@eval-exec eval-exec self-assigned this Sep 22, 2024
@eval-exec eval-exec moved this to 🏗 In progress in CKB Kanban Sep 22, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale To be closed due to a lack of activity label Oct 23, 2024
@eval-exec eval-exec removed the stale To be closed due to a lack of activity label Oct 25, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale To be closed due to a lack of activity label Nov 24, 2024
@eval-exec eval-exec removed the stale To be closed due to a lack of activity label Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eval-exec eval-exec

Labels
m:network t:enhancement Type: Feature, refactoring.
Projects
CKB Kanban
Status: 🏗 In progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eval-exec