PegasusSwap

Cronología del incidente

1. 2026-07-14 Filed after user report of wrong-memo RUNE deposit and operator's recovery-process response. Operator's stated process required a second matched-amount deposit + dual-transaction screenshots + 4-5 week window + 'processing fees for certain types.' Curator read: this is the frustrate-to-abandonment pattern common to shame-list-shaped operators; while a wrong-memo deposit is genuinely the user's mistake, the recovery process should be a manual reconciliation against on-chain proof, not a customer-borne re-deposit-and-photograph exercise.
2. 2026-07-14 kyc.rip compensated the user for half of the loss from the swap-platform budget as an attitude signal — not a settled remedy, just marking that the process response was not acceptable. Curator (on behalf of xmr.club editorial) reached out to the operator with the framing: 'put yourself in the user's position; this reads as disguised fund-taking.' Requested a list of pair/memo-required chains where this failure mode can arise, so kyc.rip can disable those pairs at its routing layer for future customers.
3. 2026-07-14 Operator responded that if the recovery-process framing is unacceptable, they will fully compensate the swap in question. Additionally offered to share the list of pairs where the wrong-memo failure mode is possible so kyc.rip can disable them at its routing layer proactively. Positive-response signal — the operator recognized the pattern and offered a systemic fix rather than a one-off apology. Follow-up: confirm full compensation lands + receive the pair list within 14 days. If both, incident closes with grade held at B and a routing-layer pair filter live on kyc.rip's side. If either doesn't land, grade re-evaluation goes on the docket.
4. 2026-07-21 Operator delivered on the systemic-fix commitment from the 2026-07-14 incident open. Per user report, PegasusSwap has filtered out all pairs where the wrong-memo recovery-process failure mode can occur (memo-required chains like RUNE, XLM, EOS, XRP, ATOM, ALGO — anything where a missing memo means the deposit can't be automatically credited). That was exactly the systemic ask on the original curator pushback. Incident marked resolved. Grade held at B. No routing-layer pair filter on kyc.rip side needed — the operator handled it upstream.