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 presents a tightly scoped, on-chain product with observable mechanics: users launch coins paired to NFT collections on Robinhood Chain (EIP-155:4663), and creator fees are routed to vaults that sweep floor listings via Seaport, with NFTs distributed through drand-backed raffles. The docs (web_2) detail an end-to-end flow—launch, trade, harvest, sweep, settle—with immutable contract constraints (e.g., no withdraw function, fixed 80/20 split, vault-only ETH→NFT conversion). Contract addresses are published and cross-referenced across sources (web_1, web_2, api_2), including the token (0xe02c…1386), Launcher, RaffleDistributor, and Seaport 1.6. The architecture enforces clear custody boundaries: vaults hold ETH but cannot withdraw it; NFTs exit only via raffle claims; randomness is pinned to drand rounds with public verification windows.
However, no evidence confirms live user activity or retention. There is no on-chain volume, holder growth, or transaction history in the supplied snapshot—only static documentation and contract metadata. The MVP is logically complete and technically specified, but its execution remains unobserved: no screenshots, interactive demo, or verified transaction traces demonstrate a real user completing the full journey from coin launch to NFT claim. The token supply data (api_2) shows circulating supply (~959M) and max supply (1B), but no liquidity, trading pairs, or usage metrics are provided. While the design rigorously addresses known failure modes (e.g., challengeable snapshots, time-locked external withdrawals), absence of behavioral telemetry caps confidence. This is a strong, well-documented protocol—but not yet a verified live product.
Overall score: 7/10 Confidence: Medium