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 tightly scoped, on-chain incentive architecture where creator fees from memecoins are programmatically split 80/20 between an NFT collection’s vault and protocol treasury. Governance is intentionally minimal: no upgradeable contracts, no owner keys on core routers or vaults, and no withdrawal functions—ETH only exits via provable Seaport sweeps, and NFTs only exit via drand-backed raffles (web_2). The keeper operator holds narrow, time-bound discretion: posting floor caps (TTL 1h), initiating raffles, and selecting holder snapshots—but cannot redirect funds, alter splits, or cancel raffles once pinned (web_2). Incentives align tightly for creators (upside is coin value, not direct fee extraction), traders (fee accrual fuels floor buys), and holders (NFT distribution via verifiable randomness). However, the keeper retains unilateral authority over which floor listings to fulfill and which snapshot to publish—both materially affect distribution fairness and lack on-chain challenge or override mechanisms (web_2). The vault’s inability to withdraw ETH is robust, but external collections introduce off-chain execution risk, relying on keeper-published Zcash viewing keys and manual delivery confirmation (web_2). No audit reports, team disclosures, or live usage metrics appear in supplied evidence, limiting verification of operational fidelity and adoption traction.
Overall score: 7/10 Confidence: Medium