Smart Contract Enhancement: Optimize DataKey storage size in Token contract

[p3ris0n]

Category: Blockchain / Smart Contract Development

Objective: Implement Optimize DataKey storage size in Token contract in the core contracts.

Detailed Description: Enhance the contract capabilities by implementing: Optimize DataKey storage size in Token contract. Ensure it adheres to the existing crate structure and includes necessary event emissions.

Acceptance Criteria:

• Code must compile with cargo build --target wasm32-unknown-unknown.
• Must pass cargo clippy without warnings.
• Must include unit tests.

Technical Requirements: Rust, Soroban SDK

Deliverables:

• Contract source code updates
• Tests for the new feature

Testing Requirements:

• Run cargo test and cargo fmt.
• Deploy to Testnet locally and verify invocation.

Estimated Difficulty: Advanced

Points: 200

[modrispath]

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

I'll take this on.

DataKey storage size matters on Soroban since every byte costs ledger rent. The typical optimization is replacing verbose enum variants or string-keyed entries with compact integer discriminants or tightly packed tuple keys, reducing the serialized footprint without changing the logical structure.

I'll audit the existing DataKey enum in the token contract, identify which variants are oversized, and restructure them to minimize storage footprint while keeping the contract logic intact. Event emissions stay in place and aligned with the updated key structure.

Changes will compile clean against wasm32-unknown-unknown, pass clippy without warnings, and include unit tests covering the optimized key paths. cargo test and cargo fmt both pass before the PR opens. Ready to start if assigned.

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