UseNosh (ticker: nosh) is a memecoin launchpad deployed on Robinhood Chain (EIP-155:4663), enabling creators to pair new tokens with NFT collections. Its core mechanism routes 80% of creator fees—collected via Pons V2’s bonding curve and Uniswap v4 pool—to a dedicated vault contract that can only purchase floor-listed NFTs from the paired collection, using Seaport 1.6 fulfillments under strict on-chain caps. The remaining 20% flows to the protocol treasury. The vault holds ETH but has no withdrawal function; NFTs exit exclusively through a drand-backed raffle system managed by RaffleDistributor (0x8D31c4C19a8a21719d6153CEE84A985338c8F9F8), with holder snapshots challengeable for 15 minutes before draw resolution. Documentation confirms the router contract (0xe02c53d448a62067b2ac10ed70f5bc6c29471386) is an immutable EIP-1167 clone, enforcing the 80/20 split at bytecode level. External collections are supported via ExternalSweepVault, where off-chain purchases are auditable via Zcash viewing keys and on-chain receipts. Key questions remain about keeper discretion in floor-cap posting and snapshot selection, the absence of formal audits, and whether the claimed multi-chain interoperability extends beyond Robinhood Chain in practice.

UseNosh implements a novel, on-chain mechanism for directing memecoin creator fees toward NFT floor sweeps on Robinhood Chain. Its core contracts — the fee router, vault, and raffle distributor — are described in detail across the website and docs (web_1, web_2), with explicit, immutable rules: 80/20 fee split hardcoded in EIP-1167-cloned routers; vaults lack withdraw functions and enforce Seaport-only, cap-bound sweeps; raffles use drand-backed OpenVRF with public challenge windows and permissionless draw resolution. Privileged actions are narrowly scoped: the keeper posts floor caps (1h TTL), snapshots holders, and opens raffles — but cannot withdraw ETH, re-roll draws, or override custody logic. External vaults introduce off-chain coordination but retain on-chain accountability via time-locked withdrawals and Zcash viewing keys (web_2). No audit reports, formal threat model, or third-party verification of contract behavior is present in the evidence. The primary thesis — that fees reliably convert to NFTs and distribute them fairly — rests entirely on claimed design, not verified execution or adversarial testing. Market data (api_2) shows circulating supply near max, but no liquidity, volume, or holder distribution metrics are supplied. While architecture is transparent and privilege surfaces are well-documented, absence of independent security validation limits confidence in runtime correctness.
Overall score: 7/10 Confidence: Medium