-
Notifications
You must be signed in to change notification settings - Fork 3
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
Implement Fallback to User Balance for Transactions When Relayer Fails #26
Conversation
@@ -302,30 +322,81 @@ export class FastAuthWalletConnection { | |||
); | |||
newUrl.searchParams.set('success_url', callbackUrl || currentUrl.href); | |||
newUrl.searchParams.set('failure_url', callbackUrl || currentUrl.href); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice but with time these params can be removed for simplicity so that we have iframe only logic 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let's open a ticket for this clean up! Will be amazing to remove the duplicated logic
This PR introduces a fallback mechanism for transactions when the relayer service fails to relay them due to specific issues such as actions not being allowed or the sender/receiver not being whitelisted. In such cases, the transaction will be retried using the user's own balance, ensuring that the transaction can still be processed without dependency on the relayer's current state or configuration. This enhancement improves the robustness of transaction handling by providing an alternative path for transaction completion.