[Wave 10] Replace public Stellar name-resolution stubs with one core implementation #242

Activity

1. truthixify

   added

   Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave program

   on Oct 12, 2026
2. collinsezedike commented on Oct 15, 2026

   

   collinsezedike

   on Oct 15, 2026 – with Drips Wave

   Contributor

   More actions

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

   GM Truth, let me help you with this issue.

   ℹ️ Repo Maintainers: To accept this application, review their application or assign @collinsezedike to this issue.
3. LuckyBeekeper commented on Oct 17, 2026

   

   LuckyBeekeper

   on Oct 17, 2026 – with Drips Wave

   More actions

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

   Hello Maintainer, I have carefully reviewed the issue and understand what is expected. I am confident I can work toward a solution that meets the requirements. I would appreciate the opportunity to take it on.

   ℹ️ Repo Maintainers: To accept this application, review their application or assign @LuckyBeekeper to this issue.
4. carelessdept commented on Oct 17, 2026

   

   carelessdept

   on Oct 17, 2026 – with Drips Wave

   Contributor

   More actions

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

   I just completed #238 (merged in PR #252) for Wave 10 and already have the monorepo built and tested locally. For #242, I will:

   1. Implement a typed core Wraith Names resolver in @wraith-protocol/sdk (Stellar module) supporting AbortSignal, network validation, cache semantics, and typed error codes for malformed/wrong-network responses.
   2. Refactor useStellarName in packages/sdk-react/src/hooks.ts and packages/sdk-svelte/src/primitives/useStellarName.ts to replace the 500ms null timer stub with the shared core resolver, exposing loading, cancellation, and typed error states.
   3. Add unit and parity tests in sdk, sdk-react, and sdk-svelte/test/stellarParity.test.ts covering found, missing, malformed, wrong-network, and aborted requests, and update the API docs.

   ℹ️ Repo Maintainers: To accept this application, review their application or assign @carelessdept to this issue.
5. beulah7717108-eng commented on Oct 17, 2026

   

   beulah7717108-eng

   on Oct 17, 2026 – with Drips Wave

   More actions

   @beulah7717108-eng has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

   Hello maintainer,

   I am a professional full-stack developer, I would like to work on issue #242 [Wave 10] Replace public Stellar name-resolution stubs with one core implementation for wraith-protocol/sdk.

   Proposed Plan
   Core Resolver Implementation: Build a robust, typed core resolver for the configured Wraith Names contract within the core package, completely replacing the placeholder timer stubs.

   Unified Framework Wrappers: Update both sdk-react and sdk-svelte packages so their respective useStellarName hooks consume the shared core resolver, supporting loading states, request cancellation, and typed errors.

   Testing & Edge Cases: Implement thorough test coverage verifying behavior for found entries, missing lookups, malformed payloads, wrong-network states, and aborted requests.

   Documentation: Clear up network configuration guidelines and caching semantics in documentation, ensuring no mock timer stubs are presented as production functionality.

   Please kindly assign this issue to me.

   ℹ️ Repo Maintainers: To accept this application, review their application or assign @beulah7717108-eng to this issue.
6. annacodervibe commented on Oct 17, 2026

   

   annacodervibe

   on Oct 17, 2026 – with Drips Wave

   More actions

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

   I would like to work on this issue. I have experience with Rust and Soroban smart contract development. I will follow the acceptance criteria and add tests. Excited to contribute. Kindly assign.

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

   assigned

   carelessdept

   on Oct 17, 2026
8. drips-wave commented on Oct 17, 2026

   

   drips-wavebot

   on Oct 17, 2026 – with Drips Wave

   More actions

   Congratulations, @carelessdept! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

   🧑‍💻 @carelessdept: 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 🌊
9. truthixify

   closed this as completedin #261on Oct 18, 2026
10. drips-wave commented on Oct 18, 2026

    

    drips-wavebot

    on Oct 18, 2026 – with Drips Wave

    More actions

    This issue has been completed by @carelessdept as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @carelessdept: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.