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
Add memo field for token entity #960
Comments
A review should be done of all of HAPI to see if there are any other entities that lack a memo field. Every entity should have an optional memo field (e.g., account, file, smart contract, topic, token, etc). Anything that has an ID like 0.0.123 should also have a memo field.
…________________________________
From: donaldthibeau <notifications@github.com>
Sent: Thursday, January 14, 2021 8:38:28 AM
To: hashgraph/hedera-services <hedera-services@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [hashgraph/hedera-services] Add memo field for token entity (#960)
Summary
Each token entity should include an optional memo field of up to 100 bytes. Uniqueness is not guaranteed. The memo can only be changed by the admin keys on the token entity.
Memo field would be returned as part of token info.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#960>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABDBYW2OWPQTNCQANWPGKFDSZ36WJANCNFSM4WCQZP3Q>.
|
So to summarize, for an entity type of X we will say that for the CreateX transaction: |
Summary
Each token entity should include an optional memo field of up to 100 bytes. Uniqueness is not guaranteed. The memo can only be changed by the admin keys on the token entity.
Memo field would be returned as part of token info.
The text was updated successfully, but these errors were encountered: