Investigate memory leaks in /emissions module causing high RAM usage

[rapidfix]

The gopher node (blockchain node) has been experiencing OOMKills due to high memory usage (83% of 64GB limit), with recent observations showing it approaching 60GB of RAM usage. This aligns with the Cosmos SDK memory leak issue cosmos/cosmos-sdk#22657, which indicates known memory bloat under heavy transaction loads.

Action Required: Investigate the /emissions module for:

• Memory leaks in state management
• Unbounded state growth patterns
• Inefficient data structures or caching mechanisms

Context: This node is critical for testnet stability (our primary user engagement channel), and current memory pressure may impact user experience. The node's resource footprint is unusually high compared to standard Cosmos nodes. We should prioritize this to prevent further OOMKills and improve testnet reliability.

Suggested next steps:

1. Profile memory usage with pprof during transaction spikes
2. Audit state storage patterns in /emissions module
3. Compare with Cosmos SDK's recommended state management practices

This issue requires urgent attention to prevent user-facing disruptions on testnet.