Wagyu

Cronología del incidente

1. 2026-06-19 Operator (@PerpetualCow) last public reply on X on Wagyu-adjacent topics.
2. 2026-07-06 Third-party outage report (@BerggoldDigital tweet + screenshot): swap widget returns "Failed to fetch" on 0.5 XMR → DAI. Reporter notes operator has gone quiet.
3. 2026-07-07 Widget partially recovered — /api/rates responds 200 across XMR pairs (DAI/BTC/ETH/SOL/USDC). Two XMR → ETH swaps executed in the last two hours after a 56-day gap in transactions of any kind. But the operator has posted an explicit "Swaps into XMR are temporarily paused" banner on the ANY → XMR direction — the unwind route that would return an XMR1 IOU on HyperCore to native Monero. Grade dropped B- → D on the same day. Operator remains silent on Wagyu channels; publicly active on Hyperliquid memecoin ecosystem.
4. 2026-07-07 Wagyu widget reported down again by curator ~11:30Z, ~30 minutes after the partial-recovery observation earlier the same morning. Server-side probes: homepage 200, /swap 200, /api/rates 200 — but the /api/rates payload is byte-identical to the earlier 09:30Z probe, suggesting the rate-source is serving a cached/stale response rather than live-fetching. Combined with the operator-declared "Swaps into XMR are temporarily paused" banner on the ANY → XMR path and the 56-day inbound-transaction gap, the service is now fluctuating within a single day AND the "recovered" state was itself misleading. This is the pattern the earlier D-grade was watching for.
5. 2026-07-07 Operator @PerpetualCow broke silence at 17:40Z on X after 18+ days of no public replies on Wagyu-side topics — first substantive comms since 2026-06-19. Key claims: (a) Wagyu is back live; (b) the downtime was caused by "a massive DDoS attack"; (c) implicit accusation that a competitor orchestrated it. Tone is dismissive of user feedback ("Not even going to bother responding to all the FUD"), boastful about market position ("only 2 sources of XMR: KuCoin and Wagyu; everything else is a wrapper"), and closes with "Going back to my holiday, gn friends." Curator read: the DDoS attribution is unverifiable but plausible, and comms restart IS a positive signal against the "operator vanished" concern. However the post does NOT address the still-live "Swaps into XMR are temporarily paused" banner on the ANY → XMR direction, the intra-day quote-then-fail pattern from earlier today, or the 56-day gap in ANY-inbound transactions — meaning the specific operational issues that drove the D grade are unresolved. The "only 2 sources of XMR" claim is also editorially questionable (ignores DEXes, atomic swaps, direct P2P) and does not match reality of the swap-engine landscape our own listings cover. Grade held at D. Watch conditions unchanged: lift requires resumed ANY → XMR execution + clean curator round-trip test-swap + sustained cadence (not one-off post). Escalation still on the table if the paused-banner is up at the 2026-07-12 re-check.
6. 2026-07-07 ANY → XMR path is materially back. Widget "Swaps into XMR are temporarily paused" banner has been REMOVED; a DAI → XMR quote renders live (1000 DAI → 2.975812 XMR, ~$1000 → ~$981, matches sane pricing at ~336 DAI/XMR); Swap button enabled. Recent Transactions strip shows FIVE ANY → XMR trades completed in the last 40 minutes (100 DAI → XMR 26m ago, 1 ETH → XMR 26m ago, 0.33 ETH → XMR twice at 34/35m ago, 400 DAI → XMR 40m ago) plus one XMR → ETH at 29m — real bidirectional throughput after ~56 days of one-way-only. Timing lines up with the operator @PerpetualCow going-public post at 17:40Z (~40 min before the earliest of these swaps). Grade held at D for now — this is 40 minutes of data, not a track record — but the operational side of the D case has meaningfully improved. Watch: if ANY → XMR stays open through 2026-07-09 with no re-pause AND a curator round-trip test-swap completes clean, lift to C.
7. 2026-07-08auto Relative to the on-file state (ANY→XMR paused; operator silent), material recovery signals appeared on 2026-07-07: operator @PerpetualCow claimed Wagyu was back after an unverified DDoS, and @xmr_club reported the pause banner gone with both-direction swaps executing. A third-party post on 2026-07-08 also said the s…