Skip to content

Conversation

@alltheseas
Copy link
Contributor

  • Added an explicit requirement for the mandatory ["d", …] tag so kind:30402 listings actually behave as NIP-01 addressable events and can be fetched or replaced reliably across relays.
    • Documented how related events should reference listings via the ["a","::"] tag to keep cross-event linking interoperable.

- Added an explicit requirement for the mandatory ["d", …] tag so kind:30402 listings actually behave as NIP-01 addressable events and can be fetched or replaced reliably across relays.
  - Documented how related events should reference listings via the ["a","<kind>:<pubkey>:<d>"] tag to keep cross-event linking interoperable.
@alltheseas
Copy link
Contributor Author

cc @aceaspades

@staab
Copy link
Member

staab commented Oct 30, 2025

This NIP isn't very well written, but this PR isn't really the solution. Kind 30402 isn't even explicitly defined here. https://github.com/nostr-protocol/nips/blob/master/17.md is an example of a more conventional way of introducing new kinds. It could be worth while re-writing this NIP to follow that format.

@luigi1256
Copy link

Kind 30402 isn't even explicitly defined here

it is probably defined in the extension GammaMarkets/market-spec

@staab
Copy link
Member

staab commented Oct 31, 2025

@GammaMarkets would you be willing to open a PR to update this NIP? Are there any areas that your spec is incompatible with this one, or is it purely an extension? Do you have any idea of which clients implement which versions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants