7

With plaintext payment ids, you should a random payment id. Using a nonrandom one can affect your and other parties privacy.

Is this still a risk with payment id? Or could you include messages in the payment id safely.

What if you reuse the same id?

6

Using a non-random plaintext ID doesn't hurt your privacy (unless you publish it somewhere to link it to yourself), but reusing the same plaintext ID significantly reduces your privacy.

There should be no issue reusing an encrypted ID (the plaintext version, as in the integrated address) in the context of the Monero blockchain (this answer does not address any out-of-band concerns, like assigning your customers incremental IDs where they can tell what order # they are, etc.).

The key is a "random" one-time-pad, so the randomness (or lack of) of the plaintext doesn't matter. Knowing the plaintext ID and seeing the encrypted ID (revealing the key, as it is simple XOR) provides no additional useful information, since the key is used only for that particular transaction.

Since they are only 64-bit (space-saving), collisions of the "ciphertext" are expected to occur after about 5 billion transactions (with IDs). A collision also provides no meaningful information.

8 bytes isn't much room to include a message, though.

  • I heard that a non-random plaintext ID hurt your privacy since it leaked info (for example, if there where customer IDs, and someone noticed the pattern). – PyRulez Sep 14 '16 at 23:37
  • 3
    Note I specifically said this answer doesn't address out-of-band concerns, like... – Luigi Sep 14 '16 at 23:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.