Nostr

Delivery: Source-only. Nostr gives Fased a lightweight decentralized DM lane without a central service account. The gateway signs in with a Nostr private key, listens on one or more relays, and routes encrypted DMs into the normal Fased session model. Status: source extension, disabled until configured.

Setup from Agent > Channels

Nostr is available from a source install. The lightweight hosted runtime does not currently include nostr-tools, and Nostr does not yet have an official Fased add-on package. Use a maintained source install for this channel. Open Agents, select the Agent, then use Agent > Channels > Nostr. Enter the private key and relay list, save the channel, then restart the gateway if the UI reports that the runtime still needs to load.

Quick setup

For most setups, treat Nostr as a DM-only channel with explicit allowlists. Start with one keypair and two or three relays, then widen from there only if you need more reach.

Generate a Nostr keypair (if needed):

# Using nak
nak key generate

Add the private key in Agent > Channels > Nostr or config:

{
  "channels": {
    "nostr": {
      "privateKey": "${NOSTR_PRIVATE_KEY}"
    }
  }
}

Export the key:

export NOSTR_PRIVATE_KEY="nsec1..."

Restart the Gateway if the UI asks for it.

Configuration reference

Key	Type	Default	Description
`privateKey`	string	required	Private key in `nsec` or hex format
`relays`	string[]	`['wss://relay.damus.io', 'wss://nos.lol']`	Relay URLs (WebSocket)
`dmPolicy`	string	`pairing`	DM access policy
`allowFrom`	string[]	`[]`	Allowed sender pubkeys
`enabled`	boolean	`true`	Enable/disable channel
`name`	string	-	Display name
`profile`	object	-	NIP-01 profile metadata

Profile metadata

Profile data is published as a NIP-01 kind:0 event. You can manage it from Agent > Channels > Nostr > Profile or set it directly in config. Example:

{
  "channels": {
    "nostr": {
      "privateKey": "${NOSTR_PRIVATE_KEY}",
      "profile": {
        "name": "fased",
        "displayName": "Fased",
        "about": "Personal assistant DM bot",
        "picture": "https://example.com/avatar.png",
        "banner": "https://example.com/banner.png",
        "website": "https://example.com",
        "nip05": "[email protected]",
        "lud16": "[email protected]"
      }
    }
  }
}

Notes:

Profile URLs must use https://.
Importing from relays merges fields and preserves local overrides.

Access control

DM policies

pairing (default): unknown senders get a pairing code.
allowlist: only pubkeys in allowFrom can DM.
open: public inbound DMs (requires allowFrom: ["*"]).
disabled: ignore inbound DMs.

Allowlist example

{
  "channels": {
    "nostr": {
      "privateKey": "${NOSTR_PRIVATE_KEY}",
      "dmPolicy": "allowlist",
      "allowFrom": ["npub1abc...", "npub1xyz..."]
    }
  }
}

Key formats

Accepted formats:

Private key: nsec... or 64-char hex
Pubkeys (allowFrom): npub... or hex

Relays

Defaults: relay.damus.io and nos.lol.

{
  "channels": {
    "nostr": {
      "privateKey": "${NOSTR_PRIVATE_KEY}",
      "relays": ["wss://relay.damus.io", "wss://relay.primal.net", "wss://nostr.wine"]
    }
  }
}

Tips:

Use 2-3 relays for redundancy.
Avoid too many relays (latency, duplication).
Commercial relays can improve reliability.
Local relays are fine for testing (ws://localhost:7777).

Protocol support

NIP	Status	Description
NIP-01	Supported	Basic event format + profile metadata
NIP-04	Supported	Encrypted DMs (`kind:4`)
NIP-17	Planned	Gift-wrapped DMs
NIP-44	Planned	Versioned encryption

Testing

Local relay

# Start strfry
docker run -p 7777:7777 ghcr.io/hoytech/strfry

{
  "channels": {
    "nostr": {
      "privateKey": "${NOSTR_PRIVATE_KEY}",
      "relays": ["ws://localhost:7777"]
    }
  }
}

Manual test

Note the bot pubkey (npub) from logs.
Open a Nostr client (Damus, Amethyst, etc.).
DM the bot pubkey.
Verify the response.

Troubleshooting

Not receiving messages

Verify the private key is valid.
Ensure relay URLs are reachable and use wss:// (or ws:// for local).
Confirm enabled is not false.
Check Gateway logs for relay connection errors.

Not sending responses

Check relay accepts writes.
Verify outbound connectivity.
Watch for relay rate limits.

Duplicate responses

Expected when using multiple relays.
Messages are deduplicated by event ID; only the first delivery triggers a response.

Security

Never commit private keys.
Use environment variables for keys.
Consider allowlist for production bots.

Limitations (MVP)

Direct messages only (no group chats).
No media attachments.
NIP-04 only (NIP-17 gift-wrap planned).

Overview

Common setup

Team and enterprise

Self-hosted and protocol

Optional and legacy

Configuration and behavior

Nostr

Nostr

Setup from Agent > Channels

Quick setup

Configuration reference

Profile metadata

Access control

DM policies

Allowlist example

Key formats

Relays

Protocol support

Testing

Local relay

Manual test

Troubleshooting

Not receiving messages

Not sending responses

Duplicate responses

Security

Limitations (MVP)

​Nostr

​Setup from Agent > Channels

​Quick setup

​Configuration reference

​Profile metadata

​Access control

​DM policies

​Allowlist example

​Key formats

​Relays

​Protocol support

​Testing

​Local relay

​Manual test

​Troubleshooting

​Not receiving messages

​Not sending responses

​Duplicate responses

​Security

​Limitations (MVP)

Nostr

Setup from Agent > Channels

Quick setup

Configuration reference

Profile metadata

Access control

DM policies

Allowlist example

Key formats

Relays

Protocol support

Testing

Local relay

Manual test

Troubleshooting

Not receiving messages

Not sending responses

Duplicate responses

Security

Limitations (MVP)