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

Circuitv2 may allow for greater privacy on the ipfs network. #8961

Closed
3 tasks done
Destroyinator69420 opened this issue May 10, 2022 · 2 comments
Closed
3 tasks done
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@Destroyinator69420
Copy link

Destroyinator69420 commented May 10, 2022

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

The circuitv2 protocol in go-libp2p could allow for greater privacy on the ipfs network. Instead of a traditional onion router, I think the feature should be opt-in, with a tit for tat karma system. It would take the form of 12 outbound tunnels and 12 inbound tunnels that are 1 hop in length, both for seeders and leeches. If both parties choose to stay private, then the tunnels will be no more than two hops in length for the entire connection. There are many ways to do a karma system, is a karmachain that tallies the amount of data that a node has contributed to the privacy of others minus the amount of data that a node has taken from the privacy of others. Another system to do the same thing could be a distributed hash table. Such a system could be complementary to filecoin. It should be noted that I do not think that this system is urgent, but I also think that it might be necessary if IPFS is truly the wave of the future and gains mainstream adoption.

All the best,
Destroyinator

edit: My apologies, I filed this under the wrong type of issue and I am unable to change it now, sorry.

@Destroyinator69420 Destroyinator69420 added the kind/enhancement A net-new feature or improvement to an existing feature label May 10, 2022
@welcome
Copy link

welcome bot commented May 10, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@Jorropo
Copy link
Contributor

Jorropo commented May 11, 2022

CircuitV2 has nothing to do with privacy and isn't aim to be.
Fitting privacy on circuit v2 would be harder and less effective than a proper solution (using already existing well known software like Tor or i2p).

If you care about that we have an issues open here:

@Jorropo Jorropo closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants