Can secp256k1 import be moved to top-level in recoverPublicKey?

[TrejGun]

Hi viem team 👋

I noticed that in recoverPublicKey the secp256k1 curve is imported dynamically inside the function:

const { secp256k1 } = await import('@noble/curves/secp256k1')

This makes the function async, while logically the operation itself is fully synchronous.

In most other places in the codebase, secp256k1 is imported at the top-level, so I wanted to ask about the intent here.

From my perspective:

• This file already depends on crypto-specific logic
• Making the function async only for the import adds unnecessary async surface
• A static import would simplify the API and implementation
• Bundlers today generally handle tree-shaking of @noble/curves well

Questions:

• Is there a specific reason this import is kept dynamic here?
• Would you be open to a PR that moves the import to the top-level and makes recoverPublicKey synchronous?
• If I submit such a change, is this something you would consider merging?

Happy to open a PR if this aligns with the project’s direction. Thanks!