# Fluidkey

> Self-custodial privacy dApp for receiving, managing, and spending onchain funds through stealth-address smart accounts and a unified wallet interface.

- Readiness score: **93/100** (score.v2)
- Integration difficulty: medium
- Chains: ethereum, arbitrum-one, base, polygon, optimism, bsc
- Categories: privacy, wallets, stealth-addresses, payments
- Last verified: 2026-06-04 by composewith.eth research (Fluidkey website, docs, FAQ, technical walkthrough, and GitHub live-verified via WebFetch 2026-06-04) (confidence: high)

## Resources

- docs: https://docs.fluidkey.com/
- sdk: https://github.com/fluidkey/fluidkey-stealth-account-kit
- template: https://docs.fluidkey.com/technical-documentation/technical-walkthrough
- support: https://t.me/fluidkey

## Good for

- privacy-preserving receiving addresses for payments, payroll, invoices, funding, and donations
- builders who want users to receive funds without reusing one public address
- self-custodial wallet UX built on stealth Safe smart accounts

## Avoid for

- apps that need full transaction untraceability by default; Fluidkey's baseline stealth addresses provide unlinkability, not traceability breaking
- multisig-connected accounts, which Fluidkey docs say are not supported yet

## Capabilities

### Stealth-address receiving UX (production-ready)
Best for: letting users receive payments through fresh addresses without manually juggling wallets, privacy-preserving payment links and Fluidkey ENS identifiers
- Baseline stealth addresses improve unlinkability but do not erase transaction history or all counterparty linkage.

### Open-source stealth account kit (production-ready)
Best for: recovering or independently generating stealth Safe accounts, builders studying Fluidkey's stealth-account architecture
- Key-generation and private-key functions must only run client-side.

## Composes with

- **ens** (wallet_and_identity; supports) — ENS can expose human-readable names while Fluidkey rotates stealth receiving addresses behind the payment UX.
- **safe** (operational_controls; supports) — Fluidkey uses Safe smart account patterns for stealth account receiving flows.
- **helios** (privacy_layer; supports) — Helios can reduce reliance on trusted RPC reads for wallets that expose stealth-address receiving flows.

## Known issues

- **Fluidkey stealth addresses provide unlinkability, not full untraceability by default** (medium, confirmed) — workaround: Use Fluidkey for privacy-preserving receiving and account management. If the product needs to break the link to prior funds, evaluate Fluidkey's Hide Trail flow or a separate private transfer design with explicit compliance and fee handling.
  - source: https://docs.fluidkey.com/readme/frequently-asked-questions (retrieved 2026-06-04, high)
  - source: https://docs.fluidkey.com/readme/frequently-asked-questions (retrieved 2026-06-04, high)

---
Canonical: https://composewith.eth/protocols/fluidkey · JSON: https://composewith.eth/protocols/fluidkey.json