Currently, when I open an active poll, there is no way to find out whether or not a vote has already been caste with the same wallet. Even when we cast a vote, there is no way to now if this is counted as a new vote, or does this overwrite a previous vote.
I could imagine that we have a button, saying "check my vote", which would bring up metamask, and send a signed TX to the contract, to get back the existing vote, if any, and then we could indicate this info to the UI.
In theory, we could also store this info in browser localstore when casting the vote, but then again, the same user might open the same poll from another device, or maybe there are multiple legitimate representatives of the same entity (with a common wallet, with one vote) which open the same poll independently, so using local store would not be a full solution. The correct solution would be to request this info from a token.
Obviously this would have to be a signed operation, so there is some friction, it can not happen automatically in the background, so I would not trigger this automatically when loading a poll, just when the user requests it.
Currently, when I open an active poll, there is no way to find out whether or not a vote has already been caste with the same wallet. Even when we cast a vote, there is no way to now if this is counted as a new vote, or does this overwrite a previous vote.
I could imagine that we have a button, saying "check my vote", which would bring up metamask, and send a signed TX to the contract, to get back the existing vote, if any, and then we could indicate this info to the UI.
In theory, we could also store this info in browser localstore when casting the vote, but then again, the same user might open the same poll from another device, or maybe there are multiple legitimate representatives of the same entity (with a common wallet, with one vote) which open the same poll independently, so using local store would not be a full solution. The correct solution would be to request this info from a token.
Obviously this would have to be a signed operation, so there is some friction, it can not happen automatically in the background, so I would not trigger this automatically when loading a poll, just when the user requests it.