BEAM·v0.1.1·MACOS · LINUX·SHA-256 VERIFIED
DOCS/Commands/send

send

Submit an arbitrary contract write. Same signature syntax as `call`, plus `--value` for payable methods.

Usage

$ beam send [--value <amount>] <contract> <function-sig> [args...]

Submits a transaction that executes <function-sig> against <contract>. The signature syntax matches beam call — same ABI form, same arg parsing.

Examples

$ beam send 0xContract "approve(address,uint256)" 0xSpender 1000000

$ beam send --value 0.01 0xContract "deposit()"

$ beam send 0xContract "claim(uint256,bytes32[])" 42 \
  '[0xabc...,0xdef...]'

Flags

  • --value <amount> — attach native gas token to a payable method. Amounts are in display units (e.g. 0.01 ETH).
  • --from <wallet|address|ens> — choose the sender. Must resolve to a wallet in the local keystore.
  • --chain <name|id> — override the selected chain.
  • --rpc <url> — override the RPC for this transaction.

Confirmation

Write commands wait indefinitely for a mined receipt by default. The terminal loader updates with the transaction hash and pending/mined status. Press Ctrl-C to stop waiting without losing the hash — Beam prints the submitted hash (and any known block number) so you can keep tracking it with beam txn.

If the active RPC stops reporting the submitted transaction for ~60 seconds, Beam returns a dropped state so you can re-broadcast or retry.

◂ Previouscall