Problem
The relayer storage key prefix is currently built as ${sourceChain.name}-${sourceChain.name} in packages/cli/src/commands/relayer.ts.
That means different pairs with the same source chain share the same local cache keys. For example, darwinia>ethereum, darwinia>polygon, and darwinia>arbitrum can all share relayer skipped/relayed state under the same prefix.
Observed impact
In production logs, skipped message state can be replayed across pair loops, making it harder to distinguish whether a message is truly pending for a specific source-target pair or just present in shared local cache.
Expected behavior
The key prefix should include both source and target chain names, for example:
{sourceChain.name}-{targetChain.name}
Current status
No immediate fix requested. This issue is only for tracking; current investigation is focused on the ORMPIndexer GraphQL default pagination behavior.
Problem
The relayer storage key prefix is currently built as
${sourceChain.name}-${sourceChain.name}inpackages/cli/src/commands/relayer.ts.That means different pairs with the same source chain share the same local cache keys. For example,
darwinia>ethereum,darwinia>polygon, anddarwinia>arbitrumcan all share relayer skipped/relayed state under the same prefix.Observed impact
In production logs, skipped message state can be replayed across pair loops, making it harder to distinguish whether a message is truly pending for a specific source-target pair or just present in shared local cache.
Expected behavior
The key prefix should include both source and target chain names, for example:
{sourceChain.name}-{targetChain.name}Current status
No immediate fix requested. This issue is only for tracking; current investigation is focused on the ORMPIndexer GraphQL default pagination behavior.