Allow users to donate to Causes using Squid Router

[divine-comedian]

For Donation Agents we should implement Squid Router integration. This will allow users to donate in most chains on most tokens to the cause. we should then bridge and swap those tokens into GIV on Polygon.

So we should be able to use the squid router on the FE and ensure it arrives in GIV on Polygon to the specified address, which will be the Cause's funding pool.

Donations will need to be verified by donation verification service which is handled in a separate BE issue.

As a separate tangent we need to ensure GIV has liquidity on Polygon to make the routing process efficient and smooth. @laurenluz

FE Flow

The user flow for donating to causes should look exactly the same as the current donation flow. take this page as a good example:
https://giveth.io/donate/the-giveth-community-of-makers

• user selects token from the list of supported tokens by Giveth on the given chain
• user can change network from their web wallt or from navbar drop down menu
• user will need to approve and then transfer tokens (two txs to sign) to squid router service
• we do not ask the user for optional donation to giveth since we take 5% fee on distribution
• do not show any modal related to stellar donations
• user cannot select to make a recurring donation

AC

• user cannot see option to make recurring donation
• users can enter donate page for a given cause
• clicking select token and choose which token they want to donate from on selected network
• balances fill for the tokens the users hold that are supported by Giveth on the given network
• user can enter amount of tokens they want to donate
• amount cannot be negative nor can they exceed their current balance of that token
• confirmation modal is shown of summary of their donation
• tx to donate is successful
• user is taken to success page
• do not show optional donation to giveth component
• funds are successfully sent to cause funding pool for cause
• donation data shows on user profile -> donation tab and is correct
• donation data shows on cause donations table and is correct

[divine-comedian]

@markoprljic I can't find the exact view of this from the q/acc files on how they handle depositing tokens using squid router, could you find them and drop a link?

we'll also need a donation success page for when a user successfully donates to a Cause.

[kkatusic]

@divine-comedian we will use Squid Router for donation, ok, what about recurring donation we wont enable that on Cause's project?

[divine-comedian]

@kkatusic recurring donations are not in scope for cause donations - I thought it was in the project documentation but I guesss it was just in my head.

we'll need to hide that element

[markoprljic]

@markoprljic I can't find the exact view of this from the q/acc files on how they handle depositing tokens using squid router, could you find them and drop a link?

we'll also need a donation success page for when a user successfully donates to a Cause.

It seems there isn't a such thing in the designs. Can you provide more info about the integration, an example I can look into and I'll try to understand and create a mockup. Thanks.

[kkatusic]

@kkatusic recurring donations are not in scope for cause donations - I thought it was in the project documentation but I guesss it was just in my head.

we'll need to hide that element

Np @divine-comedian I will hide it.

About this interaction/layout for the end users I suggest that we leave same design, like I said on meeting, user will came on that page on one network, we can check if she are suing Gnosis and suggest to connect to some another. When she is on eligible network she can choose token like it's now on one time donation for the projects. After choosing token, enter amount steps would be same, only what we will include is new approve function and donation function with amount provided by Squid Route.

ps. but like you said @divine-comedian Gnosis should be available in 2 weeks