You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
my_recent_swaps RPC currently provides a comprehensive list of swap events for both v1 and v2 protocols. However, there is a need to streamline the process for users who rely on specific event types, such as MakerPaymentRefundFailed and TakerPaymentSpendFailed, for their workflows.
Problem
Users, particularly those operating seed and maker nodes, have expressed concerns regarding the transition to database-driven swap data management. The absence of JSON files for v2 swaps poses challenges for existing processes that depend on these files for statistics, recovery, and refund operations.
Proposed Solution
Introduce filters within the my_recent_swaps RPC call to allow users to retrieve swaps that have specific events. This enhancement will significantly reduce the overhead of manually searching through swap data and improve the efficiency of recovery and refund workflows.
Benefits
Simplifies the process of identifying and recovering failed swaps.
Maintains compatibility with existing systems that depend on JSON file outputs.
Additional Considerations
Explore the feasibility of an RPC call to edit swap data/events in the database for cases where manual intervention is required.
This issue aims to address the concerns raised in the discussion with @cipig regarding the impact of database changes on maker nodes operations and the potential for a streamlined swap event filtering. Related comment: #2043 (comment)
The text was updated successfully, but these errors were encountered:
Overview
my_recent_swaps
RPC currently provides a comprehensive list of swap events for both v1 and v2 protocols. However, there is a need to streamline the process for users who rely on specific event types, such asMakerPaymentRefundFailed
andTakerPaymentSpendFailed
, for their workflows.Problem
Users, particularly those operating seed and maker nodes, have expressed concerns regarding the transition to database-driven swap data management. The absence of JSON files for v2 swaps poses challenges for existing processes that depend on these files for statistics, recovery, and refund operations.
Proposed Solution
Introduce filters within the
my_recent_swaps
RPC call to allow users to retrieve swaps that have specific events. This enhancement will significantly reduce the overhead of manually searching through swap data and improve the efficiency of recovery and refund workflows.Benefits
Additional Considerations
This issue aims to address the concerns raised in the discussion with @cipig regarding the impact of database changes on maker nodes operations and the potential for a streamlined swap event filtering. Related comment: #2043 (comment)
The text was updated successfully, but these errors were encountered: