Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AIP-31][Allowlisting for delegation pool] #121

Closed
thepomeranian opened this issue May 5, 2023 · 6 comments
Closed

[AIP-31][Allowlisting for delegation pool] #121

thepomeranian opened this issue May 5, 2023 · 6 comments

Comments

@thepomeranian
Copy link
Collaborator

thepomeranian commented May 5, 2023

AIP-31 - Allowlisting for delegation pool

Summary

This AIP introduces the concept of allowlisting in delegation pools, allowing pool owners to control who can stake in their delegation pool. The feature includes mechanisms for adding or removing delegators from the allowlist and evicting delegators not on the allowlist. By default, a delegation pool is permissionless and does not have an allowlist, until the pool owner explicitly sets an allowlist using this feature.

Link to AIP: https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-31.md

@meetrick
Copy link

meetrick commented May 9, 2023

I support AIP31, and I think there should be a rule against the delegation pool owner setting the allowlist.
Probably not, but sometimes it could be bad for the ecosystem if delegation pool owners collude with bad intentions.
If I'm wrong(like as misunderstood), please give me feedback.
Of course, I think most good block-chainers would not harm the ecosystem.

@sherry-x
Copy link
Contributor

@meetrick Would you be able to think of some case pool owner might apply the allowlist with bad intention? I think generally setting allowlist doesn't really help the pool owner, since the more people delegate to your pool, you earn more commission, so financially node operators are incentivized to keep things open. As for why allowlisting is helpful, it's described in the motivation, where some entity who wants to run delegation pool, but need to comply with stricter regulation, so this feature give pool owner some control on how they want to manage the pool.

@meetrick
Copy link

@meetrick Would you be able to think of some case pool owner might apply the allowlist with bad intention? I think generally setting allowlist doesn't really help the pool owner, since the more people delegate to your pool, you earn more commission, so financially node operators are incentivized to keep things open. As for why allowlisting is helpful, it's described in the motivation, where some entity who wants to run delegation pool, but need to comply with stricter regulation, so this feature give pool owner some control on how they want to manage the pool.

@sherry-x I agree with the basic intent, of course the delegation pool owner benefits from having more delegates, so I don't think it would be abused.
I was just thinking about the worst-case scenario where the allow list could be abused, like if the owner of all the delegation pools closed the allow list.

@davidiw
Copy link
Contributor

davidiw commented May 10, 2023

Concept and idea make sense. What is the proposed implementation of allowlists?
Furthermore, is this the right design? We're going to add a lot of storage slots just for tracking an allowlist on-chain. I might suggest an alternative approach of multi-agent or a two-stage delegation via an escrow.

@eliotstock
Copy link

Fully support this. We're an institutional staking provider and we're seeing demand from clients for allow-listed staking pools. Enabling this would unlock increased institutional staking demand, imo.

@kikakkz
Copy link

kikakkz commented Jun 2, 2023

Totally agree with that for policy of specific area. It may be a legal issue that pool owner cannot accept all staking from public user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants