diff --git a/107.md b/107.md index 4d2b494..642ee19 100644 --- a/107.md +++ b/107.md @@ -39,14 +39,14 @@ A `user` can publish these event kinds: The content of events can be transmitted in clear text (for public data) or as [NIP-59 Gift Wrap](https://github.com/staab/nips/blob/NIP-59/59.md). -### Intent Events +## Intent Events Intent Events represent different actions that can be performed on a device. These actions can be triggered by a `user` or by another `device`. The content of the event is a `JSON` which `MUST` have a `type` field indicating the what the JSON represents. Possible types: | Message Type | Sent By | Description | |--------------|----------------|------------------| | 0 | User | Configure Device | -### Event: Configure `device` +### Configure Device This message is sent by a `user` to a `device`. The `device` saves the config locally and then uses it. **Event Content**: @@ -62,11 +62,11 @@ This message is sent by a `user` to a `device`. The `device` saves the config lo } ``` -Note: - - `admin_pubkeys`: - - list of public keys that are allowed to configure this device. A fresh/blank device will not have this value, so the first received `"type: 0"` should set it. - - `users`: - - a list that can restrict access to public-keys, `device`(s) also has keys and can be a `user`. +| Field | Description | +|---|---| +| `admin_pubkeys` | List of public keys that are allowed to configure this device.
A fresh/blank device will not have this value, so the first received `"type: 0"` should set it. | +| `send_to_pubkeys` | | +| `commands_from_pubkeys` | | ### Event: Update a `device`