Gasless signed `.wraith` name registration on Stellar

[truthixify]

Labels: Stellar Wave, stellar, feature, drips, help-wanted
Tier: L (1–2 weeks)
Type: feature

Context

Today, registering a .wraith name on Stellar requires the user to hold and spend XLM. This is a real onboarding friction for users who arrive via fiat onramp and don't yet hold native asset. EVM WraithNames already supports registerOnBehalf() with an EIP-712 signature so a relayer (e.g., Spectre) can pay the fees.

We want feature parity on Stellar.

Scope

Add to contracts/stellar/wraith-names/:

1. A new entrypoint register_on_behalf(owner: Address, name: String, meta_address: BytesN<66>, signature: BytesN<64>, expiry: u64) where:
   • signature is an ed25519 signature by owner over a SHA-256 hash of a canonical message domain || "wraith-names:register" || name || meta_address || expiry.
   • expiry is a Stellar ledger sequence after which the signature is invalid.
2. Verification logic on-chain using Soroban's env.crypto().ed25519_verify(...).
3. Replay protection — track used signature hashes in storage (or use nonces, justify either choice).
4. Equivalent update_on_behalf and release_on_behalf.
5. Tests covering: success, wrong signer, expired, replay attempts, malformed inputs.

Open design questions to address in the PR

• Where does the "canonical message" definition live so SDK and contract stay in sync? Propose a WRAITH_NAMES_DOMAIN constant.
• Should the relayer receive a tip from the contract caller (paid out of pre-funded balance) or is gas-sponsorship sufficient for now? Argue.
• What's the storage cost of replay protection? Look at issue #06 (budget profiling) for the framework.

Acceptance criteria

• New entrypoints implemented with full unit and property test coverage.
• Replay protection demonstrated by adversarial tests.
• SDK follow-up issue filed describing how to construct the signed message (mirror signNameRegistration from sdk/src/chains/stellar/).
• Demo follow-up issue filed for surfacing the new flow in the UI.
• Spectre follow-up issue filed for using this as the default registration path when an agent's Stellar wallet is unfunded.

Why this matters

This is the only path to "create your Wraith name during signup" UX. Without it, every new Stellar user hits a XLM funding wall before they can claim identity.

Resources

• EVM reference: contracts/evm/contracts/WraithNames.sol::registerOnBehalf
• Soroban ed25519 verify: https://docs.rs/soroban-sdk/latest/soroban_sdk/crypto/struct.Crypto.html#method.ed25519_verify

[sudo-robi]

@sudo-robi has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer I'm a full stack dev and smart contract dev let me help you resolve this issue.

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

[clintjeff2]

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

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

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

[sudo-robi]

Hi @truthixify i haven't been assigned to help you with this issue, please assign me

[drips-wave]

Congratulations, @sudo-robi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @sudo-robi: 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 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @sudo-robi as part of the Stellar Wave Program's 5th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor implemented the on_behalf registration, update, and release functions on Stellar using Ed25519 signature verification and replay protection. The PR includes high-quality logic, custom error handling, and comprehensive unit and property tests that fulfill the core technical requirements of the issue.

😎 @sudo-robi: You earned 400 Points for completing this issue! After the current Wave ends, 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.