Skip to main content

FAQ

Product

Is Tenebrae a wallet?

No. Tenebrae is bring-your-own-wallet. Your existing wallet (MetaMask, Rabby, institutional signer) signs transactions. The Tenebrae client shows private balance and runs settlement — it does not custody your keys.

What is Tenebrae Protocol?

Tenebrae Protocol is on-chain private settlement on public EVM chains — deposit, private transfer, and withdraw through a Gateway contract. Confidentiality comes from client-side ZK Proofs (Noir), not from moving assets to a private L2.

Is everything private on-chain?

No. Deposit and withdraw amounts are public on-chain. Private settlement applies to the motion between those steps. We disclose this on every product page — do not assume “fully private payments.”

Is Tenebrae mainnet-ready?

Not yet. Live product hosts are listed under Stack · Settlement Chains. See Stack.

Is Tenebrae a dark pool?

No. Tenebrae is privacy-pool-class confidential settlement on public host chains — deposit, private transfer, withdraw — with client-side ZK Proofs (Noir). We do not operate a dark-pool trading venue. Category place: privacy layer on host chains you already use — see Overview · Use cases.

Are you compliant in the United States (or any named market)?

We do not claim market clearance. Diligence language is the two-layer model: institution upstream controls plus policy predicates verified in Protocol settlement proofs. That is not “compliant in {market}.” See compliance two-layer and claims-register.

Do you offer private Uniswap or Aave today?

Not as branded Uniswap or Aave products. Confidential DeFi on sandbox hosts runs private venue-class flows (swap · supply · borrow) through Tenebrae Protocol — who you are stays private; token · amount · market stay public at the venue. Venue enablement is per host. Not mainnet production. See Stack · Confidential DeFi.


Privacy & compliance

How does confidentiality work?

Client-side ZK Proofs (Noir) prove valid settlement without revealing private state on-chain. Transfer links handle recipient discovery (ECDH + asset index). Detail: privacy model.

Is Tenebrae “compliant by design”?

No unqualified claim. We describe a two-layer compliance model: your institution’s upstream controls plus Protocol-level policy predicates at submit. That is an architecture description — not regulator verification. Detail: compliance two-layer.

How is this different from other privacy-pool-class systems?

Tenebrae settles on host chains you already use — no mandatory migration to a private L2. Architecture differs on hub trees, compliance proof shape, and client-side proving. We do not publish competitor comparison tables on the public site; partner materials cover lane-specific positioning.


Integrators

How do I try it?

25-minute Sepolia smoke: integrator quickstart — deposit → transfer → withdraw at tenebrae.xyz.

Is there an API like multi-recipient private send?

Not as shipped product docs. Tier 2–3 batch private disbursement is roadmap. Do not build against competitor multi-payee API shapes as if Tenebrae ships them today. See use cases for roadmap cards.

Can I embed Tenebrae in my wallet or product?

Yes — three public packaging shapes:

  1. SDK embed — your UI + Tenebrae SDK V2 (SDK V2 · embed patterns)
  2. Tenebrae client — institutional UX at tenebrae.xyz without building UI
  3. Co-brand / white-label — partner-primary settlement UX · “Powered by Tenebrae Protocol” under partner MAP (not a self-serve SKU) — How to adopt

Do you offer white-label?

As a commercial packaging option under partner MAP — yes. Partner-primary UI, brand kit lockups, Protocol under the hood, BYOW preserved. Not a downloadable white-label portal product and not wallet-as-a-service. See How to adopt · co-brand / white-label · Brand.


Host chains

Which chains are supported?

Live Protocol hosts today:

  • Ethereum Sepolia
  • Base Sepolia
  • Tempo Testnet (compose peer — not “our L1”)

See Stack · Settlement Chains · settlement hub.

Why is Tempo signing sequential?

Tempo BYOW often requires sequential wallet signatures today (MetaMask EIP-5792 disabled on Moderato). This is a host constraint — not a Tenebrae product bug. Use Sepolia for the smoothest tutorial path.


Still have questions?

AudienceNext step
Product / treasuryUse cases
EngineerHow to adopt
DiligenceAssurance summary