How to adopt
Packaging paths
| Packaging path | What you ship | Who brands the UX | Maturity today |
|---|---|---|---|
| Client journey | Users settle in Tenebrae client (tenebrae.xyz) | Tenebrae | Testnet hosts |
| SDK embed | Your product UI, wallet Host shell, or automation + Tenebrae SDK V2 | Your brand · Protocol under the hood | Preliminary interface · testnet hosts |
| Co-brand / white-label | Partner-facing settlement experience on client patterns + Protocol | Partner primary · “Powered by Tenebrae Protocol” | Partner MAP · brand kit · not a self-serve SKU |
| Partner orchestration | Marketplace / payroll orchestration into private settlement | Partner | Roadmap · counsel required |
All paths keep: bring your own wallet · client-side ZK Proofs (Noir) · deposit and withdraw amounts public by design · institution owns upstream KYC / screening. Live hosts: Stack · Settlement Chains.
Decision guide
- Need settlement inside your product UI, wallet Host shell, or automation? → SDK embed — Tenebrae SDK V2 · embed patterns · Integration Sandbox for bounded Host dry-run (not live Host spend proof)
- Users can use the Tenebrae client as-is? → Client journey — Quickstart
- Need partner-primary branding on settlement UX? → Co-brand / white-label (partner MAP) — section below
- Orchestrating payroll or marketplace disbursement rails? → Partner orchestration (roadmap) — use cases
What you can build
With the Tenebrae client or Tenebrae SDK V2 embed path:
- Deposit into Tenebrae — public wallet → Protocol private settlement (deposit amounts public on-chain by design)
- Private transfer — directed settlement inside Protocol; observers see Protocol verification, not plaintext counterparty ERC-20 fields
- Withdraw from Tenebrae — Protocol private settlement → public wallet (amount public by design)
- Compliance-bound submit — Protocol verifies policy predicates at every settlement; your institution still owns upstream KYC / screening
Integration model
- Bring your own wallet — Tenebrae is not a wallet product
- Client-side ZK Proofs (Noir) — proving stays with the operator stack; we do not sell enclave-default remote prove as the trust story
- No payments-L1 migration — settlement on host EVM testnets you already use
Supported flow types
| Flow | Motion | Honesty |
|---|---|---|
| Public → Private | Deposit into Tenebrae | Deposit amount public |
| Private → Private | Private transfer | Directed settlement privacy |
| Private → Public | Withdraw from Tenebrae | Withdraw amount public |
| Batch private payroll (multi-recipient) | Payroll use case | Roadmap — counsel required · not shipped today |
Who this is for
- Payment / payroll / treasury product teams
- Wallet and product embedders via Tenebrae SDK V2 (app embed or Kohaku-class Host shell)
- Partners evaluating co-brand / white-label settlement UX (MAP)
- Custody-adjacent stacks that keep keys in the institution’s wallet
- Individual builders on Sepolia
Client journey
Job: Smoke private settlement on sandbox environments without building UI.
Start here: Quickstart — Sepolia
Goal: run deposit into Tenebrae → private transfer → withdraw from Tenebrae against a peer testnet with a browser wallet.
- Pick a sandbox — Ethereum Sepolia, Base Sepolia, or Tempo Testnet
- Use Tenebrae client — tenebrae.xyz for BYOW smoke
- Connect your wallet — MetaMask or Rabby. On Tempo Testnet, wallet batching is sequential today (wallet limitation on Moderato — not a Tenebrae defect)
- Deposit into Tenebrae
- Private transfer
- Withdraw from Tenebrae
Motions: Deposit · Private transfer · Withdraw.
SDK embed
Job: Embed prepare → prove → submit in your app, wallet Host shell, or automation.
| Page | Contents |
|---|---|
| Tenebrae SDK V2 | Settlement + Confidential DeFi · wallet Host distribution |
| Deposit into Tenebrae · Private transfer · Withdraw from Tenebrae | Operation guides |
| Embed patterns | Prepare / balance / port literacy |
Institutional Activity / ops UX still defaults to Tenebrae client when you need the full product shell.
Private DeFi (Uniswap / Aave-class): in product on sandbox — see Stack · SDK V2 · Confidential DeFi.
Multi-recipient / batch pay: private payroll APIs that pay many recipients in one flow are roadmap — not shipped today. See global payroll partner track (partner channel — contact BD) · Payroll · batch roadmap.
Deploy and manifest details stay in operational guides — this page stays packaging and surface map first.
Co-brand / white-label
Job: Ship a settlement experience that looks like your product, backed by Tenebrae Protocol — without rebuilding custody or claiming you are a wallet.
| We say | We do not say |
|---|---|
| Partner-primary UI · Powered by Tenebrae Protocol | Self-serve white-label download |
| Brand lockups + claims footnote from the partner brand kit | Recolor gold · drop testnet honesty |
| MAP + BD for scope, domains, and SLA | Silent capture of user funds · Tenebrae as WaaS |
| Same BYOW + client-side prove story as client journey / SDK embed | “Tenebrae wallet” · employment / payroll compliance ownership |
What white-label means here
- Brand — Partner mark primary; Tenebrae wordmark / “Powered by Tenebrae Protocol” per partner co-brand
- Surface — Client-pattern settlement UX (private balance, motions, Activity) configured for the partner — not a separate custodial stack
- Settlement — Still Tenebrae Protocol · wallet-signed · policy predicates at submit
Maturity: available as a commercial packaging option under partner MAP. Public docs do not claim a turnkey white-label SKU, custom-domain portal product, or contracted payroll white-label today.
Next step: BD / partner channel · download brand rules from Brand · technical path still SDK V2 + client when scoped.
Partner orchestration (roadmap)
Job: Partner orchestrates funds into private settlement (employer treasury prefund, marketplace receive, batch disbursement) inside their rail — still BYOW for worker / end-user withdraw.
Documented as roadmap in use cases. Do not scope builds as if multi-recipient private payroll APIs ship today.
What every packaging path refuses
| Forbidden implication | Honest line |
|---|---|
| Tenebrae holds keys | BYOW always |
| White-label = WaaS | We are private settlement, not wallet-as-a-service |
| Mainnet live today | Live hosts are listed under Stack · Settlement Chains |
| Fully private payments | Deposit and withdraw amounts public by design |
| Market compliance clearance | Two-layer compliance — predicates ≠ “compliant in {market}” |
Operator smoke checklists
| Network | Checklist |
|---|---|
| Sepolia | Deposit · transfer · withdraw QA |
| Tempo Testnet | Tempo testnet QA |
| Private transfer discovery | Transfer links guide |
For Tenebrae repo contributors
Internal engineering references — not part of the buyer-facing packaging story.
| Topic | Reference |
|---|---|
| Frontend ↔ indexer wiring | Frontend–indexer integration |
| Settlement stack | Settlement subsystem overview |
| Platform use-case catalog | Platform use cases |
| Workflow test harness | Workflow harness framework |
Next
| Role | Go here |
|---|---|
| Sandbox walkthrough | Quickstart |
| Builder embed / Host | Tenebrae SDK V2 |
| Product packaging | Co-brand with BD on this page |
| Use cases | Use cases |