Intent-based cross-chain swaps with Stellar as the settlement layer.

Users express a swap intent — "I want to receive USDC on Stellar, and I'm willing to send 0.14 WETH from Base" — and a competing solver network races to fill it. No bridges. No wrapped tokens. Settlement is guaranteed by on-chain solver bonds.

Project status: ~30% complete. Core settlement contract, intent relay API, and swap/solver UI are functional against mock data and Stellar testnet primitives. The solver registry contract, on-chain proof verification, and live wallet/contract wiring are in progress. See the per-repo roadmaps and open issues for contribution opportunities.

Each repository is independently buildable and deployable. Setup instructions live in each repo's README.

Getting tokens onto Stellar from Ethereum / Base / Polygon today requires:

1. Finding a bridge that supports your source token
2. Waiting for bridge finality (often 15–30 min)
3. Dealing with wrapped assets that carry bridge-specific trust assumptions
4. Paying multiple fees across multiple protocols

Vortex replaces this with a single UX primitive: the swap intent.

User                    Vortex                   Solver                   Stellar
 │                         │                        │                        │
 │─── submit_intent() ────►│                        │                        │
 │    (src: 0.14 WETH      │                        │                        │
 │     dst: min 480 USDC)  │◄── quote / accept ────►│                        │
 │                         │                        │                        │
 │                         │                        │── fill_intent() ──────►│
 │                         │                        │   (sends 485 USDC      │
 │◄── 485 USDC received ───│◄───────────────────────│    to user on Stellar) │
 │                         │                        │                        │

Intent lifecycle:

Vortex's security relies on two primitives:

1. Solver bonds — solvers must lock USDC to participate. Failed fills slash 10% of their bond, making repeated failures unprofitable.
2. Fill-window enforcement — once a solver accepts, the intent is locked for 5 minutes. If they fail to fill, the intent reverts to open and is re-auctioned, and the bond is slashed permissionlessly via slash_solver().

In production, on-chain proof verification (via cross-chain messaging or oracle attestation) will remove the remaining trust assumption on the solver's honest reporting.

To report a vulnerability, see SECURITY.md.

Vortex is open source and contributions are welcome — this is part of why the project participates in the Drips ecosystem for sustainable open-source funding. Please read CONTRIBUTING.md and our Code of Conduct before opening a pull request.

MIT © 2026 Vortex Protocol Contributors