nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-15 00:09:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix typos

Browse Source
This commit is contained in:
Vitor Pamplona 2024-10-11 09:43:07 -04:00 committed by GitHub
parent e666636859
commit 9c38c8eb6d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
85.md
View File

@ -6,9 +6,9 @@ Trusted Assertions
`draft` `optional` `draft` `optional`
Certain calculations in Nostr require access to the entire dataset of events and are impossible to do directly by Clients. This NIP allows the creation of services that can perform such calculations and output signed events for each result in a continuous basis. Each calculation types receives a separate event kind. Users can setup which service providers they trust to perform these calculations and Clients can load and display the results accordingly. Certain calculations in Nostr require access to the entire dataset of events and are impossible to do directly by Clients. This NIP allows the creation of services that can perform such calculations and output signed events for each result continuously. Each calculation type receives a separate event kind. Users can set up which service providers they trust to perform these calculations so that Clients can load and display the results accordingly.
Assertions are always addressable events with the `d` tag pointing to the subject of the assertion. Assertions are always addressable events with the `d` tag pointing to the subject of the assertion. The following kinds and tags have been specified:
| name | kind | `d` tag value | result tags | | name | kind | `d` tag value | result tags |
| -------------------- | ----- | ------------- | --------------------------------------- | | -------------------- | ----- | ------------- | --------------------------------------- |
@ -34,7 +34,7 @@ Example:
} }
``` ```
Service providers SHOULD update their results constantly and MAY limit access to their results by using paid relays. Service providers SHOULD update their results constantly and MAY limit access by using paid relays.
## Declaring Trusted Service Providers ## Declaring Trusted Service Providers
@ -53,4 +53,4 @@ Kind `10040` lists the user's authorized providers for each service. The service
} }
``` ```
Clients should download this list, load and display assertions when appropriate. Clients should download this list, and load and display assertions when appropriate.