-
Notifications
You must be signed in to change notification settings - Fork 50
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
feat: APP-2699 - Use Aragon Gateway for RPC requests #1200
Conversation
8b7ed45
to
8d983f6
Compare
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.
Looks good to me, hopefully we caught everything 😅
}); | ||
} else return signer?.provider; | ||
}, [network, signer?.provider]); | ||
const provider = useMemo( |
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.
@sepehr2github Do you know why we are bypassing the signer provider on Polygon and Mumbai?
1322dcf
to
ea2bf80
Compare
WebApp IPFS Hash: QmRcGW7c6W1Vd7gdsbuFVBPT1DpqPpKU6GQRz2SidBXC9G |
WebApp IPFS Hash: QmZ5GkhiB4T5cXfT167Scmc2tb8hTUXC2aAeVqEWcbVsnR |
Description
VITE_INFURA_MAINNET_PROJECT_ID
toVITE_GATEWAY_RPC_API_KEY
Task: APP-2699
Type of change
Checklist:
CHANGELOG.md
file in the root folder.