GhostDrip

GhostDrip is a scheduled swap runner that turns Monero DCA into a set-and-forget operation. Approve a capped allowance once, define a strategy (cadence + per-swap amount + destination XMR wallet), and a minimal backend cron fires the swaps against a decentralized router. Strategies auto-delete when finished, on request, or after 3 consecutive failures — the site is designed to hold as little state about you as possible.

Background. Built by @babysolo_ (the solo dev also behind [XMR98](/tools/xmr98)) and launched publicly on 2025-11-17 — so ~8 months of tenure as of listing. Same operator posture: minimal accounts, minimal metadata, XMR-native.

What you trust. *Allowance-scoped, briefly custodial.* You approve a capped ERC-20 allowance to a GhostDrip contract, and when a strategy fires, the operator's server pulls up to that allowance and routes the funds through a swap aggregator on your behalf. Funds pass through operator custody during the pull-and-swap window — it is not a purely non-custodial atomic operation on-chain today (no DEX supports scheduled DCA natively). What you're trusting is bounded by the allowance amount you approved and can be revoked. No signup, no email, no cookies, no analytics per operator claim. Only piece of state kept per strategy is the last execution ID, so you can independently verify the on-chain fill. Auto-deletion after completion / request / 3-strike failure is a structural privacy win, not a bolted-on feature.

Operational specs. DCA target: XMR only. Trigger surface: minimal backend cron. Execution surface: decentralized router (DEX). Fees: no added platform fee per operator claim ("Just DEX & gas"). No account / email / phone required. State retention: capped to the last execution ID per strategy. Delivery: swaps land at the destination XMR address you approve at strategy-creation time — GhostDrip never touches the XMR itself.

Grade rationale. Listed at Grade B because the operator posture is unusually restrained (auto-deleting state, non-custodial by structure, no cookies/analytics per meta), the solo-dev has 8 months of public runway on this tool plus the tenure from XMR98, and the workflow addresses a real gap — every consumer-facing DCA platform we know of demands KYC + accounts. Grade A is withheld pending: (a) a curator test run of a full strategy cycle, (b) verification of the actual DEX router used and its fee behaviour under stress, (c) independent corroboration outside the babysolo ecosystem.

Caveats. *Trust surface is not zero.* Between the allowance-pull and the swap completion, the operator's server has custody of the funds — up to your approved allowance limit per pull. Approve small allowances and rotate them; revoke on any concern. No DEX today does true scheduled DCA on-chain, so this pattern is the current state of the art for automated DCA-to-XMR — worth understanding before signing the approval. SPA architecture (initial HTML is a loading shell) means automated audit sees no policy text — the meta description is what upstream probes get. Confirm the router and fee model by running a small strategy before committing large XMR flows. The capped-allowance model reduces blast radius if anything goes wrong, but review the allowance amount you approve — a large approval means a large potential draw. Docs page is "coming soon" per the operator's own copy at time of listing.