Support for Proxy/Delegations

[crystalin]

I don't know well snapshot but I'm curious how we could support the proxy/delegations case for Moonbeam
Those are in a "many-to-many" relationship. Ex:

Account A gives proxy rights to Account B, C, D to perform "vote"

If I simply check if B is proxy of A and allows to use the Tokens, it also means that C, D (and also A) can spend the same tokens which is unfair.

@ChaituVR do you have an idea ?

[ChaituVR]

HI @crystalin Which strategy you are referring to? 🙈 Sorry i didn't get it

[crystalin]

@ChaituVR Sorry for the delay. I'm mostly referring to the moonbeam-free-balance strategy. But I think the concept is indepandant of which chain.

In this case, the same tokens can be used by multiple accounts, the question is how to limit so that it is used only once ?

[ChaituVR]

Do you mean limiting spaces to use this strategy only once? 🤔

[crystalin]

Yes, I think the easiest way to think about it is with proxies.
If you are account A and allow account B or account C to use your tokens for voting, how do you prevent having both B and C voting ? (on-chain this is easy because we have a "lock" mechanism for those tokens, but snapshot doesn't interact with the chain/state so it would require storing that lock in a database or ....)

[crystalin]

Gentle ping :)
Any idea ?

[apocys]

Could we consider implementing a "Proxy Login" feature? This would allow account B to vote as usual when logging in independently. However, if account B chooses to "log in as a proxy" for account A, their session would mimic that of account A, enabling them to vote (or propose) on behalf of account A. We can provide the verification on-chain, so we know that B is effectively a proxy of A.

[crystalin]

That would work for supporting proxies yes, but requires Snapshot to support asProxy feature.
@ChaituVR what do you think ?

[apocys]

gentle ping