Support Metadata Input on Package Creation

[Cedarich]

Description

Allow the caller to pass metadata into create_package instead of always using an empty map.

Requirements

• Update create_package signature to accept metadata: Map<Symbol, String>.
• Store the provided metadata in the Package struct instead of constructing an empty map.
• Add tests creating a package with some metadata keys and validating they are stored and retrievable.
• Consider basic constraints (for now just rely on gas limits; no hard limit required).

Complexity

• Level: 150

[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

[abdulomeiza]

@abdulomeiza has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I am a Full Stack Developer specializing in Next.js,Python, TypeScript, Node.js,Rust, PostgreSQL,Oracle, JavaScript and DevOps Engineering. With over 50 contributions across projects in web3 and specifically stellar ecosystem, I’ve developed strong proficiency in delivering high-quality solutions and resolving complex issues within tight deadlines. My experience spans frontend, backend, smart contracts, and the optimization and maintenance of scalable codebases.
I can handle this task. Kindly assign.

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

[drips-wave]

Congratulations, @abdulomeiza! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @abdulomeiza: 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 issued 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 🌊

[devJaja]

@devJaja has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I work on this issue, I will deliver on time

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

[soomtochukwu]

@soomtochukwu has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hey, let me take this off your plate quickly :]

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

[Escelit]

@Escelit has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'd like to work on this metadata support feature because it adds crucial flexibility to the package system, enabling use cases like package descriptions, versioning info, and custom attributes without requiring contract changes.

Relevant Experience:

1. Soroban Contract Development: Experience with Soroban's Map type and storage patterns, understanding its gas implications and limitations.

2. Data Structure Design: I've implemented similar extensible data patterns in smart contracts where future-proofing is essential.

3. Testing Expertise: Proficient at writing comprehensive tests for storage operations and data integrity validation.

Implementation Approach:

• Update create_package function signature to include metadata: Map<String, Bytes>
• Store metadata directly in the Package struct without additional validation (gas-based limits only)
• Add tests covering: empty metadata, single key-value, multiple entries, and various value types
• Ensure metadata is properly retrieved in view functions
• Document gas considerations for large metadata maps

This small change significantly increases the contract's utility while maintaining simplicity and gas efficiency.

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

[DokaIzk]

@DokaIzk has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Gm can I work on this?

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

[rachealkenny]

@rachealkenny has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi Maintainer! I'm interested in implementing the metadata input support for package creation, updating the function signature to accept a Map and ensuring it's properly stored and retrievable in the Package struct. I have experience with Move and can add comprehensive tests to validate the metadata behavior while respecting gas constraints.

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