SHILDO Docs / Products

Products

Modular stack for wallets, protocols, and payment apps built on one privacy settlement layer. Each product maps to a protocol layer and can be used independently or together.

Product map

ProductLayerPrimary user
Privacy RouterRoutingProtocols, bridges
Shielded WalletClientEnd users
Settlement HubBase contractsValidators, integrators
Developer SDKAPIApplication developers
Compliance View KeysAuditFinance, legal, regulators

Privacy Router

Routes shielded payments across EVM networks and Solana. The router selects paths based on liquidity, fee, and latency. At each hop metadata is stripped before public mempool exposure.

Capabilities

  • Multi hop path finding with fee estimation
  • Automatic fallback when a relayer is offline
  • Route id encoded in Base public inputs
  • Shielded and plain mode per intent

Shielded Wallet

Confidential send and receive for supported assets. The demo wallet at /access includes:

  • Seed phrase generation and recovery
  • Portfolio with live fiat estimates
  • Send flow with shield toggle
  • Transaction history panel
  • Network explorer with block list
  • Staking and node management UI (simulated)

Settlement Hub

Base anchored finality with unified zk state. Acts as the verification and coordination layer for all routes. See Settlement for finality and gas details.

Developer SDK

JavaScript SDK and REST endpoints for intent creation, proof submission, and delivery status. Typical integration requires fewer than 20 lines for a basic shielded send. See SDK.

Compliance View Keys

Optional view keys let users prove compliance to auditors without publishing transaction details to public explorers. Keys are scoped to individual transfers and can be rotated or revoked by policy.

Use cases

  • Tax reporting for shielded receipts
  • Regulatory examination of specific payroll runs
  • Internal finance reconciliation

Integration patterns

A

Embed wallet

Link to /access or iframe the send panel for quick demos.

B

SDK only

Use @shildo/sdk inside your existing wallet or checkout flow.

C

Protocol level

Call verifier contracts and run your own relayer against Base events.