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

Mixnet: Use max_message_size and max_path_length for Sphinx encoding #104

Closed
wants to merge 1 commit into from

Conversation

youngjoon-lee
Copy link
Contributor

We've defined two parameters: max_message_size and max_mix_path_length, but we haven't used it for Sphinx encoding because the pysphinx library didn't support those parameters.
Now that I modified the pysphinx to accept those parameters (instead of using hard-coded parameters), we can pass those parameters to pysphinx.

As a reminder,

  • The size of Sphinx packet is determined by those two parameters. Those are global parameters shared to all nodes in the network.
  • All Sphinx packets have the same size, even if an actual message in several packets is shorter than max_message_size.
  • All Sphinx packets have the same size, even if an actual mix path of several packets is shorter than max_mix_path_length.
  • If an user tries to use values longer than those parameters, pysphinx raises an exception.

@youngjoon-lee youngjoon-lee requested a review from madxor July 13, 2024 07:03
@youngjoon-lee youngjoon-lee self-assigned this Jul 13, 2024
@youngjoon-lee youngjoon-lee changed the title Mixnet: Use max_message_size and max_route_len for Sphinx encoding Mixnet: Use max_message_size and max_path_length for Sphinx encoding Jul 13, 2024
@youngjoon-lee
Copy link
Contributor Author

Closing this with the same reason mentioned in #98 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant