VM5 Delivery Lab
Free CLI · No npm login · No API keys · No wallet signing

Catch Base USDC payout CSV mistakes in your terminal.

For recurring contributor bounties, payroll exports and engineering pipelines: verify basic address formatting, duplicates, exactly six-decimal token amounts, Base chain and USDC token syntax before giving a payout list to a real sender.

Get the local CLI ↓ Use the free browser version ↗

This is an original free, AI-assisted source project, not a custodial payout API or human-audited on-chain compliance service. No private keys, raw wallet data, payments, telemetry or API credentials are transmitted by the CLI.

Real original public repository

Install by cloning the source.

You don't need an npm account. Clone the owner-controlled repository once. It contains the same checker.mjs logic as the public browser tool plus a small offline CLI wrapper.

git clone https://github.com/livastic-vm5-primary-20260911/vm5-delivery-lab.git
cd vm5-delivery-lab
node tools/base-usdc-payout-csv-cli.mjs --help
node tools/base-usdc-payout-csv-cli.mjs --version

CLI v1.0.0 GitHub release ↗ Review exact CLI source ↗

If you use a release asset, verify the published SHA-256 on the GitHub release page. The full source is MIT-licensed. No credentials, external installs or npm registry publication are needed.

One valid local file

node tools/base-usdc-payout-csv-cli.mjs --file ./authorized-payees.csv

JSON result for an existing automated workflow

cat ./authorized-payees.csv \
  | node tools/base-usdc-payout-csv-cli.mjs --stdin --json --strict \
  > private-row-check-results.json

# Exit 0 = no syntax problems under requested strictness.
# Exit 1 = data errors (or warnings under --strict).
# Exit 2 = usage, parsing or I/O failure.
# Not a blockchain ownership/transaction verification.

Test without private recipient files

node tools/base-usdc-payout-csv-cli.mjs --demo --json

Share CLI feedback and your generic CSV header format ↗

Feedback is a public GitHub issue. Never paste real recipient addresses or confidential payout data; use synthetic examples only. Feedback is free and never creates a paid order.

The sample is deliberately broken: this command returns exit 1 and shows 3 errors and 1 warning. That is a correct result. The printed synthetic 6.7 USDC partial total is not money owned, paid or received by anybody.

Explicit safety limits

It reports data issues. It never approves a payment.

What it really checks

Strict quoted CSV parsing; field count; nonzero 40-character hexadecimal EVM address shapes; case-insensitive duplicate recipients; positive, fixed-point Base USDC amounts in exact atomic units; explicit chain and canonical token column; formula-like data-cell prefixes.

Maximum 64 KiB, 500 rows, 8 columns.

What it never claims

Ownership or EIP-55 checksums; recipient verification, sanctions, chain state, allowances, token balances, fraud screening, gas simulation, legal compliance, contracts, actual transactions, payment finality or customer safety guarantees.

Never send cryptocurrency based only on a zero-error report.

This CLI accepts files from local disk or stdin and reports issue codes and row/column positions; it does not print source addresses, recipient notes or raw data cells. For private payroll, never commit the CSV or generated client information to a public GitHub repository. A cloud CI runner may still process files on that third-party provider; the CLI itself makes no network requests.

Before any crypto payment, check the real person's recipient address, correct chain (Base, 8453), canonical Circle USDC token (0x833589fCD6eDb6E08f4C7C32D4f71b54bdA02913), appropriate EIP-55 checksum verification, sanctions/KYC obligations where applicable, amounts and actual sender-wallet simulation using separately authorized tools.

After payout: separate evidence review

CSV input was clean. Was the transfer actually completed?

Our same-owner VM3 project provides an independent free, browser-local candidate receipt CSV reviewer for supplied Base USDC txHash/logIndex and partial-payment fields. It can flag inconsistent copied records, but does NOT fetch chain data, prove receipt or turn a candidate CSV into settled money. Never mark an invoice paid without independently verified chain receipts and valid business records.

Free VM3 candidate Base USDC receipt review ↗