Skip to main content

Wallet Management

As part of onboarding with CRYMBO Oracle, each Bussiness/ institution must register and manage two types of wallets:

  1. Master Wallet — the authoritative, KYB-bound identity
  2. Operational Wallets — whitelisted addresses used for executing on-chain requests

This section details how to configure and manage these identities securely.

Master Wallet​

The master wallet is the cryptographic identity that:

  • Represents the Bussiness/ institution on-chain
  • Is tied to the Bussiness/ institution's KYB record
  • Has permission to approve or revoke operational wallets

Registration​

The master wallet must be:

  • A secure EOA (Externally Owned Account)
  • Generated and held under the Bussiness/ institution sole control
  • Submitted during onboarding through CRYMBO Connect

Once verified, CRYMBO will bind the master wallet to the Bussiness/ institution ID in the Oracle system.

Operational Wallets​

Operational wallets are used to:

  • Initiate identity data requests
  • Interact with the OracleCoordinator smart contract

Whitelisting Methods​

You can whitelist an operational wallet via:

1. On-Chain Transaction​

From the master wallet, call:

function whitelistWallet(address operationalWallet)

2. CRYMBO Connect Portal​

  • Navigate to Wallet Management
  • Add new wallet address
  • Submit for approval

Security Considerations​

  • Each operational wallet must be signed by the master wallet before activation
  • Whitelisted wallets can be removed at any time by the Bussiness/ institution
  • Wallets should follow industry best practices for key management (e.g. hardware wallets, MPC wallet, custody...)

Viewing Wallet Status​

You can retrieve your wallet configuration using the CRYMBO API:

GET /api/wallets
Authorization: Bearer <token>

Example Response:

{
	"master": "0xMasterWallet...",
	"operational": ["0xOp1...", "0xOp2..."]
}