search

passportxyz / passport

Passport allows users to prove their identity through a secure, decentralized UI
Other
982 stars 456 forks source link

Optimize calls to Alchemy API #1368

Open michaelgreen06 opened 1 year ago

michaelgreen06 commented 1 year ago

We should restrict Alchemy api keys to specific domains/IPs. It's possible that a lot of the calls we're making through Alchemy could be routed through the user's metamask RPC.

The keys are currently being used in: IAM, Passport Frontend, Scorer Frontend, Scorer Backend, Staking. There could be additional places where the keys are being used.

Other Context

On June 14th 2023 @lucianHymer cut the ID Staking App off from Alchemy. It was being used for polling a user's wallet for GTC balance and for ENS resolving with community staking. It was cut off because it was consuming a huge amount of our alchemy compute units and was only providing minimally useful features. Getting these features back likely is dependent on overhauling the ID staking code because it is very inefficient right now. Overhauling ID staking is currently low priority considering our current priorities of scaling and also the uncertain future of GTC staking more broadly.

lucianHymer commented 1 year ago

I think the goal of this ticket is more clearly defined in https://github.com/gitcoinco/passport/issues/1370