Sharing another info/announcement from SecureShift's X page:

---

The $1,000 $XMR Swap Game Is LIVE!

Celebrate 3 Years of SecureShift Exchange and win your share of $1,000 in $XMR!

🪙 Swap any crypto (min $50 per swap)
🔥 $XMR pairs count double
🏆 Random & top traders both win
📅 Runs from Nov 7 – Dec 1
📢 Winners announced Dec 3

---

Source: https://x.com/secureshift_io/status/1986810213505380688

---

Disclaimer: I don't manage these giveaway/contests; join at your own risk.

// SECURESHIFT DEX: ENTER THE MATRIX
connecting nodes... routing liquidity...

---

SECURESHIFT DEX IS LIVE
No custody.
No limits.
No permission.

---

>> CROSS-CHAIN SWAPS
BTC ⇄ XMR ⇄ ETH ⇄ SOL
Different chains. One execution layer.

---

>> CONTROL LAYER
• You hold the keys
• You execute the swap
• You own the result

---

>> ACCESS THE DEX
https://secureshift.io/dex

---

>> IMPORTANT NOTE
The DEX is still under active improvement and optimization.
We strongly suggest avoiding large deposits at this stage.
Recommended swap size per order:
• 0.2 BTC → 0.3 BTC
• Up to 1 BTC maximum per swap
Please do NOT deposit large funds until further updates.

---

The system runs.
No one controls it.

---

// WELCOME TO THE DECENTRALIZED MATRIX

Thanks for raising this, fair points, and we want to be clear about how things work.

At the moment, SecureShift operates on a hybrid model. We use decentralized liquidity and protocols for pricing and routing, but the execution layer still relies on temporary routing addresses to complete swaps across multiple sources. That can look custodial, but it’s limited to the swap process only, we don’t hold user funds long-term or have access to private keys. That said, it’s not a fully trust-less DEX yet, and we’re actively working toward fully on-chain, wallet-to-contract execution.

We also run AML checks before any swap is routed. If a transaction is flagged, the swap is stopped and funds are automatically refunded to the original wallet address. This is in place to prevent misuse and keep the platform compliant without adding friction for users.

On transparency -:- you’re right to expect it. If code repositories and audit reports aren’t easily accessible, those claims aren’t verifiable. References to firms like CertiK, Trail of Bits, Halborn, and OpenZeppelin will be backed by clear, public links. We’re currently organizing and publishing these so anyone can review them directly.

In short, what’s live today is a hybrid execution layer using decentralized liquidity, not a fully pure DEX yet. We’re improving both the architecture and how we communicate it.

Web3 wallet-connection will be live in few days.
 
Appreciate the direct feedback, it helps us tighten things up.

Fair point, and honestly, this is exactly the kind of pushback we need.

You’re right on the core argument: if funds pass through addresses we control during execution, that introduces a custodial element. Even if it’s brief and only for routing, it’s still not the same as a pure smart-contract DEX where users keep full control end-to-end.

Here’s where things actually stand, without dressing it up:

What’s live today is a hybrid swap system. We aggregate decentralized liquidity, but execution still uses temporary routing wallets to complete cross-source swaps.
That means it’s not a fully non-custodial DEX yet, and calling it that outright can be misleading. We’ll be correcting how this is presented so it reflects reality more clearly.
At no point do we hold funds beyond the swap process, and we never have access to user private keys, but yes, during execution, funds are briefly in our control. That distinction matters, and we’re not going to blur it.

On AML, your assumption is partly right.
We run checks because:

some liquidity sources and bridges enforce compliance,
and we also want to prevent flagged funds from entering the routing system and causing failures or freezes mid-swap.

If something is flagged, the system stops the swap and automatically refunds to the original wallet. No manual intervention, no holding.

On audits and transparency, we removed those references temporarily because they weren’t properly backed with public links yet. That’s on us. Rather than leave unverifiable claims up, we pulled them down until everything can be published clearly and checked by anyone.

Bottom line:
What’s on the website will be aligned with what’s actually live. No overstatements.

And longer term, the goal is still the same move toward a fully contract-based, trust-minimized execution layer where this custodial step doesn’t exist at all.

If you’ve got more concerns, keep them coming. This kind of scrutiny helps us tighten things up.

SecureShift will be the OFFICIAL MEDIA HUB SPONSOR of the Litecoin Summit in Amsterdam this coming June 22-23, 2026. This will be held in Amsterdam, Netherlands.
Sources:
https://litecoin.com/summit#sponsors
https://x.com/LTCFoundation/status/2042622913002770899

„FULL PRIVACY FEATURE” BTW