Context
contracts/oracle/src/lib.rs line 290, purge_submitter(env: Env, caller: Address, feeder: Address) removes a submitter, implying there's a set of tracked active submitters — but no getter exposes that set (unlike role_members() for role-based membership).
Why it matters
An operator deciding whether to purge_submitter for inactivity or misbehavior has no on-chain way to see the current submitter roster to know who's even eligible for review, and must reconstruct the list from event history instead.
Suggested approach
If submitters are tracked via the Feeder role (check Role enum usage in this contract), this may already be coverable by the existing role_members()-equivalent for oracle roles — if so, just document that purge_submitter targets should be sourced from role_members(Role::Feeder); if submitters are tracked separately, add a dedicated getter.
Context
contracts/oracle/src/lib.rsline 290,purge_submitter(env: Env, caller: Address, feeder: Address)removes a submitter, implying there's a set of tracked active submitters — but no getter exposes that set (unlikerole_members()for role-based membership).Why it matters
An operator deciding whether to
purge_submitterfor inactivity or misbehavior has no on-chain way to see the current submitter roster to know who's even eligible for review, and must reconstruct the list from event history instead.Suggested approach
If submitters are tracked via the
Feederrole (checkRoleenum usage in this contract), this may already be coverable by the existingrole_members()-equivalent for oracle roles — if so, just document thatpurge_submittertargets should be sourced fromrole_members(Role::Feeder); if submitters are tracked separately, add a dedicated getter.