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

Make Centrifuge router a controller when making an investment #2469

Open
0x4Graham opened this issue Oct 3, 2024 · 0 comments
Open

Make Centrifuge router a controller when making an investment #2469

0x4Graham opened this issue Oct 3, 2024 · 0 comments

Comments

@0x4Graham
Copy link

Summary:

With the introduction of Liquidity Pools V2, we can now assign a controller to the investment process, allowing anyone to permissionlessly call functions such as mint and others on LP investments. This feature can be leveraged to streamline the claiming process for investors, automating the claim and transfer of tranche tokens.
Problem:

Currently, when an investor makes an investment, they are required to manually claim their tranche tokens once they are ready. This adds unnecessary friction for the user, as they need to monitor and execute the claim themselves.

Solution
To enhance user experience, we propose the option for permissionless claiming of tranche tokens, allowing a bot or any other external actor to claim tokens on the investor’s behalf as soon as they are ready. The tokens will always be sent directly to the investor’s wallet, ensuring security and ownership. Therefore we need to make the Centrifuge router an operator

Checkbox Text:
Allow permissionless claiming of your <> (LTF).

Tool Tip:
By selecting this option, you allow anyone to execute the claim transaction on your behalf. However, the tokens will always be sent directly to your wallet, ensuring only you receive them.

You make the CentrifugeRouter as an operator by calling CentrifugeRouter.enable(<vault_address>). It will take the msg.sender the entity that's calling the centriugeRouter and assign to it, the router as an operator

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

No branches or pull requests

1 participant