-
Notifications
You must be signed in to change notification settings - Fork 53
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
End to end Multichain Faucet Implementation #572
Comments
In order to avoid making contract changes we must first test out the behavior of Safe.call with an encoded multicall function. In the scenario where the config.amount exceeds or below we expect the txn to revert. If this works, we may need to have the designs reflect this by making sure the total amount the user claims equals 1.0 or 0.1 ETH exactly. @mayanksayshi Created eng tracking here: #575 |
Was able to get a working multicall claim without making contract changes and tested the 3 scenarios:
We can exclude contract changes but need to make sure two things are scoped into the design and eng:
We should now be able to complete eng scoping and iterate towards a final design with @mayanksayshi |
This is a continuation of the efforts started here: #509
We need to provide a claim flow that allows users to claim to multiple chains, specifycing amounts for each chain. This will change the way the faucet works at all levels (contract, backend service, and front-end experience). It will make claiming 1 smooth step and will take the cost of bridging away from the user.
The text was updated successfully, but these errors were encountered: