Documentation Index
Fetch the complete documentation index at: https://docs.privacyboost.io/llms.txt
Use this file to discover all available pages before exploring further.
Configuration
Once you have an App ID, initialize the SDK with a configuration object specifying your endpoints and target chain.Required Parameters
| Parameter | Type | Description |
|---|---|---|
serverUrl | string | URL of the Privacy Boost server |
appId | string | Your application identifier (see App Setup) |
Optional Parameters
| Parameter | Type | Description |
|---|---|---|
chainId | number | EVM chain ID for the target network (auto-discovered from server) |
shieldContractAddress | string | Address of the deployed Shield contract (auto-discovered from server) |
wethContractAddress | string | WETH contract address (required for native ETH deposits) |
rpcUrl | string | JSON-RPC URL for on-chain reads (token registry lookups) |
logLevel | string | Console log verbosity: "silent" (default), "error", "warn", "info", "debug" |
Example
Supported Networks
| Network | Chain ID | Description |
|---|---|---|
| OP Sepolia | 11155420 | Optimism Sepolia testnet (recommended for development) |
CLI Environment Variables
The CLI reads configuration from environment variables:| Variable | Description |
|---|---|
PRIVACY_BOOST_APP_ID or APP_ID | Application identifier |
SERVER_URL | Privacy Boost server URL |
SHIELD_CONTRACT_ADDRESS | Shield contract address (auto-discovered if omitted) |
WETH_CONTRACT_ADDRESS | WETH contract address |
RPC_URL | JSON-RPC URL |
Logging
By default, the SDK produces no console output (silent). Set logLevel to control verbosity during development or debugging:
| Level | Output |
|---|---|
"silent" | No output (default) |
"error" | Errors only |
"warn" | Errors and warnings |
"info" | Errors, warnings, and informational messages |
"debug" | All messages including verbose debug output |
Use
"debug" during development to trace SDK operations. In production, leave it as "silent" (the default) or "error" to avoid leaking internal state to the browser console.[Vault], [Auth]) for easy filtering in browser dev tools.
Multi-Chain Configuration
To operate on additional chains beyond your primary one, create chain clients withsdk.forChain(). Only serverUrl is required — all other parameters are auto-discovered:
| Parameter | Type | Required | Description |
|---|---|---|---|
serverUrl | string | Yes | URL of this chain’s server |
chainId | number | No | EVM chain ID (auto-discovered) |
shieldContractAddress | string | No | Shield contract address (auto-discovered) |
wethContractAddress | string | No | WETH contract address |
rpcUrl | string | No | RPC URL for on-chain reads |
tokenRegistryAddress | string | No | Token registry contract (auto-discovered) |
teePublicKey | string | No | TEE public key (auto-discovered) |
Next Steps
Authentication
Connect a wallet and log in
Key Management
Key derivation, persistence, and recovery
Multi-Chain
Operate across multiple blockchains