Skip to content

#324 FeeRefundRecord type and its storage key are unused scaffolding …#415

Open
Priest-Codes wants to merge 1 commit into
HubDApp:mainfrom
Priest-Codes:#324-FeeRefundRecord-type-and-its-storage-key-are-unused-scaffolding-for-a-never-built-feature-FIX
Open

#324 FeeRefundRecord type and its storage key are unused scaffolding …#415
Priest-Codes wants to merge 1 commit into
HubDApp:mainfrom
Priest-Codes:#324-FeeRefundRecord-type-and-its-storage-key-are-unused-scaffolding-for-a-never-built-feature-FIX

Conversation

@Priest-Codes

Copy link
Copy Markdown

Findings:
The codebase contained dead/unused scaffolding for a planned but never-implemented fee-refund feature.
Two definitions were identified that were never used anywhere in the contract:
FeeRefundRecord struct in types.rs
ExtensionKey::FeeRefundRecord(u64) variant in storage_keys.rs
Fix Features Applied:

Completely removed the unused FeeRefundRecord struct definition.
Completely removed the unused FeeRefundRecord(u64) variant from the ExtensionKey enum.
Result: Clean removal of dead schema with no impact on any existing functionality.
Benefits of the Fix:

Eliminates dead code
Reduces contract size
Prevents future confusion from unused storage types
Keeps the codebase maintainable and clean

CLOSE #324

@drips-wave

drips-wave Bot commented Jul 23, 2026

Copy link
Copy Markdown

@Priest-Codes Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FeeRefundRecord type and its storage key are unused scaffolding for a never-built feature

1 participant