nostr-protocol
Adding more useful tags to NIP 69
I'm currently working on an open source project that requires the use of event kind 38383 though not published yet I'd like to request an update to the tags of NIP 69
Problem: Clients and relays would love to get this type of events but have to deal with spams or events that do not meet standard of an actual p2p ads, so by that they'll need new standard tags to filter events they request or wish to store.
Example: say a relay wanted to store p2p ads that have links to verifiable creds of the creator of the ads or ads with review from public sources like twitter/x or Facebook or any other social media they're local in, same would go for a client requesting events from relays.
Solution: I'm suggesting additional tags to the tag fields to make it more standard (the tags can be renamed if it would conflict with any other)
- [rate," the rate they're exchanging at, based on the fiat currency"]
- ["volume", "the amount of the assets you have left"]
- ["reviews", "should either a list of url to public posts from SMs or a single link that can show this"]
- ["public creds", "this should point to public credential to promote Verifiability instead of trusting, so many sources can be used for this especially liveness checkers and even if they want to int passport publicly 😁 "]
- ["trade limit", "the amount the ads creator is willing to trade at minimum and maximum (min:1000, max:10,000)" ]
- ["success rate", "this data could come from any p2p platform that uses NIP 69 and now shareable to others that request the ads i.e [total orders/trades: 1000, successfully completed:95% ]"]
In essence i'm saying we could make the event more of a p2p ads like CEXs do with their p2p section for a better user experience thank you for your attention to this matter
💙 to all nostr contributors for building this vehicle that leads to freedom
Best thing would be to open a PR and point to any implementations. Once there are two clients that implement the changes, we can merge.
Best thing would be to open a PR and point to any implementations. Once there are two clients that implement the changes, we can merge.
ok thank you. I'll do that thanks for the direction