Project name limitations

[tupui]

We should store the project differently than the Soroban Domains name. These can be different.

This can also open the door to pointing to the same domains as to support organizations - #336

That means that we need to have the project name stored in IPFS as metadata. Then the UI needs to be adjusted to show both project name and the Soroban Domains name.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[KodeSage]

@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi @tupui! I’d love to work on Tansu and contribute to the Project Name Limitations issue. I’m quite familiar with your project.

You can check out my profile to see my contributions to the most important projects within the Stellar ecosystem!!

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

[Josue19-08]

@Josue19-08 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello maintainers 👋

I’m Josué, an experienced open-source contributor with a strong background in blockchain-oriented systems and full-stack development. I’ve worked on multiple projects involving Stellar and Soroban smart contracts, backend APIs, and frontend applications built with React, always paying close attention to code organization, performance, and user experience.

I’m used to contributing in collaborative open-source environments and understand the importance of clear scope definition, clean implementations, and maintainable solutions. From initial analysis to final pull request, I follow a structured approach that ensures reliability and long-term value for the project.

This issue is well aligned with my experience, and I’m confident I can provide a high-quality solution efficiently. Feel free to check my GitHub profile to review my previous contributions and technical work across different repositories.

I’m excited about the opportunity to contribute, collaborate with the maintainers, and help push this task to completion with a professional and results-driven mindset.

Best regards.

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

[drips-wave]

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

🧑‍💻 @KodeSage: 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.

⚠️ Important: When opening a PR, please link it to this issue to ensure it gets tracked accurately.

🤠 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 🌊