Change Details

This resolves [ENG-2593](https://linear.app/comm/issue/ENG-2593/use-reverserecords-smart-contract-for-bulk-ens-name-lookups). When I start my iOS app, it needs to resolve 142 ENS names to build the in-memory search indices for @-mentioning and inbox search. Before this diff, this meant 142 individual network requests to Alchemy. After this diff, it requires only 1. Depends on D9524

This resolves [ENG-2593](https://linear.app/comm/issue/ENG-2593/use-reverserecords-smart-contract-for-bulk-ens-name-lookups). For more info about this smart contract, see [official ENS docs](https://docs.ens.domains/dapp-developer-guide/resolving-names#reverse-resolution) and [GitHub repo](https://github.com/ensdomains/reverse-records). When I start my iOS app, it needs to resolve 142 ENS names to build the in-memory search indices for @-mentioning and inbox search. Before this diff, this meant 142 individual network requests to Alchemy. After this diff, it requires only 1. Depends on D9524

This resolves [ENG-2593](https://linear.app/comm/issue/ENG-2593/use-reverserecords-smart-contract-for-bulk-ens-name-lookups). For more info about this smart contract, see [official ENS docs](https://docs.ens.domains/dapp-developer-guide/resolving-names#reverse-resolution) and [GitHub repo](https://github.com/ensdomains/reverse-records). When I start my iOS app, it needs to resolve 142 ENS names to build the in-memory search indices for @-mentioning and inbox search. Before this diff, this meant 142 individual network requests to Alchemy. After this diff, it requires only 1. Depends on D9524