Reject DTag transfers #297
Labels
kind/new-feature
Propose the addition of a new feature that does not yet exist
x/profiles
Module that allows to create and manage decentralized social profiles
Milestone
Feature description
Currently, during the DTag transferring process, there is no way for a user to reject a DTag request. This, together with the fact that trades are kept "suspended" if the sending user's DTag changes, can cause strange situations.
Let's consider the situation in which Alice has DTag
first
and Bob wants it. Then this happens:second
.In this case the following would occur:
Implementation proposal
In order to solve this problem, I think we should implement the following processes:
Also, we should implement two new message types:
MsgCancelDTagRequest
This can be used only by the user who started the request, and it cancels the process by deleting the request itself.
MsgRejectDTagRequest
This can be used only by the user who is asked for their DTag. This also cancels the process.
The text was updated successfully, but these errors were encountered: