Protocol record · production

Fluidkey

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

93readiness / 100

integration: mediumethereumarbitrum-onebasepolygonoptimismbsc

Also available as JSON · Markdown

Resources

docsdocs.fluidkey.com sdkgithub.com templatedocs.fluidkey.com supportt.me

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

Readiness score

93/100

Readiness measures how much verified integration surface exists for builders and agents. It does not mean the protocol is easy to use — integration difficulty is tracked separately.

Docs10/10

Docs URL present

SDK8/8

SDK URL present

Template6/6

Template/quickstart present

Support6/6

Support channel present

Capability depth13/20

Stealth-address receiving UX: production_surface; Open-source stealth account kit: integration_workflow

Production-ready15/15

Has a production-ready capability

Confidence5/5

Protocol provenance confidence is high

Chain coverage10/10

5 chain(s) (capped at 5)

Freshness10/10

Last verified 6 day(s) ago

No critical issues10/10

No open critical issues

No hard caps applied.

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.

public payment names with private receiving addresses

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.

Provenance

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). Score computed by score.v2.