State methods

Use these methods when connecting your application’s account data and storage to the SDK. For the setup sequence, start with Frontend integration or Backend integration.

Assets and balances

Method	Purpose
`upsertAssets(assets)`	Add or update the configured asset catalog, including token and pool contracts
`getAssets()`	Read the local asset catalog
`getPrivateBalance({ owner, asset })`	Calculate a private balance from records held in SDK state
`getPrivateAssetRows(owner)`	Read private asset balances for an account
`upsertPrivateRecords(records)`	Add restored or received private records to SDK state

A local balance reflects the records loaded into the SDK. Read private records with @arcanetech/privacy-sdk-data-layer, then check each incoming note before treating the balance as complete. Asset metadata comes from your integration’s catalog; it is not inferred from a symbol such as USDC.

Pool and recipient lookups

Method	Purpose
`syncPoolMerkleState({ poolContractId, walletPublicKey })`	Fetch and merge pool state through the configured network connection
`checkRegistrationStatus({ address, walletPublicKey })`	Look up a recipient’s registration and cache the result
`setPoolMerkleState(state)`	Write a pool snapshot supplied by an external sync integration
`saveRegistryLookup(lookup)`	Write a registry result supplied by an external integration

Prefer the network lookup methods for a standard integration. The write methods accept data; they do not fetch or independently establish its freshness.

Private addresses

Method	Purpose
`saveWalletPrivateAddressRecord(record)`	Store the account’s private address and nonce
`saveWalletPrivateAddressScalar(scalar)`	Store the private scalar associated with that account and nonce
`setWalletDefaultPrivateAddressNonce({ owner, nonce })`	Select the saved private address used by spend preparation

These methods store values produced by the wallet’s private-address setup. They do not generate the values. Keep private scalars out of source code, logs, and shared configuration.

Check an incoming note

Decrypt the note in your application, then call assessIncomingNote before upsertPrivateRecords. Add the record only when the verdict is spendable.

const verdict = await client.assessIncomingNote({
  note: {
    value: decrypted.value,
    nullifier: decrypted.nullifier,
    secret: decrypted.secret,
    commitment: decrypted.commitment,
    asset_hi: decrypted.asset_hi,
    asset_lo: decrypted.asset_lo,
  },
  commitmentHex: deliveredCommitmentHex,
  privKeyScalarHex,
  walletPublicKey,
});

if (verdict.kind === 'spendable') {
  await client.upsertPrivateRecords([record]);
}

Verdict	Meaning
`{ kind: 'spendable' }`	The commitment matches, the leaf is in the pool, and the nullifier is unspent.
`{ kind: 'pending' }`	The commitment matches, and the leaf is not in the pool yet. Keep the note and assess it again after you sync pool state.
`{ kind: 'dead', reason: 'commitment_mismatch' }`	The decrypted fields do not match the delivered commitment. Do not store the note.
`{ kind: 'dead', reason: 'nullifier_consumed' }`	The note is already spent. Do not store the note.

Pass poolContractId when the note belongs to a pool other than the pool on the client. Set note.application_id when that note was opened for an application other than the one configured on the client.

Updates after a transaction

Execution writes operation results into SDK state. See Transaction lifecycle for the storage stage. Preserving those changes across reloads remains part of your application’s storage integration.

Environment configuration

Use Set up the SDK for application IDs, audit keys, network contracts, and service configuration. An environment’s pool, registry, application, and services must be compatible; do not mix frontend and backend demo values.

Isolated examples

Some operation guides include a Seed state block with fixture addresses and records. Those blocks illustrate method inputs; replace them with account setup, network lookups, and restored records for a live integration.

Introduction

Compliance Platform

Privacy Layer

Custom KYT providers

Support

Assets and balances

Pool and recipient lookups

Private addresses

Check an incoming note

Updates after a transaction

Environment configuration

Isolated examples

​Assets and balances

​Pool and recipient lookups

​Private addresses

​Check an incoming note

​Updates after a transaction

​Environment configuration

​Isolated examples

Assets and balances

Pool and recipient lookups

Private addresses

Check an incoming note

Updates after a transaction

Environment configuration

Isolated examples