<aside>

1. Overview & Value Proposition

What is RemiDe in one line?

A managed routing + compliance layer that lets licensed wallets/PSPs/banks move stablecoins across chains/stables with alias addressing (RemiTag) and Travel Rule built-in.

What is RemiDe's core moat (unified defensibility)?

1. Policy-tracked execution layer – We don't stop at checks; we route and execute stablecoin payments (same- or cross-chain) under versioned corridor policies, with pre-flight explainability, kill-switches, and per-payment evidence bundles (incl. optional on-chain hashing)
2. Identity + compliance by default – Alias directory + Travel Rule embedded in the flow; PII stays at endpoints
3. Rail-agnostic routing – Any compliant VASP, chain, and stablecoin; we stitch rails (stables & chains) together
4. Vendor-neutral – Bring your own TR/KYT/custody; no forced stack
5. Speed & corridor agility – Ship new chains/stables/payout partners fast; switch policies without redeploys (config-over-code)
6. Future-proof endpoints – Same alias delivers to wallets today, bank accounts next (SEPA/ACH/instant), under the same compliance envelope
7. Deep observability – Idempotent APIs, per-hop traces (routing, policy decisions, TR handshakes, chain receipts), webhooks, and dry-run simulation

Why not build this in-house?

Cross-chain/stable routing + Travel Rule interop + audit-grade data retention + treasury ops across many chains is a 3–12-month lift per corridor; RemiDe compresses that to a single API and a compliance-ready network.

• Canonical glossary (for this FAQ) </aside>

<aside>

2. Target Market & Timing

What category are we creating?

Stablecoin Clearing Network — the infrastructure layer that combines compliance (Travel Rule, counterparty verification) + routing (chain-agnostic, stablecoin-agnostic) + network effects (permissioned membership). Think: SWIFT for stablecoins, or Chainalysis for payments.

Who are the initial target customers?

Licensed Web2/Fintech wallets, PSPs, exchanges, and banks in LATAM + Africa.

Why now?

Regulation (MiCA, US stablecoin frameworks) and Travel Rule standardization (IVMS-101) make this feasible now.

Which corridors first?

A handful of high-demand corridors in LATAM + Africa. Currently building up relationships.

Detailed corridor strategy

• We remain open to discovery while validating broadly now, then focus post-signal. We are not in pure sales yet — this is validation mode with a wide funnel
• Preference: Dominate a few very expensive corridors first (e.g., USD > CO/AR/MX, EUR/GBP > NGN), where pain is highest and ROI is clear
• Sequence demand/supply: win recipients (banks/PSPs in the Global South) first, then senders (EU/US banks) per corridor; then expand regionally (LATAM or Africa before both)
• Parallel "plugin" leverage: integrate under existing infra multipliers (Palisade.co, Utila.io, Inabit.com, DLT-finance.com, ForDefi.com) to light up many tenants at once (while keeping direct sales pilots in flight) </aside>

3. Team & Advisors

<aside>

Who are the founders?

Our team combines deep expertise in regulated payments, high-scale systems and go-to-market:

• Anton Titov (CEO) - https://www.linkedin.com/in/antotitov/
  • Founded Archway.Finance, a remittance-as-a-service platform
  • Raised €1.5M pre-seed and processed transactions across 30+ regions
• Roman Shprenger (CTO) - https://www.linkedin.com/in/shprengerroman/
  • Built TADS.me from concept to $1M ARR in one year
  • Handling 50M+ events per day

Together, we built compliant payment infrastructure, know how to navigate regulators and partners. We move fast-shipped Remide's PoC in two weeks. We've been able to address and articulate global challenge and thus attract strong advisors onboard.

Who are the advisors?

An intentionally complementary bench across: (1) scaled fintech ops & bank GTM, (2) regulatory policy/sandbox design, and (3) ecosystem distribution/infra (wallets, cross-chain, MPC). In short: Operators + Regulators + Rails.

Advisors Onboarded

• Christian Niedermüller - COO @ KuCoin EU https://www.linkedin.com/in/christian-niedermueller-47080211/
  • Ex-banker (16+ yrs) turned digital-asset operator
  • Co-founded SMAPE Capital and DAIC Capital
  • Former CEO of Blocktrade; board member of Austria's DAAA
  • Helps us shape exchange/bank-grade ops and EU ecosystem access, strengthens fundraising credibility with regulated venues and VCs
• Georg Hauer - Former N26 General Manager (scaled N26 through hyper-growth) https://www.linkedin.com/in/georghauer/
  • Later COO/CFO at HAWK:AI (AML)
  • Sharpens our bank/PSP GTM, compliance-messaging, and enterprise sales motion from someone who's shipped at scale on both the bank and AML sides
• Matthias Bauer-Langgartner - Chief of Policy @ Chainalysis https://www.linkedin.com/in/matthias-bauer-langgartner-a14383123/
  • MD UK & Ireland at Bitpanda
  • Previously a Technical Specialist in the FCA's Innovate unit where he helped build the original regulatory sandbox and led crypto/DLT testing
  • Will guide our MiCA/Travel-Rule posture and regulator-facing pilot design to reduce approval risk
• Arne Brutschy, PhD - CTO & Co-Founder @ Archway.Finance https://www.linkedin.com/in/arnebrutschy/overlay/about-this-profile/
  • PhD in AI/Swarm Robotics from Université libre de Bruxelles; published researcher in distributed systems and multi-agent coordination
  • Former CTO at RISE Financial Technologies: built DLT systems for post-trade processes (settlement, asset issuance) with focus on scalability, data integrity, and privacy
  • Architect of secure blockchain services handling historically significant Bitcoin addresses
  • Advises on RemiDe's technical architecture, bringing rare combination of academic rigor in distributed AI and hands-on blockchain infrastructure experience
• Ashley Shen - Head of Treasury @ Kraken & KuCoin [LinkedIn]
  • 10+ years supporting global crypto exchanges in liquidity and financial operations
  • Led end-to-end treasury infrastructure: TMS implementation, fiat/digital asset reconciliation, funding ops, internal banking, safeguarding frameworks
  • Works cross-functionally with product, risk, engineering, and finance to solve operational challenges at scale
  • Advises RemiDe on building robust liquidity infrastructure and improving information flow for high-volume environments </aside>

<aside>

4. Architecture & Technology

Are you centralized or decentralized?

Pragmatically centralized by design (audited controls, guaranteed SLAs). Not a DEX/bridge. There is no plan to decentralize network control.

Do you use smart contracts in the payment path?

Not required in v1. Settlement is push-to-address with wallet management and intent tracking; rebalancing happens off the critical path.

What MPC/security stack do you use?

Our settlement execution is designed to work with an MPC custody provider. Current reference implementation uses dfns (MPC).

Detailed MPC & Controls

• Multisig & signing policy:
  • Default 2-of-3 quorum
  • High-value payouts use 3-of-5 (adds RemiDe Security + Executive approver)
  • For payments ≤ $50k, if the counterparty is allow-listed and all pre-flight checks pass (Travel Rule ACKs, KYT/sanctions, velocity, and treasury limits), our policy engine auto-releases the payout under a 2-of-3 MPC quorum—the automated HSM share and the independent custodian co-signer
  • If any rule isn't green or it's a first-time beneficiary, it auto-escalates to a human instead of sending
• Operational controls:
  • High-level sanction countries limitations, address allow-lists
  • TBD: velocity limits, multi-role approvals, and a documented break-glass emergency procedure
• Per-client controls:

How do you ensure segregation?

Per-partner routing/payout accounts per chain/corridor; no commingling. Dedicated deposit/payout addresses per partner per chain.

</aside>

<aside>

</aside>

<aside>

</aside>

<aside>

</aside>

<aside>

</aside>

<aside>

</aside>

<aside>

</aside>