I agree. We don't need to put everything on 30382.
What we do need is to specify what the "service" is calculating so that the user can chose which provider of that calculation they trust and clients can know what the value means.
There will be some differences between providers, but the goal and the final result spec (type, range, tags, etc) should be just one.
Hopefully this NIP enables that multiple provider specification to come together.
Vitor Pamplona
npub1gc…fnj5z
2024-10-11 14:27:38
in reply to nevent1q…ky3t
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-10-11 14:27:38Event JSON
{
"id": "f4b7c043cfbb55aed1730790049c607f1e042a5a2b6cd6003abd4eedddba5a3d",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1728656858,
"kind": 1,
"tags": [
[
"e",
"ebba38aff4f5e02c614bcfd3daed805dc44ebdf305bdf0ff17c058ed3b33df72",
"",
"root"
],
[
"e",
"ebba38aff4f5e02c614bcfd3daed805dc44ebdf305bdf0ff17c058ed3b33df72",
"",
"root"
],
[
"e",
"830f1279e90edbbab6453c4366d6bb136c75570ce0b102aa29845454babee71d",
"",
"reply"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
],
[
"p",
"f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11"
]
],
"content": "I agree. We don't need to put everything on 30382. \n\nWhat we do need is to specify what the \"service\" is calculating so that the user can chose which provider of that calculation they trust and clients can know what the value means.\n\nThere will be some differences between providers, but the goal and the final result spec (type, range, tags, etc) should be just one. \n\nHopefully this NIP enables that multiple provider specification to come together. ",
"sig": "606ff8edc66eaf88b1e4dfe56fe4a6f8938050905b6a8f6a200855e295998dd91484c6ec13e0f191336e9230e7dc4264ba80182c9e8e340c935913224f4c7aac"
}