xmr.club
EN 中文 ES RU
★ availableBecome the front-page sponsor— 1.5 XMR/mo · 1 slot site-wide · banner on home, every category, every provider
/exchanges · verified 2026-06-18

Shroud Finance

HELD

Pre-launch privacy cross-chain bridge from operator @xmrtodd (X handle, also `uzmanalexander` on GitHub) under the brand @shroudfinance. The protocol design is documented (THORChain + Near Intents + Aztec ZK, N-of-M agent consensus) but deployment and community track-record do not yet exist. Held until the gap between operator claims and shipped surface narrows materially.

At a glance

KYC posture
anonymous signup
Last verified
2026-06-18

Review

This listing is currently held — present for direct-URL reference, not graded, not shown in default search.

What it is. A privacy cross-chain bridge UI at `shroud.finance` plus a protocol specification published as `ShroudChain` on GitHub. Routes intended through THORChain, Near Intents, and Aztec ZK. Non-custodial design, no-KYC, no-geoblocking claims. Live swap widget accepts XMR/ETH/SOL/USDC/USDT/BNB/BASE/ARB/TRX/XRP/BTC pairs at the UI level.

Why we're holding rather than grading.

  • The "chain" was created the same day we received the sponsor inquiry. `github.com/uzmanalexander1-dot/shroudchain` was created 2026-06-18 02:23 UTC, 65 KB, 0 stars/forks/issues. The architecture document and Solidity scaffold are well-written and the design is coherent, but there is no deployment history to evaluate.
  • "Battle-tested, open-source infrastructure" is contradicted by the repo age. The homepage claim and the freshly-initialized repository do not reconcile in any honest framing.
  • The published manifesto isn't actually published. The homepage's comparison table — positioning Shroud against centralized exchanges and a named competitor — is wrapped in `<div class="comp-section" style="display:none">` and never renders to visitors. The strongest operator claims live in HTML that nobody sees.
  • Operator identity threads do not yet reconcile cleanly in public. The homepage and Telegram both publish under `@shroudfinance`, the submitter email is `uzmanalexander@gmail.com`, the GitHub username is `uzmanalexander1-dot`, the GitHub profile name is "xmrtodd", and the linked X handle from GitHub is `@xmrtodd` ("gdj") — none of these are wrong individually, but no single page surfaces the connection so a visitor can confirm they are looking at one operator.
  • Zero independent footprint. No discussion on r/Monero, r/privacy, monero.town, getmonero.org/community. The operator's own promotional tweet from `@xmrtodd` linking to `@shroudfinance` registered 11 views.
  • No Tor mirror, no policy pages, no published team or jurisdiction, no proof-of-liquidity, no incident history.

This is not a scam tag. The architecture spec is real, the swap UI does load, and the operator is publicly attached to the project. The gap is between operator claims and shipped surface — the directory cannot honestly grade a project whose evidence base is mostly documentation that runs ahead of its deployment.

Re-evaluate when all of the following hold:

1. The `shroudchain` repository has at least three months of public commit history with non-trivial contributions and an external contributor or two. 2. Settlement contracts are deployed at named addresses on at least one source chain (EVM or Solana) with traceable on-chain activity. 3. The comparison-table manifesto is actually visible on the public homepage (not `display:none`). 4. Operator identity is reconciled on a single public page — e.g. an `/about/` that connects `@xmrtodd` to `@shroudfinance` openly, or a published team page. 5. At least one independent peer directory (kycnot, monerica, web3privacy, monero.fail, privacyguides) carries a curated review, not just a search-name match.

Until then the listing stays held. Sponsorship discussions resume after a regular grade is on the page.

Live ops data

kyc.rip hasn't routed swaps through Shroud Finance yet, so we have no first-party settlement data (typical XMR settlement, slow-tail, confirmations) for it.

Operator? Request integration: @kyc_rip_bot

Integration status does not affect this provider’s grade or review.

Links

Sourced from operator pages — verify identity via more than one channel before trusting time-sensitive instructions.

Audit trail — receipts for the editorial claim

  • UPSTREAM No probe yet — daily cron at 06:00 UTC
  • ONION No .onion mirror listed
  • MANUAL Last manual verification 2026-06-18 (<30d)

Reviews — moderated · rules

No community reviews yet. Be the first below.

Add a review

Honest, brand-neutral feedback welcome. A curator approves before it appears here. No JS required.

Required: review body. Honest, descriptive reviews get approved within a day. Marketing copy, slurs, or invective get rejected. Per-day cap of 5 submissions per IP.