Issue, transfer & operate

Start with the rights model

Even for the same physical asset, ownership-related rights, access eligibility and revenue rights require different data and constraints. Define how agreements, asset IDs and token IDs relate.

A common implementation flow

Separate preparation and submission

prepareTransfer provides details such as recipient, amount and execution policy for review. submitTransfer requests execution. Successful preparation does not complete a transfer.

1
2
3
4
5
6
7
8

import { createHazbaseWalletClient,
  type PrepareTransferInput } from "@hazbase/kit/wallet";

const wallet = createHazbaseWalletClient();
export async function previewTransfer(input: PrepareTransferInput) {
  const prepared = await wallet.prepareTransfer(input);
  return { display: prepared.display, policy: prepared.policy };
}

Show the details in your UI and submit only after the required authentication and approval. Retain userOpHash and transactionHash, then reconcile status with the on-chain result.

Check units and execution results

Amount units vary by API and Helper. Avoid floating-point arithmetic for smallest units and consult the method types. BigInt cannot be passed directly to JSON; define an explicit storage representation.

Contract state changes, bank payments, physical delivery and contractual rights are separate processes. Provide reconciliation with your business systems.