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

automatic tipping of deserving Tor routers #140

Open
nathan-at-least opened this issue Mar 8, 2015 · 1 comment
Open

automatic tipping of deserving Tor routers #140

nathan-at-least opened this issue Mar 8, 2015 · 1 comment
Labels
A-wallet Area: Wallet F-tor Feature: Tor integration I-privacy Problems and improvements related to privacy. not in 1.0 public relations special to Zooko use case Zcash codebase

Comments

@nathan-at-least
Copy link
Contributor

Tor wants to diversify their funding:

https://twitter.com/micahflee/status/574629662501928960

Tor may provide for a need necessary to some use cases (eg: avoid linking transaction times with IP addr correlation), and people who like privacy may like both projects. It would be good PR and I would feel good if Tor were partially funded by our users!

Tor accepts Bitcoin for development donations:

-and they also recommend people tip infrastructure providers.

Here's a website you can send your funds to and the promise to distribute them to router operators:

However, our wallet should be able to replicate this functionality such that user coins go straight to routers, and ideally the router addresses would be authenticatedly bound to the local Tor client's consensus view.
@nathan-at-least nathan-at-least added Zcash codebase F-tor Feature: Tor integration A-wallet Area: Wallet potential feature I-privacy Problems and improvements related to privacy. public relations use case labels Mar 8, 2015
@nathan-at-least nathan-at-least mentioned this issue Mar 8, 2015
Closed
@zookoatleastauthoritycom
Copy link

It seems like a really good way to do this is the "auto tip a random good node" method. The way this works is that the client use the normal Tor process of selecting a Tor router or gateway, but it will not use that Tor node for actual traffic. Instead it will send a Zcoin donation to any Zcoin address that the Tor node registered in its metadata.

Good things about this approach:

  • It doesn't require any opt-in from the Tor developers or the Tor project, only from the operators of Tor nodes who want to receive tips.
  • It rewards "better" Tor nodes (as determined by the node selection algorithm) more. The Tor devs and the Tor project are already faced with the task of automatically selecting "better" Tor nodes, and this approach makes it so that whatever approach they take to that, our Zcoin tipping feature automatically uses that approach. (Note: except that some Tor nodes opt-in by putting in a Zcoin address into their metadata and others don't — we should be on the lookout for ways in which that divergence between them could cause the Tor approach of selecting better nodes for routing purposes to have the wrong consequences for our tipping purposes.)
  • It could be contributed to Bitcoin upstream.

@zookoatleastauthoritycom zookoatleastauthoritycom changed the title Integrated "tip Tor" button. automatic tipping of deserving Tor routers Aug 24, 2015
Open
ebfull pushed a commit that referenced this issue Nov 4, 2015
@sipa
Squashed 'src/secp256k1/' changes from b0210a9..bccaf86
ecae2ac 
bccaf86 Merge pull request #150
2a53a47 Merge pull request #151
5f5a31f Merge pull request #149
3907277 Merge pull request #142
a3e0611 Enable tests in x86 travis builds
45da235 x86 builder
8bb0e93 Merge pull request #155
971fe81 build: fix openssl detection for cross builds
f22d73e Explicitly access %0..%2 as 64-bit so we use the right registers for x32 ABI
e66d4d6 Avoid the stack in assembly and use explicit registers
cf7b2b4 Fix ECDSA message hashes to 32 bytes
056ad31 Really compile with -O3 by default
74ad63a Merge pull request #146
9000458 Merge pull request #145
1f46b00 build: fix __builtin_expect detection for clang
aaba2e0 Merge pull request #136
8a0775c Merge pull request #144
ee1eaa7 Merge pull request #141
c88e2b8 Compile with -O3 by default
6558a26 Make the benchmarks print out stats
000bdf6 Rename bench_verify to bench_recovery
7c6fed2 Add a few more additional tests.
992e03b travis: add clang to the test matrix
b43b79a Merge pull request #143
e06a924 Include time.h header for time().
8d11164 Add some additional tests.
3545627 Merge pull request #118
6a9901e Merge pull request #137
376b28b Merge pull request #128
1728806 Merge pull request #138
a5759c5 Check return value of malloc
39bd94d Variable time normalize
ad86bdf Merge pull request #140
54b768c Another redundant secp256k1_fe_normalize
69dcaab Merge pull request #139
1c29f2e Remove redundant secp256k1_fe_normalize from secp256k1_gej_add_ge_var.
2b9388b Remove unused secp256k1_fe_inv_all
f461b76 Allocate precomputation arrays on the heap
b2c9681 Make {mul,sqr}_inner use the same argument order as {mul,sqr}
6793505 Convert YASM code into inline assembly
f048615 Rewrite field assembly to match the C version
3ce74b1 Tweak precomputed table size for G

git-subtree-dir: src/secp256k1
git-subtree-split: bccaf86caa9c44166e5a66600b742c516e03c3f0
@DeaVulTan DeaVulTan mentioned this issue Apr 2, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-wallet Area: Wallet F-tor Feature: Tor integration I-privacy Problems and improvements related to privacy. not in 1.0 public relations special to Zooko use case Zcash codebase
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zookoatleastauthoritycom @nathan-at-least