Implemented tunnel payouts #3492
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
devos50
force-pushed
the
payouts3
branch
2 times, most recently
from
92b8ae0 to
44b287b
Compare
devos50
changed the title
|
@qstokkink ready for review. I think the missing lines in the code coverage are acceptable :) |
qstokkink
approved these changes
Mar 4, 2018
qstokkink
changed the title
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR, I implemented the payouts for the tunnel community. When destroying a 'regular' data circuit or an e2e circuit, the downloader pays the subsequent node in the form of bandwidth tokens. Note that this implementation is the most basic implementation possible and does not contain any sophisticated security/anonymity features.
Depends on Tribler/py-ipv8#67
Fixes #3493