Use Cases
Orbinum enables privacy-preserving operations for institutions and individuals who require confidentiality without sacrificing compliance capabilities.
Table of Contents
Institutional Finance
Private Treasury Management
Organizations can manage treasury operations without exposing holdings:
Benefits:
- Hide treasury size from competitors
- Prevent front-running on large transactions
- Maintain audit trail via view keys
Confidential Payroll
Process salary payments without revealing individual compensation:
| Traditional | With Orbinum |
|---|---|
| All salaries visible on-chain | Only total payroll amount visible |
| Employee addresses linked to amounts | Employees receive via private notes |
| Easy to analyze compensation structure | Privacy preserved, audit possible |
Enterprise Operations
B2B Settlements
Execute inter-company payments without revealing business relationships:
- Shield incoming payments from customers
- Transfer internally between departments
- Unshield for vendor payments
- Full audit trail available to authorized parties
Supply Chain Privacy
Track goods through supply chain while protecting commercial relationships:
- Suppliers shield product commitments
- Transfers between intermediaries remain private
- End recipient verifies provenance via ZK proof
Individual Privacy
Personal Asset Management
Individuals can manage digital assets with bank-grade privacy:
- Shield tokens to hide balance from public view
- Transfer between personal accounts privately
- Unshield only when needed for public transactions
Compliance-Ready Privacy
Unlike fully anonymous systems, Orbinum supports regulatory compliance:
User generates View Key → Shares with auditor → Auditor verifies transactions
→ User privacy preserved from public
Technical Integration
EVM Compatibility
Solidity contracts and EVM wallets can deposit into the shielded pool through its precompile:
// Precompiled contract at 0x0000000000000000000000000000000000000801
interface IShieldedPool {
/// @dev Payable — the deposited amount travels in msg.value, not in an argument.
function shield(
uint32 assetId,
bytes32 commitment,
bytes calldata encryptedMemo,
bytes calldata proof,
uint32 circuitVersion
) external payable;
}
shield is the only function it exposes. Transfers and withdrawals are submitted unsigned through
Substrate, so no EVM transaction links an address to them — see the
precompile reference.
Building a payment flow
Your dapp reads the chain and composes the payment; an Orbinum wallet holds the keys and performs the spend. You never handle a spending key.
import {
OrbinumClient,
sealPaymentSlip,
encodePaymentSlip,
} from '@orbinum/protocol';
const client = await OrbinumClient.connect({
substrateWs: 'wss://rpc.testnet.orbinum.io',
});
// Seal a slip toward the recipient's viewing public key, then hand it to a wallet.
const envelope = sealPaymentSlip(recipientIvkPacked, {
commitmentHex,
encryptedMemo,
});
const wire = encodePaymentSlip(envelope); // 'orbslip1:…'
See Building on Orbinum for the public client, payment slips, and address helpers, and the custody boundary for what stays in the wallet.
Implementation Examples
| Use Case | Shield | Transfer | Unshield | View Key |
|---|---|---|---|---|
| Treasury | Yes | Yes | Yes | CFO, Auditor |
| Payroll | Yes | Yes | Yes | HR, Employee |
| B2B | Yes | Optional | Yes | Legal, Finance |
| Personal | Yes | Yes | Yes | User only |
Learn More
📄️ Vision
Orbinum's mission to deliver privacy-preserving infrastructure for institutional blockchain applications.
📄️ Use Cases
Practical applications of Orbinum's privacy-preserving infrastructure.