-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add USDGLO as recurring donation token #1810
Comments
@HrithikSampson - want to try this one out Recurring donations use Superfluid in the background https://www.superfluid.finance/ - this feature is ONLY deployed on Optimism on Giveth atm. how it works is we have an underlying token which is a regular ERC-20 token such as USDGLO in this case, the underlying token needs to get wrapped in the super token contract, converting it to USDGLOx - this allows the token to be "streamed" from one address to another We'll need to configure setting up USDGLO as an elegible token to deposit and stream using the recurring donations feature Check out how we handle other eligible ERC20 tokens such as USDC, DAI, GIV and OP @CarlosQ96 and @mohammadranjbarz should be able to support you with info |
From the FE when I try to open the token drop down menu from the recurring donation page I get an application error Screencast.2024-10-01.14.00.15.mp4 |
@divine-comedian , I had a small doubt is it coming sometimes or all the time. I couldnt duplicate the error. |
working now on production! https://optimistic.etherscan.io/tx/0x233ab8872a0925ca45a114656c0bef5ba97894ec032fb0b74e94cdc9b1836a32 |
We should add USDGLO as an option to donate for recurring donations made on Optimism
They have already added their Super Token which can be found here:
https://optimistic.etherscan.io/address/0x9f41d0aa24e599fd8d0c180ee3c0f609dc41c622
We have also added USDGLO into the dapp so the token icon should be ready. Here is the underlying token address
https://optimistic.etherscan.io/address/0x4f604735c1cf31399c6e711d5962b2b3e0225ad3
Since there is no testnet version we will need to test this in production
AC:
The text was updated successfully, but these errors were encountered: