nostr-marketplace-builder

To create compliant Nostr marketplace events, generate stall, product, auction, bid, and P2P order events with correct IDs, content, and tag structures. Validate tag references, shipping calculations, and frontmatter metadata to ensure spec compliance across all event kinds.

A complete Nostr marketplace workflow requires kind:30017 for stalls, kind:30018 for products, kind:30020 for auctions, kind:1021 and kind:1022 for bids and confirmations, and kind:38383 for P2P orders. Each kind enforces specific tag structures and lifecycle rules.

Nostr auction events use kind:30020 with start_date and duration fields. The auction lifecycle becomes immutable after bids are placed, meaning the event content and core parameters cannot be edited once bidding has started to maintain auction integrity.

Yes, you can assemble Nostr kind:38383 P2P order events with tags describing payment methods, fiat currencies, status, and expiry. Validate field references like stall and product IDs to ensure the P2P trade event is safe for publishing.

Validate Nostr stall events by ensuring the d tag matches the content ID, checking stall and product references, and verifying shipping zone IDs. Enforce frontmatter-driven metadata like name and description, and validate per-unit shipping and quantity rules.

Provide an AI agent with a concrete marketplace scenario involving stalls, shipping, auctions, and payments. Ask it to output the full set of Nostr marketplace events and validate that all field references, tag structures, and shipping calculations conform to the spec.