Skip to main content
0xio lets you send native OCT, OAT tokens, and private stealth transfers, covering both public and confidential transactions. To send a token instead of OCT, pick it from the token selector on the Send screen; the steps below otherwise apply to both.

​
Standard Public Send

Send a transparent transaction visible on the blockchain.
1

Open Send Tab

Click “Send” in the main navigation
2

Enter Recipient

Enter the recipient’s Octra address (starts with oct)
  • 47 characters (oct + 44 Base58)
  • Validates automatically
  • Can paste or scan QR code
3

Enter Amount

Specify the amount to send
  • Enter in OCT units
  • Shows fiat equivalent (if available)
  • Displays available balance
4

Select Source

Choose “Public Balance” as the source
5

Review Transaction

Review the transaction details:
  • Recipient address
  • Amount to send
  • Network fee (see below)
  • Total including fees
6

Confirm and Sign

Click “Send” and enter your password to sign

​
Transaction Details

  • Speed: Typically a few seconds, subject to network conditions
  • Privacy: Transaction is visible on the blockchain
  • Network fee: Quoted live from the node via octra_recommendedFee and shown before you confirm
Fees are denominated in operational units (ou) and displayed converted to OCT (1 OCT = 1,000,000 ou). The wallet fetches a Standard / High / Fast estimate from the node; you can override it with a custom ou value. There is no fixed fee tier; the node sets the recommended amount.

​
Private Send

Send a stealth transfer where the amount stays confidential. The wallet derives a one-time stealth address for the recipient via ECDH (x25519), encrypts the amount with PVAC-HFHE, and attaches a zero-knowledge range proof, all generated locally on your device.
1

Open Send Tab

Navigate to Send in the main menu
2

Enter Recipient

Input the recipient’s Octra address
3

Enter Amount

Specify the amount to send
4

Select Private Balance

Choose “Private Balance” as the source
5

Review Encrypted Details

Review transaction information:
  • Recipient (visible)
  • Amount (will be encrypted)
  • Network fee (higher than a plain transfer because of proof generation)
6

Confirm

Confirm and sign the transaction

​
How Private Transfers Work

  1. Local Proof Generation: Your device encrypts the amount (PVAC-HFHE) and builds a range proof. A full-screen progress overlay shows each step (verify → encrypt → range proof → submit).
  2. Stealth Output: A one-time stealth output is derived from the recipient’s view key via ECDH so the recipient, and only the recipient, can detect it.
  3. Broadcast: The encrypted payload and proof are submitted to the network.
  4. Validation: Validators verify the proof on encrypted data without learning the amount.
  5. Claim: The recipient scans for incoming stealth outputs and claims them into their private balance.

​
Transaction Details

  • Speed: Slower than a public send because proofs are generated locally
  • Privacy: Amount is encrypted; the sender’s address may be visible, the recipient is shielded behind a stealth output
  • Network fee: Quoted live from the node (proof-bearing transactions cost more ou than a plain transfer)
Private transfers require the recipient to claim the stealth output before the funds appear in their private balance. See Receiving Funds and Privacy Operations.

​
Bulk Send

Send to multiple recipients in one flow. Each recipient is submitted as its own transaction and tracked individually, so the batch reports per-recipient success and failure.
1

Open Bulk / Batch Mode

Switch the Send screen to bulk (the extension and mobile use a “Bulk” tab; desktop uses a “Batch” tab).
2

Add Recipients

Add addresses with individual amounts.
  • Extension and mobile: add up to 5 recipients, each with its own address and amount; remove rows with the trash icon.
  • Desktop: add rows individually or paste/import a CSV (address,amount per line). A live batch summary shows the running total, flags duplicate addresses, and warns when the total exceeds your available balance.
3

Choose Balance Type

Select the Public balance as the source. Private (FHE) bulk sends are available only in 0xio Desktop; the extension and mobile app send privately to one recipient at a time.
4

Review Total

Review the total amount, the per-recipient breakdown, and the estimated fee.
5

Confirm

Confirm and sign. The wallet processes each transfer and reports how many succeeded.

​
When to Use Bulk Send

  • Time Saving: Queue many transfers from a single screen instead of one at a time
  • Ideal For:
    • Payroll and salary payments
    • Airdrops and token distributions
    • Multi-party settlements
    • Team payments
Bulk send submits a separate transaction per recipient, so total fees scale with the number of transfers; there is no per-batch discount.

​
Whitelisted Addresses (Mobile)

On the mobile app, you can mark an address you trust as whitelisted, either by ticking Whitelist this address on the Send screen or from the Address Book.
  • Whitelisting an address requires your PIN or biometrics.
  • Later sends to a whitelisted address skip the PIN or biometric check. You still see and confirm the review of every send.
  • The whitelist is checked at the moment you confirm, so changing the recipient after it was checked cannot slip past it.
  • Remove an address from the whitelist in the Address Book at any time.
Anyone holding your unlocked phone could send to a whitelisted address without your PIN. Whitelist only addresses you control or fully trust, and keep auto-lock on.

​
Transaction Priority

​
Custom Network Fees

You can customize the operational unit (ou) fee to control transaction priority:
  1. Tap the estimated network fee on the Send screen.
  2. Choose a priority level. The wallet pulls Standard, High, and Fast estimates from the node, or you can set a Custom ou amount.
  3. Higher ou = faster inclusion in blocks.
During network congestion, a higher ou value helps your transaction get processed sooner. The displayed presets are sourced live from the node, so exact values vary with network conditions.

​
Transaction States

​
Pending

  • Transaction submitted to network
  • Awaiting validator confirmation
  • Typically 3-10 seconds

​
Confirmed

  • Transaction included in block
  • Funds transferred successfully
  • Transaction hash available for explorer

​
Failed

  • Transaction rejected or reverted
  • Funds safely returned to your wallet
  • Common causes:
    • Insufficient balance for gas
    • Network connectivity issue
    • Invalid recipient address

​
Adding a Memo

Include a message with your transaction:
  1. Open the memo field on the Send screen
  2. Enter memo text (up to 200 characters)
  3. Note: The memo is stored on-chain and visible for public sends
Use Cases:
  • Payment references
  • Invoice numbers
  • Personal notes
Memos are permanent and cannot be edited after the transaction is confirmed.

​
Best Practices

​
Security

  • Always double-check recipient addresses
  • Send a small test transaction first for large amounts
  • Verify addresses through multiple channels
  • Be cautious of phishing attempts

​
Privacy

  • Use Private Balance for sensitive transactions
  • Encrypt funds before private transfers
  • Monitor pending claims for incoming private transfers

​
Efficiency

  • Use Bulk Send for multiple recipients
  • Consider standard priority unless urgent
  • Group similar transactions to save on fees