-
Notifications
You must be signed in to change notification settings - Fork 1
Exploring tooling, testing scenarios for an Alpha,Beta rollout
A braindump of testing ideas and tooling enhancements subject to revision.
Due to chain, deputy timing discrepancies, front-running potential, and processing delays: Claim the near-expired transaction, and refund it at the opposite end.
Identify any circumstances to process a swap transaction more than once at each chain. Please note, once a Swap transaction is processed, it generates a chain event which the Deputy reads and sends to the next chain-hop.
Examine temporal/qualitative side-effects upon Deputy operational resumption for incomplete single-chain swap trx (HTLT, Claim, Refund).
Replay concurrently with Deputy and post Deputy processing at any stage.
Stress testing above scenarios etc... Side note, Deputy is not employing concurrency for processing swaps other than tracking the chains block activity.
Trx_log Eth transaction hash uniqueness violations have been observed under artificial debugging scenarios.
Examine Uniswap token pricing swings with open swap profit-earning potential.
Trigger Report for high balance relays, token value, circulation swings.
Velocity alerts--not only spikes but frequent repeat activity.
Correlate Deputy swap activity with chain Defi activity, Avalanche, Uniswap, Dex, etc.
Single E2E transaction tracing responding to customer inquiries.
Submit full or partial swap (HTLT, Claim, Refund) transactions at either direction with test networks baked-in. Optionally bypassing deputy.
Display balance and fund relay post-effects for single executed swaps (E-money <-> Eth) Stakeholders (Chains' 2 deputies, swap contract approval balance, token balance, e-Money supply balances, user(s).
Aggregate effects for x concurrent swap operations by time, by trx ids, address.