Open 3Nigma opened 2 years ago
Adding memo-support makes sense & is expected to come with #44 + v2 more generally. Currently it's expected to be supported in single transfers (see the screenshot in #50) and in the bulk transaction distribution by adding an additional column to the .csv input (so that way each tx in the bulk distribution can have a unique memo). Would that be sufficient?
Yes. I think that would very much suffice. Thank you, @Cooper-Kunz !
Issue
There is no easy way for multi-signature Hedera accounts to send assets with a
memo
-info attached.Potential solution
We should add support for a multi-sig Hedera account to utilize this tool to be able to assign a
memo
information on a collective basis (meaning, we ask for it once and it's being replicated to all resulting transactions) to all the individual-resulting transactions of the requested assets.Question
How does this manifest in the user journey?
Before final confirmation of the resulting assets distribution is asked for, the user is prompted to input the desired, optional,
memo
string which should be validated (current maximum size is 100 characters, I think).