You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation, we have a reason field for MsgCancel that is not stored in state but included in EventCancel but we do not have a reason field for MsgRetire.
In the past, we have used the transaction memo field for retirement reason but we should create a reason field for MsgRetire that is not stored in state but included in EventRetire (same as MsgCancel/EventCancel).
Problem Definition
Users must use the memo field of a transaction to provide a retirement reason but may want to use the memo field for something else or would rather use an explicit field for retirement reason.
Proposal
Add reason to MsgRetire that is not stored in state but included in EventRetire.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
A reason field would also need to be added to MsgCreateBatch and MsgSend in the ecocredit module and MsgBuyDirect within the marketplace submodule and MsgTake within the basket submodule.
Summary
In the current implementation, we have a reason field for
MsgCancel
that is not stored in state but included inEventCancel
but we do not have a reason field forMsgRetire
.In the past, we have used the transaction memo field for retirement reason but we should create a reason field for
MsgRetire
that is not stored in state but included inEventRetire
(same asMsgCancel
/EventCancel
).Problem Definition
Users must use the memo field of a transaction to provide a retirement reason but may want to use the memo field for something else or would rather use an explicit field for retirement reason.
Proposal
Add
reason
toMsgRetire
that is not stored in state but included inEventRetire
.For Admin Use
The text was updated successfully, but these errors were encountered: