Use cases

Tenebrae adds confidential settlement between public funding and public withdrawal. It is designed for organisations that need public-chain execution without exposing every internal movement as an easily reconstructed transaction graph.

Current maturity: core settlement flows are available on testnet. Some integration and orchestration models remain preliminary or on the roadmap. See Stack for the current capability matrix.

Use case pages

Treasury operationsReduce exposure of operating payments and counterparties · testnet.Fintech and vault productsConfidential settlement between funding and spend rails · testnet.Directed B2B paymentsPay a known counterparty without plaintext amount · testnet.Post-payroll privacyWorker opt-in after a public stablecoin payout · testnet.Batch private disbursementMulti-recipient confidential pay · roadmap.

Treasury operations

Public-chain treasury activity can expose operating balances, vendor relationships, transaction cadence, and changes in strategy. Tenebrae lets a treasury team move supported assets into private Protocol settlement while retaining its existing wallet and host chain.

A typical flow is:

1. An operating wallet deposits assets into Tenebrae Protocol.
2. The treasury makes private transfers to supported recipients.
3. Recipients withdraw to public wallets when public liquidity or disclosure is required.

Deposits and withdrawals remain public. Tenebrae protects activity inside the Protocol; it does not conceal every source of transaction metadata or provide privacy inside regulated fund-share mechanics.

Best suited to: treasury operations, tokenised-asset operations, finance operations, and digital-asset teams.

Explore treasury use cases

Fintech and vault products

Fintech and vault products often combine public on-ramps, institution-controlled wallets, internal asset movements, and public spend or withdrawal rails. Without a privacy layer, internal rebalancing and counterparty payments can remain visible to anyone monitoring the relevant addresses.

Tenebrae can provide confidential settlement between those public boundaries:

1. The institution or user funds Tenebrae from an existing wallet.
2. Internal transfers take place inside private Protocol state.
3. Assets return to a public wallet or spend rail when required.

Tenebrae does not replace the institution's wallet, ledger, licence, card network, or compliance programme. Embedded SDK integration is preliminary; teams can evaluate the workflow through the Tenebrae testnet client first.

Best suited to: fintech vaults, digital-asset accounts, wealth products, and applications with institution-controlled smart accounts.

Explore vault use cases

Directed B2B payments

Standard token transfers publish the sender, recipient, amount, and timing. This can reveal supplier relationships, commercial activity, and payment schedules.

Tenebrae supports directed transfers inside private Protocol state. The sender continues to use its existing wallet, while the recipient discovers and receives the private asset through the Tenebrae client flow.

Best suited to: vendor payments, contractor payments, trading operations, and bilateral stablecoin settlement.

Explore directed B2B payments

Post-payroll privacy

Stablecoin payroll normally arrives as a public transfer to a worker-controlled wallet. Subsequent wallet activity may expose balances, counterparties, and spending patterns.

With Tenebrae, the worker can opt into private settlement after receiving that public payout:

1. The payroll provider sends funds to the worker's public wallet.
2. The worker chooses to deposit some or all of those funds into Tenebrae.
3. Later transfers take place inside private Protocol state.
4. The worker withdraws to public rails when needed.

The initial payroll payment remains public. Tenebrae does not intercept payroll funds, replace the worker's wallet, or assume the payroll provider's employment, identity, or compliance responsibilities.

Best suited to: payroll platforms exploring an optional privacy feature and workers who receive stablecoin compensation.

Explore post-payroll privacy

Batch private disbursement

Employers, marketplaces, and payroll platforms may ultimately need to pay many recipients without publishing a complete disbursement graph.

This orchestration model is on the roadmap. Multi-recipient private payment APIs and employer-driven batch payroll should not be treated as currently available product capabilities.

The intended direction is:

1. An organisation funds Protocol settlement.
2. A batch operation creates private value for multiple recipients.
3. Each recipient controls and withdraws their own funds.

Explore the batch private disbursement roadmap

Shared boundaries

Every use case follows the same principles:

• Existing wallets remain in control of keys.
• Deposits and withdrawals are public on-chain.
• Private settlement does not eliminate timing, wallet, RPC, or other metadata risks.
• Institutions retain responsibility for KYC, screening, policy design, and regulatory obligations.
• Testnet availability must not be presented as mainnet production readiness.

Next

Treasury operationsStart with the first job page.StackEnvironments · maturity · capability ceiling.QuickstartSepolia deposit → transfer → withdraw.