Proposal: Automatic handling of unavailable counterparties
RejectedPR- SIG
- node-deployment-operations
- Champion
- —
- Author org
- —
- Ask
- source pending
Abstract
This proposal introduces an automated, persistent counterparty lifecycle management system in the SV App to handle unresponsive counterparties and those with vetting errors. By shifting counterparty exclusions from in-memory lists to persistent SQL-level anti-joins and isolating failures via recursive batch splitting, this mechanism prevents failing nodes from blocking healthy trigger processing, eliminates manual operator intervention, and scales up to 100M total network parties.
Milestones
No milestones recorded.
Budget impact
- % of approved-to-date
- —
- % if all RFV pass
- —
RFV scenario unavailable — using approved-to-date as denominator (degraded mode).
- Ask (CC)
- amount pending
Comments by org
No public reasons documented.
View discussion on GitHub