Skip to content
Blog

Arc logs most USDC payments twice. Here is how to count each one once.

2026-09-24

USDC on Arc is both the gas token and an ERC-20, so one payment can leave two Transfer logs. Counting both overstates the money by about two thirds. These are the rules Memoline uses, with the cases that trip people up.

On most chains, one token transfer leaves one Transfer log. On Arc, USDC is two things at once: the native currency that pays for gas, kept with 18 decimals, and an ERC-20 token at 0x3600…0000 with 6 decimals. Both interfaces move the same balance. That is convenient for wallets and a trap for anyone keeping books.

What the logs show

When USDC moves natively, Arc records a Transfer from a system address, 0xffff…fffE, with the amount in 18 decimals. When the move goes through the ERC-20 transfer() call, the USDC contract also emits its own Transfer, with the same amount in 6 decimals. So one payment can appear twice, in two units. A tool that adds up every Transfer it sees overstates the money. We measured about two thirds too much on a busy sample of real traffic.

The rules

  1. For USDC, the system address’s log is the truth. Read the amount from it, and ignore the USDC contract’s duplicate of the same move.
  2. Keep the exact 18-decimal amount. Divide by 10^12 for the 6-decimal figure people read, and note any remainder below a millionth instead of rounding it away.
  3. A transfer to yourself through the ERC-20 interface leaves no system log, because no balance changed. Record it from the contract’s log as a line to yourself that nets to zero, so it is not missing from the books.
  4. For EURC, read the token’s own log. It has no second interface.
  5. Gas is paid in USDC. The fee is gasUsed × effectiveGasPrice in 18 decimals and belongs to whoever sent the transaction.
  6. USDC that arrives from another chain through Circle’s CCTP is minted: a system Transfer from address zero. It is money in, counted once.

The payer side

A payment made through Arc’s Memo contract sits between a BeforeMemo event and a Memo event with the same memo index. A transfer between those two events, from the memo’s sender and in the memo’s token, is the one the memo describes. That is how an invoice number written on-chain is tied to the right money, and a memo with no transfer beside it ties to nothing. When Memoline built or settled the payment itself, it also checks that the memo’s call-data hash matches the transfer exactly.

Try it

Paste any Arc address or transaction into Memoline’s reconcile page or the proof page for a transaction. The same rules run in Memoline’s ledger core, with tests built on real Arc receipts. The developer page shows the JSON API.