N.B. This implementation is based on https://cips.cardano.org/cip/CIP-20 which defines a format to support multi-entry messages, whereas Lace currently only has good support for single entry (with a split to handle > 64 bytes). To adopt this solution we will be considering changing to a multi-line input field.
Context
When fixing https://github.com/input-output-hk/lace/issues/978 I discovered there's more we can be doing in the SDK to help applications produce compliant CIP-20 transaction metadata. I've fixed the immediate issue here https://github.com/input-output-hk/lace/pull/1379, but there were no tests and I would rather put energy into removing the responsibility from Lace altogether.
https://github.com/input-output-hk/lace/blob/e877d4668c02ae647ed39293f05233d0ac513663/packages/cardano/src/wallet/lib/get-auxiliary-data.ts#L1-L74
N.B. This implementation is based on https://cips.cardano.org/cip/CIP-20 which defines a format to support multi-entry messages, whereas Lace currently only has good support for single entry (with a split to handle > 64 bytes). To adopt this solution we will be considering changing to a multi-line input field.
Proposed Solution
See commit messages
Important Changes Introduced
See commits