Skip to content

Explain consequences of public key first byte collisions #1202

Description

@redfast00

In the FAQ (which @LitBomb recently updated), it says 3.6. Q: The first byte of my repeater's public key collides with an exisitng repeater on the mesh. How do I get a new private key with a matching public key that has its first byte of my choosing? and then shows how to change the public key and choose an arbitrary prefix.

I have some more questions about that FAQ entry:

  • What are all the consequences of such a first byte collision?
  • Assuming that there are more than 256 repeaters in the mesh (I can see this happening with a European mesh), and every possible first byte is already in use, how should you then choose what a new repeaters first byte should be?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions