Sending and receiving INT — basic transaction guide

Help & Support
1

How to send and receive INTcoin in either the Qt desktop wallet or via intcoin-cli. This is the basic happy-path guide; for fee bumping, multisig, hardware-wallet integration, etc. see other topics in Help & Support.

Receiving INT

You receive INT by giving someone a wallet address. Anyone can send to it; only you (the holder of the corresponding private key) can spend the received funds.

Qt wallet

  1. Open INTcoin Qt.
  2. Click the Receive tab.
  3. Click Request payment to generate a fresh address. Optionally fill in a label (private; just for your own bookkeeping) and an amount (the QR code embeds it for the sender’s convenience).
  4. Copy the address (or scan the QR code) and send it to the payer.
  5. The transaction appears in your Transactions tab as soon as your node hears about it on the P2P network. You’ll see:
    • Pending until the first confirmation (one block has built on top — usually within ~2 minutes).
    • Confirmed with a green tick after 6 confirmations (~12 minutes) for typical use; exchanges may require more.

CLI

intcoin-cli getnewaddress           # generate a fresh address
intcoin-cli getnewaddress "my-label" # ...with an optional label

You can generate as many addresses as you like — there’s no cost, and using a fresh address per transaction improves privacy. All addresses derived from your wallet share the same recovery seed.

To see your full balance:

intcoin-cli getbalance              # confirmed only
intcoin-cli getbalances             # detailed breakdown (trusted / pending / immature)

To see incoming transactions:

intcoin-cli listtransactions        # last 10 by default
intcoin-cli listtransactions "*" 50 # last 50, all labels

Sending INT

You send INT by specifying a destination address, an amount, and (implicitly) a fee. The wallet looks up your unspent outputs (UTXOs), constructs and signs the transaction, and broadcasts it to the network.

Qt wallet

  1. Open INTcoin Qt.
  2. Click the Send tab.
  3. Paste the destination address into Pay To.
  4. Enter the amount in Amount. The wallet checks your balance and warns if you’re trying to spend more than you have.
  5. (Optional) Add a label for your own record-keeping — this is local-only metadata.
  6. (Optional) Adjust the fee. The default uses estimated fee based on current mempool conditions; click Fee settings to override.
  7. Click Send. You’ll be prompted to enter your wallet passphrase if the wallet is encrypted.
  8. The transaction appears in your Transactions tab marked as Outgoing — Pending.

For multiple recipients in one transaction: click Add recipient before clicking Send. Multi-output transactions cost slightly more in fees (more outputs = more bytes) but consolidate sending.

CLI — simple send

intcoin-cli sendtoaddress <destination> <amount>

Example:

intcoin-cli sendtoaddress int1qghym2qqtwnaw5qv8vf7v3zdwmav6xnt2k0wy8z 10.5

Returns the txid. Watch its progress with:

intcoin-cli gettransaction <txid>

CLI — multiple recipients in one tx

intcoin-cli sendmany "" '{"int1q...A":1.5, "int1q...B":2.25, "int1q...C":0.1}'

The empty "" is an unused legacy parameter (account name); always pass it as empty.

CLI — modern send with options

The send RPC supports per-tx fee rate, RBF signalling, locktime, and other knobs:

intcoin-cli send '{"int1q...A":1.5}' '{"fee_rate":2,"replaceable":true}'

Fees

Fees pay miners to include your transaction in a block. The wallet estimates a sensible fee based on recent block contents — for normal use you don’t need to think about it.

If your transaction sits unconfirmed for a long time during a busy mempool, you can:

  1. Bump the fee if you signalled RBF (replaceable: true) — see the bumpfee docs.
  2. Wait — most chains clear within an hour even without bumping.
  3. Abandon if the transaction is yours and you want to free its inputs for a different send: intcoin-cli abandontransaction <txid>.

INTcoin’s mempool currently has near-zero contention (the network is small), so most transactions confirm within the first block — no fee tuning needed.

Common pitfalls

  • “Insufficient funds” when balance looks adequate. You may have immature coinbase outputs (mined coins waiting for the 100-confirmation maturity rule before they can be spent). getbalances shows these separately.
  • Sent to the wrong address. Cryptocurrency transactions are irreversible by design — there’s no “cancel” once a transaction is confirmed. Double-check addresses before clicking Send. Use the QR-code path when receiving from someone in person to eliminate transcription errors.
  • Wallet locked. If your wallet is encrypted, you’ll need to unlock it temporarily with walletpassphrase "<phrase>" 60 (60-second window) before signing.
  • Transaction not appearing in explorer. The explorer indexes the canonical chain; if your local node hasn’t relayed the transaction (e.g. you’re behind a firewall blocking outbound connections), peers don’t know about it. Check getconnectioncount and confirm getrawmempool includes the txid.

Privacy considerations

  • Address reuse leaks information. Anyone who sends to or receives from a known-yours address can link it to all your other transactions on that address. Generate a fresh address per incoming payment when possible.
  • Coin selection is automatic by default. The wallet picks UTXOs based on a privacy-aware algorithm, but if you need to control exactly which UTXOs are spent (e.g. for compliance reasons), use coin control in the Qt wallet or lockunspent from the CLI.
  • Network privacy. If you run your daemon over Tor or I2P (see the Privacy & Networking category), nobody on your network path can see which transactions you originate.

Questions? Post here or ask in #support on Discord.