mirror of
https://github.com/nostr-protocol/nips.git
synced 2026-01-27 04:28:49 +00:00
Compare commits
5 Commits
f34e98c73f
...
master
| Author | SHA1 | Date | |
|---|---|---|---|
|
acf74f8c29 | ||
|
d33bcbac7c | ||
|
b58a6048b1 | ||
|
|
f461065c29 | ||
|
|
eb252ccfc4 |
20
29.md
20
29.md
@@ -120,21 +120,21 @@ Clients can send these events to a relay in order to accomplish a moderation act
|
||||
|
||||
Each moderation action uses a different kind and requires different arguments, which are given as tags. These are defined in the following table:
|
||||
|
||||
| kind | name | tags |
|
||||
| --- | --- | --- |
|
||||
| 9000 | `put-user` | `p` with pubkey hex and optional roles |
|
||||
| 9001 | `remove-user` | `p` with pubkey hex |
|
||||
| 9002 | `edit-metadata` | fields from `kind:39000` to be modified |
|
||||
| 9005 | `delete-event` | `e` with event id hex |
|
||||
| 9007 | `create-group` | |
|
||||
| 9008 | `delete-group` | |
|
||||
| 9009 | `create-invite` | |
|
||||
| kind | name | tags |
|
||||
| --- | --- | --- |
|
||||
| 9000 | `put-user` | `p` with pubkey hex and optional roles |
|
||||
| 9001 | `remove-user` | `p` with pubkey hex |
|
||||
| 9002 | `edit-metadata` | fields to be modified, and optionally `unrestricted`, `open`, `visible` `public` |
|
||||
| 9005 | `delete-event` | `e` with event id hex |
|
||||
| 9007 | `create-group` | |
|
||||
| 9008 | `delete-group` | |
|
||||
| 9009 | `create-invite` | arbitrary `code` |
|
||||
|
||||
It's expected that the group state (of who is an allowed member or not, who is an admin and with which permission or not, what are the group name and picture etc) can be fully reconstructed from the canonical sequence of these events.
|
||||
|
||||
### Group metadata events
|
||||
|
||||
These events contain the group id in a `d` tag instead of the `h` tag. They MUST be created by the relay master key only and a single instance of each (or none) should exist at all times for each group. They are merely informative but should reflect the latest group state (as it was changed by moderation events over time).
|
||||
These events contain the group id in a `d` tag instead of the `h` tag. They MUST be created by the relay master key only (as stated by the [NIP-11](11.md) `"self"` pubkey) and a single instance of each (or none) should exist at all times for each group. They are merely informative but should reflect the latest group state (as it was changed by moderation events over time).
|
||||
|
||||
- *group metadata* (`kind:39000`) (optional)
|
||||
|
||||
|
||||
15
46.md
15
46.md
@@ -97,18 +97,25 @@ Each of the following are methods that the _client_ sends to the _remote-signer_
|
||||
|
||||
| Command | Params | Result |
|
||||
| ------------------------ | ------------------------------------------------- | ---------------------------------------------------------------------- |
|
||||
| `connect` | `[<remote-signer-pubkey>, <optional_secret>, <optional_requested_permissions>]` | "ack" OR `<required-secret-value>` |
|
||||
| `connect` | `[<remote-signer-pubkey>, <optional_secret>, <optional_requested_perms>]` | `"ack"` OR `<required-secret-value>` |
|
||||
| `sign_event` | `[<{kind, content, tags, created_at}>]` | `json_stringified(<signed_event>)` |
|
||||
| `ping` | `[]` | "pong" |
|
||||
| `get_public_key` | `[]` | `<user-pubkey>` |
|
||||
| `ping` | `[]` | `"pong"` |
|
||||
| `get_public_key` | `[]` | `<user-pubkey>` |
|
||||
| `nip04_encrypt` | `[<third_party_pubkey>, <plaintext_to_encrypt>]` | `<nip04_ciphertext>` |
|
||||
| `nip04_decrypt` | `[<third_party_pubkey>, <nip04_ciphertext_to_decrypt>]` | `<plaintext>` |
|
||||
| `nip44_encrypt` | `[<third_party_pubkey>, <plaintext_to_encrypt>]` | `<nip44_ciphertext>` |
|
||||
| `nip44_decrypt` | `[<third_party_pubkey>, <nip44_ciphertext_to_decrypt>]` | `<plaintext>` |
|
||||
| `switch_relays` | `[]` | `["<relay-url>", "<relay-url>", ...]` OR `null` |
|
||||
|
||||
### Requested permissions
|
||||
|
||||
The `connect` method may be provided with `optional_requested_permissions` for user convenience. The permissions are a comma-separated list of `method[:params]`, i.e. `nip44_encrypt,sign_event:4` meaning permissions to call `nip44_encrypt` and to call `sign_event` with `kind:4`. Optional parameter for `sign_event` is the kind number, parameters for other methods are to be defined later. Same permission format may be used for `perms` field of `metadata` in `nostrconnect://` string.
|
||||
The `connect` method may be provided with `optional_requested_perms` for user convenience. The permissions are a comma-separated list of `method[:params]`, i.e. `nip44_encrypt,sign_event:4` meaning permissions to call `nip44_encrypt` and to call `sign_event` with `kind:4`. Optional parameter for `sign_event` is the kind number, parameters for other methods are to be defined later. Same permission format may be used for `perms` field of `metadata` in `nostrconnect://` string.
|
||||
|
||||
### Switching relays
|
||||
|
||||
At all times, the _remote-signer_ should be in control of what relays are being used for the connection between it and the _client_. Therefore it should be possible for it to evolve its set of relays over time as old relays go out of operation and new ones appear. Even more importantly, in the case of the connection initiated by the _client_ the client may pick relays completely foreign to the _remote-signer_'s preferences, so it must be possible for it to switch those immediately.
|
||||
|
||||
Therefore, compliant clients should send a `switch_relays` request immediately upon establishing a connection (always, or at reasonable intervals). Upon receiving such requests, the _remote-signer_ should reply with its updated list of relays, or `null` if there is nothing to be changed. Immediately upon receiving an updated relay list, the _client_ should update its local state and send further requests on the new relays. The `remote-signer` should then be free to disconnect from the previous relays if that is desired.
|
||||
|
||||
## Response Events `kind:24133`
|
||||
|
||||
|
||||
132
85.md
Normal file
132
85.md
Normal file
@@ -0,0 +1,132 @@
|
||||
NIP-85
|
||||
======
|
||||
|
||||
Trusted Assertions
|
||||
------------------
|
||||
|
||||
`draft` `optional`
|
||||
|
||||
Certain Webs of Trust calculations require access to a large volume of events and/or computing power, making it virtually impossible to perform them directly on clients. This NIP allows users to offload such calculations to declared trusted service providers, and for these providers to publish signed "Trusted Assertion" events for the user client's consumption.
|
||||
|
||||
## Assertion Events
|
||||
|
||||
Trusted Assertions are always addressable (replaceable) events with the `d` tag pointing to the "subject" of the assertion. This NIP currently recognizes three distinct target "subjects" on which such calculations can be performed: *pubkeys*, *regular events*, and *addressable events*. Each subject type is mapped to an event kind:
|
||||
|
||||
| Subject | Event Kind | `d` tag value |
|
||||
| ------------------ | -------------- | ----------------- |
|
||||
| User | 30382 | `<pubkey>` |
|
||||
| Event | 30383 | `<event_id>` |
|
||||
| Addressable Event | 30384 | `<event_address>` |
|
||||
| NIP-73 Identifier | 30385 | `<i-tag>` |
|
||||
|
||||
Calculation results are saved in pre-defined tags whose syntax and semantics are agreed upon by providers and clients.
|
||||
|
||||
Example of ranking a pubkey with a web of trust score of `89`:
|
||||
|
||||
```jsonc
|
||||
{
|
||||
"kind": 30382,
|
||||
"tags": [
|
||||
["d", "e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411"], // target user's public key
|
||||
["rank", "89"],
|
||||
],
|
||||
"content": "",
|
||||
//...
|
||||
}
|
||||
```
|
||||
|
||||
## Kind 30382: Users as Subject:
|
||||
|
||||
The following result types have been declared:
|
||||
|
||||
| Result type | Tag name | Tag value format |
|
||||
| ----------------------- | ---------------------- | ----------------- |
|
||||
| Follower Count | `followers` | int |
|
||||
| User Rank | `rank` | int, norm 0-100 |
|
||||
| First Post Time | `first_created_at` | unix timestamp |
|
||||
| Post Count | `post_cnt` | int |
|
||||
| Reply Count | `reply_cnt` | int |
|
||||
| Reactions Count | `reactions_cnt` | int |
|
||||
| Zap Amount Received | `zap_amt_recd` | int, sats |
|
||||
| Zap Amount Sent | `zap_amt_sent` | int, sats |
|
||||
| Zap Number Received | `zap_cnt_recd` | int |
|
||||
| Zap Number Sent | `zap_cnt_sent` | int |
|
||||
| Avg Zap Amount/day recd | `zap_avg_amt_day_recd` | int, sats |
|
||||
| Avg Zap Amount/day sent | `zap_avg_amt_day_sent` | int, sats |
|
||||
| Reports Received | `reports_cnt_recd` | int |
|
||||
| Reports Sent | `reports_cnt_sent` | int |
|
||||
| Common Topics | `t` | string |
|
||||
| Generally active start | `active_hours_start` | int, 0-24, UTC |
|
||||
| Generally active end | `active_hours_end` | int, 0-24, UTC |
|
||||
|
||||
Each provider can offer their own ways to calculate such values. For instance, the Follower Count of one trust provider might remove the user's muted public keys while another provider keeps them. Users can then choose how they want to see this information in their preferred client by picking a provider that aligns with their view.
|
||||
|
||||
## Kind 30383: Events as Subject
|
||||
|
||||
Providers can rate individual events with the following tags:
|
||||
|
||||
| Result type | Tag name | Tag value format |
|
||||
| ----------------------- | ---------------------- | ----------------- |
|
||||
| Event Rank | `rank` | int, norm 0-100 |
|
||||
| Event Comment Count | `comment_cnt` | int |
|
||||
| Event Quote Count | `quote_cnt` | int |
|
||||
| Event Repost Count | `repost_cnt` | int |
|
||||
| Event Reaction Count | `reaction_cnt` | int |
|
||||
| Event Zap Count | `zap_cnt` | int |
|
||||
| Event Zap Amount | `zap_amount` | int, sats |
|
||||
|
||||
## Kind 30384: Addressables as Subject
|
||||
|
||||
Providers can rate all versions of addressable events using the following tags:
|
||||
|
||||
| Result type | Tag name | Tag value format |
|
||||
| ------------------------- | ---------------------- | ----------------- |
|
||||
| Address Rank | `rank` | int, norm 0-100 |
|
||||
| Address Comment Count | `comment_cnt` | int |
|
||||
| Address Quote Count | `quote_cnt` | int |
|
||||
| Address Repost Count | `repost_cnt` | int |
|
||||
| Address Reaction Count | `reaction_cnt` | int |
|
||||
| Address Zap Count | `zap_cnt` | int |
|
||||
| Address Zap Amount | `zap_amount` | int, sats |
|
||||
|
||||
## Kind 30385: External identifier as Subject
|
||||
|
||||
Providers can rate books, locations, movies, websites, and hashtags using [NIP-73](73.md) identifiers.
|
||||
|
||||
| Result type | Tag name | Tag value format |
|
||||
| ----------------- | ---------------------- | ----------------- |
|
||||
| Rank | `rank` | int, norm 0-100 |
|
||||
| Comment Count | `comment_cnt` | int |
|
||||
| Reaction Count | `reaction_cnt` | int |
|
||||
|
||||
NIP-73 `k` tags should be added to the event as well.
|
||||
|
||||
## Declaring Trusted Service Providers
|
||||
|
||||
Kind `10040` lists the user's authorized providers for each result. Each `kind:tag` is followed by the `pubkey` of the service and the relay where the results are published. Users can specify these publicly or privately by JSON-stringifying and encrypting the tag list in the `.content` using NIP-44.
|
||||
|
||||
```js
|
||||
{
|
||||
"kind": 10040,
|
||||
"tags": [
|
||||
["30382:rank", "4fd5e210530e4f6b2cb083795834bfe5108324f1ed9f00ab73b9e8fcfe5f12fe", "wss://nip85.nostr.band"],
|
||||
["30382:rank", "3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d", "wss://nostr.wine"],
|
||||
["30382:zap_amt_sent", "4fd5e210530e4f6b2cb083795834bfe5108324f1ed9f00ab73b9e8fcfe5f12fe", "wss://nip85.nostr.band"],
|
||||
],
|
||||
"content": nip44Encrypt(JSON.stringify([
|
||||
["30383:rank", "4fd5e210530e4f6b2cb083795834bfe5108324f1ed9f00ab73b9e8fcfe5f12fe", "wss://nip85.nostr.band"],
|
||||
["30384:rank", "4fd5e210530e4f6b2cb083795834bfe5108324f1ed9f00ab73b9e8fcfe5f12fe", "wss://nip85.nostr.band"],
|
||||
]),
|
||||
//...
|
||||
}
|
||||
```
|
||||
|
||||
If the provider offers several algorithms or multiple points of view of an algorithm, the key listed in each tag SHOULD point to the key created for each algorithm or point of view.
|
||||
|
||||
## Final Considerations
|
||||
|
||||
Service providers SHOULD update Trusted Assertions as fast as new information arrives, but only if the contents of each event actually change to avoid re-downloading the same information.
|
||||
|
||||
Service providers MAY limit access to the results by using paid relays.
|
||||
|
||||
In TAs, `p`, `e`, and `a` tags with the same value as the `d` tag MAY be used to add a relay hint to the home relay of that user or event.
|
||||
Reference in New Issue
Block a user