feat(contract): add get_all_meters admin function to list all registered meter IDs

[Dev-AdeTutu]

Feature Request

Area: Smart Contract
File: contracts/solar_grid/src/lib.rs

Description

There is currently no way to enumerate all registered meters from the contract. The provider dashboard and backend need a way to list all meter IDs to display the registry and run batch operations.

Implementation Guide

Maintain a Vec<Symbol> of meter IDs in instance storage:

`
ust
const METER_LIST: Symbol = symbol_short!("MTRLIST");

// In register_meter, after storing the meter:
let mut list: Vec = env.storage().instance()
.get(&METER_LIST).unwrap_or(Vec::new(&env));
list.push_back(meter_id.clone());
env.storage().instance().set(&METER_LIST, &list);

// New function:
pub fn get_all_meters(env: Env) -> Vec {
env.storage().instance().get(&METER_LIST).unwrap_or(Vec::new(&env))
}
`

Definition of Done

• METER_LIST maintained in instance storage on every register_meter call
• get_all_meters returns full list of registered meter IDs
• Unit test verifies list grows correctly as meters are registered
• Backend GET /api/meters route updated to call get_all_meters
• Provider dashboard fetches live meter list from contract

[morapay-app]

@morapay-app has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I am applying to work on: “feat(contract): add get_all_meters admin function to list all registered meter IDs”. Provider dashboards need enumeration without scanning arbitrary keys. I would maintain METER_LIST in instance storage on register_meter, expose get_all_meters, and align backend GET /api/meters + dashboard fetch per the issue—watching list size so admin reads stay bounded. I have shipped similar Soroban registries before with tests that grow the list across many registrations.

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

[Idrhas]

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

Hi, I'd like to work on this issue, I have experience with the relevant technologies and ecosystem and have previously contributed to similar issues. I’m comfortable working with the codebase and familiar with standard practices.

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

[drips-wave]

Congratulations, @Idrhas! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Idrhas: 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 awarded 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 🌊