calvadev⚡️ on Nostr: At the moment, I just send a normal message containing the buyer inputted info with ...
At the moment, I just send a normal message containing the buyer inputted info with the payment, but I was going to modify the NIP-15 spec and replace the NIP-04 requirement with NIP-17 and an "order-info" subject tag (that tag is already set in the current implementation btw).
Was thinking that when "type" is set to 0, it would require an address but not a contact. If type is set to 1, it would require a contact but not an address. Contact could also be changed to be more generic and not require Nostr, phone, or email.
Published at
2024-10-21 18:19:05Event JSON
{
"id": "d2c3a72b9ba1e4a1c5f484588c9a3aa1d4ca0009080d2150bc079351d94a26f6",
"pubkey": "d36e8083fa7b36daee646cb8b3f99feaa3d89e5a396508741f003e21ac0b6bec",
"created_at": 1729534745,
"kind": 1,
"tags": [
[
"e",
"35c24a820fab71934c165c5b78adc5666e1b72298b6863628bfda7657e412745",
"",
"root"
],
[
"p",
"d36e8083fa7b36daee646cb8b3f99feaa3d89e5a396508741f003e21ac0b6bec"
],
[
"p",
"c8383d81dd24406745b68409be40d6721c301029464067fcc50a25ddf9139549"
]
],
"content": "At the moment, I just send a normal message containing the buyer inputted info with the payment, but I was going to modify the NIP-15 spec and replace the NIP-04 requirement with NIP-17 and an \"order-info\" subject tag (that tag is already set in the current implementation btw).\n\nWas thinking that when \"type\" is set to 0, it would require an address but not a contact. If type is set to 1, it would require a contact but not an address. Contact could also be changed to be more generic and not require Nostr, phone, or email.",
"sig": "c765e6c303560344238c8269938c305747975897d8de607af783152e01e4d95eef0d133d3efe24ee059f0d22ad274ef9a55112c6e9bd4dd5c36f22f7057c1bb4"
}