package hw.trezor.messages.nostr

Get desktop application:
View/edit binary Protocol Buffers messages

* Response: Computed event ID and signature @end

• required bytes pubkey = 1

  pubkey used to sign the event

• required bytes id = 2

  ID of the event

• required bytes signature = 3

  signature of the event

* Request: Ask the device for the Nostr public key @start @next NostrPubkey

• repeated uint32 address_n = 1

  used to derive the key

* Response: Nostr pubkey @end

• required bytes pubkey = 1

  pubkey derived from the seed

* Request: Ask device to sign an event @start @next NostrEventSignature @next Failure

• repeated uint32 address_n = 1

  used to derive the key

• required uint32 created_at = 2

  Event created_at: unix timestamp in seconds

• required uint32 kind = 3

  Event kind: integer between 0 and 65535

• repeated NostrTag tags = 4

  Event tags

• required string content = 5

  Event content: arbitrary string

* @embed

Used in: NostrSignEvent

• required string key = 1

  Nostr tags consist of at least one string (the key) followed by an arbitrary number of strings, the first of which (if present) is called "value". See NIP-01: https://github.com/nostr-protocol/nips/blob/master/01.md#tags

• optional string value = 2

• repeated string extra = 3