fix: fix asynchronous issue with resolveAddress in populate function

[0xlora]

• Because this PR includes a bug fix, relevant tests have been included.
• Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
• I didn't do anything of this.

---

In the populate function, the resolveAddress call was not awaited, causing the returned Promise<string> to be assigned directly to pop.to, which expects a string. I've added await to correctly resolve the address before assignment. This ensures the function works as expected, resolving the promise to the actual address string.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 549db6f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 11, 2025 7:02pm