Implement Stellar federation resolution with identity verification and caching

[Just-Bamford]

Description

Problem

Federated Stellar addresses require applications to manually perform federation lookups. The SDK has no high-level resolver for converting human-readable federation addresses into account information.

Repeated federation lookups also create unnecessary network traffic and provide no standardized identity verification or caching strategy.

Solution

Implement federation resolution utilities that parse federation addresses, query the configured federation service, validate the response, and cache successful lookups.

The resolver should distinguish account identifiers, memo information, federation domains, and invalid responses.

Acceptance Criteria

• resolveAddress(federationAddress) is implemented.
• Federation addresses are validated before requests are made.
• Account and memo information are returned in a structured response.
• Federation responses are validated against the requested address.
• Successful results are cached with configurable TTL.
• Failed lookups do not poison the cache.
• Cache invalidation is supported.
• Identity verification utilities are provided where federation metadata supports verification.
• Tests cover valid addresses, invalid addresses, failed lookups, cache hits, expiration, and malformed responses.
• Exported through src/account/index.ts and src/index.ts.

Note for Contributors

Do not trust federation responses solely because the HTTP request succeeded. Validate the returned account information and federation domain before returning the result.

[Kappa16]

@Kappa16 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please maintainer assign this issue to me and have it resolved ASAP 🙏

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kappa16 to this issue.

[dot-enny]

@dot-enny has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi there, I'd like to work on this please. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dot-enny to this issue.

[Turawa2]

@Turawa2 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can work on this task , assign me please!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Turawa2 to this issue.

[dakwa001]

@dakwa001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi! I’d like to take this issue. I’ll go through the existing implementation, identify the root cause, and work on a clean solution before submitting a PR for review.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dakwa001 to this issue.

[drips-wave]

Congratulations, @dakwa001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @dakwa001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊