Skip to content

Conversation

@MCozhusheck
Copy link
Contributor

Description

Reflects naming changes done by this PR which renames PaymentId to MemoField and user_data to payment_id as requested in this issue.

Copy link
Contributor

@hansieodendaal hansieodendaal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, some comments.

Comment on lines +91 to +93
| one_sided + memo field | 🐋 | 05 | 6 |
| interactive + memo field | 🌙 | 06 | 7 |
| onesided + interactive + memo field | 🤔 | 07 | 8 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest just calling it memo instead of memo field in this document.

Comment on lines +112 to +113
#### Memo Field
Tari includes an optional encrypted bytes field with a max size of 256 bytes. This field allows you to store bytes that are encrypted on chain, on the UTXO. This can be used to track payments etc. When included into the Tari address, the sent UTXO will include this memo field.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just memo

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.

2 participants