consistently. Capability-based access (transfer caps, kiosk caps) to let users prove ownership without exposing raw objects. Custom transaction builders in SDKs so wallets can construct the right Move calls while abstracting complexity. Metadata standards (token/NFT metadata, display standards) so wallets can render assets correctly. Event hooks & subscriptions so wallets can update UI based on on-chain

You usually integrate custom smart contracts with Sui wallets by letting the wallet handle keys and signatures while your dApp manages the contract logic. The main pattern is to expose your Move module’s entry functions, then connect to them through the Sui SDK or wallet adapter. You build a TransactionBlock, add the smart contract call, and pass it to the wallet for signing and execution. This keeps signing secure while letting you focus on contract behavior. For example:

import { TransactionBlock } from '@mysten/sui.js/transactions';

async function runCustomContract(wallet) {
  const txb = new TransactionBlock();
  txb.moveCall({
    target: "0x2::my_module::custom_action",
    arguments: [txb.pure("sample data"), txb.pure(42)],
  });

  const result = await wallet.signAndExecuteTransactionBlock({
    transactionBlock: txb,
  });

  return result;
}