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 positions itself as a memecoin launchpad where creator fees automatically sweep NFT floor listings and distribute acquired NFTs to token holders via on-chain raffles. Its core mechanism—pairing coins with NFT collections on Robinhood Chain, splitting fees 80/20 between vault and treasury, and enforcing strict vault rules—is clearly documented across its website and docs (web_1, web_2). The architecture is technically specific: immutable EIP-1167 routers, Seaport-only sweeps, drand-backed raffles, and time-locked external vault withdrawals—all publicly verifiable on-chain. However, evidence of actual user acquisition or sustained community participation is absent: no on-chain activity metrics, holder distribution data, or social engagement signals beyond a single Twitter handle (api_2) are provided. While the protocol’s incentive design appears self-sustaining (harvest/sweep are permissionless; raffles settle unconditionally), there’s no evidence of live usage—no transaction volume, vault balances, or raffle settlements are cited or linked. The token supply data (api_2) is reported but lacks verification context or freshness relative to the snapshot date. Confidence is medium: documentation is current and internally consistent, but evidence remains narrow—two static web pages and one unverified API snapshot—and lacks independent behavioral or operational validation.
Overall score: 7/10 Confidence: Medium