denylist-stuck-messages

To denylist stuck messages and prevent relayer failures, this skill parses provided message IDs, validates their format, and updates the relayer denylist configuration. It modifies the TypeScript customBlacklist.ts file and opens a GitHub PR for deployment.

Updating a relayer denylist involves reading input message IDs, validating their formats, and grouping them by destination when applicable. The workflow then updates the customBlacklist.ts configuration file and initiates a GitHub PR for review and deployment.

Yes, you can use this denylist workflow for a specific app context and environment by providing parameters like app_context=USDC/mainnet-cctp-v2-standard. This focuses the denylist update and PR creation on the correct relayer configuration.

You can automate PR creation for relayer configuration updates by using this skill to modify the customBlacklist.ts file with validated message IDs. It automatically initiates a GitHub PR to review and deploy the corrected denylist.

Stuck messages affect downstream processing by causing relayer failures, but denylisting specific message IDs prevents these problematic messages from impacting operations. This protects the relayer by skipping the stuck messages during processing.