{"content":"IDBots dev journal - feat: wallet_tx_status + wallet_tx_verify (Phase 1 T2+T3, commit 5cb5334af on feat/wallet-tools-phase1)\n\nAfter the Phase 0 balance fix, the agent still had no way to answer 'did this tx land?' or 'did they really pay?' - the incident bot improvised curl calls. T2+T3 give it real tools with honest evidence grading.\n\n- wallet_tx_status: BTC via mempool.space ESPLORA (block height, confirmations via tip height, fee, output addresses); DOGE via blockchair (confirmed txs only - pending reports as not-found, noted in output); MVC has NO reachable public tx-status JSON API (mvcscan serves an SPA, explorer.microvisionchain.com unreachable), so confirmation is DERIVED: metalet raw-tx endpoint proves the tx exists, and the receiver's utxo-list (height > 0, same rule as wallet_balance) proves confirmation - reported with its evidence class, including the spent-onward caveat.\n- wallet_tx_verify: reuses the repo's own txTransferVerification decode layer (parseTxOutputs + pubkey-hash extraction now exported); native coins verify receiver+amount_sats against decoded outputs; MVC20 token outputs decode through meta-contract's token proto getters (genesis/codehash/amount/receiver hash attribution - round-trip verified against a proto-built script), with the receiver-side balance-list as labeled supporting evidence.\n- Verdicts: VERIFIED / MISMATCH / NOT_FOUND / INSUFFICIENT_EVIDENCE. Subtle rule: if the moved token total matches but the share attributed to the named receiver is short (change went elsewhere), that is a MISMATCH - the receiver did not get paid.\n\nValidation: compile exit 0; test:wallet 37/37 green (14 new tests: both MVC confirmation derivations, BTC pending/confirmed, DOGE ISO-time shape, native verify/mismatch, MVC20 exact/attribution-shortfall/mismatch/insufficient-evidence).","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}