Portal Community
BizFirstAI Portal / Nodes / Coinbase / Examples: Server Wallet

Examples: Server Wallet

Worked custodial-wallet workflow patterns

Create a testnet wallet, fund it, and check the balance

  1. account / getOrCreate with accountName: "demo-wallet" — creates the EVM account if it doesn't exist yet, and returns its address.
  2. account / requestFaucet with that address and token: "eth" (network defaults to base-sepolia, testnet). Requires walletSecretCredentialId.
  3. account / listBalances with the same address and network: "base-sepolia" (override the mainnet default) to confirm the faucet funds arrived.

Send funds out of a managed wallet

  1. transfer / sendNative with accountName, toAddress, and amount. Requires walletSecretCredentialId.
  2. The idempotency key is generated once for this step and reused automatically on retry — safe to let the platform's transport retry a transient failure here, unlike swap/execute.
  3. Inspect the returned transactionHash to track on-chain confirmation externally.

Quote before you swap

  1. swap / quote with fromToken, toToken, fromAmount — no wallet secret needed for this read-only step.
  2. A condition node checks liquidityAvailable === true before proceeding — false is a normal response, not an error.
  3. If liquidity is available, swap / execute with the same accountName/tokens/amount. Because this operation has no confirmed idempotency mechanism, treat a timeout as an unknown outcome — check balance / listTokens for the account before deciding whether to re-run the swap.

Enforce a spend policy on a smart account

  1. account / getOrCreate to get an owner EVM address.
  2. smartAccount / getOrCreate with that ownerAddress and an accountName.
  3. policy / create with a policyJson document describing the allowed spend rules. Requires walletSecretCredentialId.
  4. policy / list or policy / get later to audit which policies are active — these two reads don't need the Wallet Secret.

Solana side-by-side

solanaAccount / getOrCreate and solanaAccount / requestFaucet mirror the EVM account lifecycle above one-for-one — same config shape, same fail-closed Wallet Secret requirement on the faucet call.