chore: screening optimisations

[defispartan]

General Changes

• Disable screening endpoint call for mocked address

To test: check different combinations of connecting, disconnecting, and switching between normal and mocked wallet and check that no request is made to https://aave-api-v2.aave.com/addresses/status?address for mocked wallet

Developer Notes

Does not use existing watchModeOnlyAddress parameter which is exported from Web3Provider because currentAccount and watchModeOnlyAddress are updated asyncronously

---

Author Checklist

Please ensure you, the author, have gone through this checklist to ensure there is an efficient workflow for the reviewers.

• The base branch is set to main
• The title is using Conventional Commit formatting
• The Github issue has been linked to the PR in the Development section
• The General Changes section has been filled out
• Developer Notes have been added (optional)

If the PR is ready for review:

• The PR is in Open state and not in Draft mode
• The Ready for Dev Review label has been added

Reviewer Checklist

Please ensure you, as the reviewer(s), have gone through this checklist to ensure that the code changes are ready to ship safely and to help mitigate any downstream issues that may occur.

• End-to-end tests are passing without any errors
• Code style generally follows existing patterns
• Code changes do not significantly increase the application bundle size
• If there are new 3rd-party packages, they do not introduce potential security threats
• If there are new environment variables being added, they have been added to the .env.example file as well as the pertinant .github/actions/* files
• There are no CI changes, or they have been approved by the DevOps and Engineering team(s)
• Code changes have been quality checked in the ephemeral URL
• QA verification has been completed
• There are two or more approvals from the core team
• Squash and merge has been checked

[drewcook]

LGTM 👍

[github-actions]

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	471.43 KB (🟡 +46 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

[github-actions]

• Ipfs hash: bafybeifdndwlekqxzfxyx2sxhqc5sk55zjmqb66z7v3ph5ptgd2tpf5lem
• Ipfs preview link: https://bafybeifdndwlekqxzfxyx2sxhqc5sk55zjmqb66z7v3ph5ptgd2tpf5lem.ipfs.cf-ipfs.com/

[github-actions]

• Ipfs hash: bafybeibsavurbfmtotmg4qbyt2ru4ucmclctwjwrqoacscpnshe32grqja
• Ipfs preview link: https://bafybeibsavurbfmtotmg4qbyt2ru4ucmclctwjwrqoacscpnshe32grqja.ipfs.cf-ipfs.com/

[github-actions]

• Ipfs hash: bafybeifidaxajta3xzanal74kk7b6q2npicuixdiisc6st2sdyrqxylj34
• Ipfs preview link: https://bafybeifidaxajta3xzanal74kk7b6q2npicuixdiisc6st2sdyrqxylj34.ipfs.cf-ipfs.com/

[MareskoY]

all good,
but I found one more point where we could optimise request

case

1. connect via any wallet = request https://aave-api-v2.aave.com/addresses/status?address
2. open the switch wallet modal and choose any option (walletconnect)
3. cancel connect

result:

• after canceling we again sent a request https://aave-api-v2.aave.com/addresses/status?address with the address from the step1 for which we already connect

I think we don't need to make a second request
cc @defispartan

[defispartan]

all good, but I found one more point where we could optimise request

case

1. connect via any wallet = request https://aave-api-v2.aave.com/addresses/status?address

2. open the switch wallet modal and choose any option (walletconnect)

3. cancel connect

result:

* after canceling we again sent a request https://aave-api-v2.aave.com/addresses/status?address with the address from the step1 for which we already connect

I think we don't need to make a second request cc @defispartan

Unfortunately, this isn't something that can be changed on the interface side. The account variable of the Web3React library determines which wallet is connected so if this is not being updated correctly there's no way to modify it

[github-actions]

• Ipfs hash: bafybeia642a4an6nyocsz5kk4huoevk7qnnhrdeu7zexjcaqave7aizlsq
• Ipfs preview link: https://bafybeia642a4an6nyocsz5kk4huoevk7qnnhrdeu7zexjcaqave7aizlsq.ipfs.cf-ipfs.com/