# nostr-bray

**Trust-aware Nostr MCP server, CLI and TypeScript SDK for AI and humans.** 261 tools across 29 groups. Model-agnostic. Works with Claude, ChatGPT, Gemini, Cursor, Windsurf, or any MCP client.

[![npm](https://img.shields.io/npm/v/nostr-bray)](https://www.npmjs.com/package/nostr-bray)
[![CI](https://github.com/forgesworn/bray/actions/workflows/ci.yml/badge.svg)](https://github.com/forgesworn/bray/actions/workflows/ci.yml)
[![licence](https://img.shields.io/npm/l/nostr-bray)](./LICENSE)
[![TypeScript](https://img.shields.io/badge/TypeScript-ESM-blue)](./tsconfig.json)
[![GitHub Sponsors](https://img.shields.io/github/sponsors/TheCryptoDonkey?logo=githubsponsors&color=ea4aaa&label=Sponsor)](https://github.com/sponsors/TheCryptoDonkey)

## Quick Start

Requires Node.js 24 or later.

Install globally or run via npx:

```bash
npm install -g nostr-bray
```

New to Nostr? Mint a key first -- this works before anything is configured
and prints your npub plus a 24-word mnemonic (write it down; it is the key):

```bash
npx nostr-bray create
```

Add to your MCP client config:

```json
{
  "mcpServers": {
    "nostr": {
      "command": "npx",
      "args": ["nostr-bray"],
      "env": {
        "NOSTR_SECRET_KEY": "nsec1...",
        "NOSTR_RELAYS": "wss://relay.damus.io,wss://nos.lol"
      }
    }
  }
}
```

`npx nostr-bray` with no arguments starts the MCP server (stdio by default, HTTP with `TRANSPORT=http`); subcommands run the CLI.

Then ask your AI to call `whoami` to verify it works.

For production use, prefer [Heartwood](https://github.com/forgesworn/heartwood) or any NIP-46 bunker (your key never leaves your signing device):

```json
{
  "mcpServers": {
    "nostr": {
      "command": "npx",
      "args": ["nostr-bray"],
      "env": {
        "BUNKER_URI": "bunker://...",
        "NOSTR_RELAYS": "wss://relay.damus.io,wss://nos.lol"
      }
    }
  }
}
```

### Auth tiers (best to worst)

| Tier | Method | Key exposure |
|------|--------|-------------|
| **Heartwood** | Dedicated signing appliance (`BUNKER_URI`) | Key never leaves the signing device. Supports nsec-tree derivation, per-client permissions, and device-backed attestations. |
| **Software bunker** | Any NIP-46 bunker (`BUNKER_URI`) | Key held by a separate process. Never seen by bray. |
| **ncryptsec** | NIP-49 encrypted key (`NOSTR_NCRYPTSEC`) | Key encrypted at rest, decrypted in memory at startup. |
| **Key file** | File path (`NOSTR_SECRET_KEY_FILE`) | Key on disk, read once, env var deleted. |
| **Env var** | Inline secret (`NOSTR_SECRET_KEY`) | Key visible in process environment. Use only for development. |

## Promoted tools

Of the 261 registered tools, 50 are promoted: callable directly from the MCP tool list. Everything else is catalogued, so find it with `search-actions` and run it with `execute-action` (both are always available). Nothing that spends is promoted.

- **Identity and social:** `whoami`, `identity-switch`, `social-post`, `social-reply`, `social-feed`, `social-profile-get`, `dm-send`, `dm-read`, `dm-conversation`
- **Wallet, relay and trust:** `zap-balance`, `relay-query`, `signet-badge`, `trust-score`, `verify-person`, `vault-read`
- **Publishing:** `article-publish`, `article-read`, `article-list`, `search-notes`, `search-profiles`, `hashtag-feed`
- **Badges, communities and calendar:** `badge-create`, `badge-award`, `badge-accept`, `badge-list`, `community-create`, `community-feed`, `community-post`, `community-approve`, `community-list`, `calendar-create`, `calendar-read`, `calendar-rsvp`
- **Listings:** `listing-create`, `listing-read`, `listing-search`, `listing-close`
- **Dispatch (13):** `dispatch-send`, `dispatch-check`, `dispatch-reply`, `dispatch-ack`, `dispatch-status`, `dispatch-cancel`, `dispatch-refuse`, `dispatch-failure`, `dispatch-query`, `dispatch-propose`, `dispatch-capability-publish`, `dispatch-capability-discover`, `dispatch-capability-read`

The dispatch tools are registered only when `DISPATCH_IDENTITIES` points at an identities file; without it 37 tools are promoted.

## Tool Groups

| Group | Tools | Key examples |
|-------|------:|--------------|
| **Identity** | 16 | `whoami`, `identity-derive-persona`, `identity-switch`, `identity-prove`, `nip05-lookup` |
| **Social** | 15 | `social-post`, `social-reply`, `social-feed`, `contacts-follow`, `social-notifications` |
| **Direct Messages** | 4 | `dm-send`, `dm-read`, `dm-conversation` |
| **Trust** | 22 | `trust-attest`, `trust-ring-prove`, `trust-spoken-challenge`, `trust-attest-chain` |
| **Dispatch** | 13 | `dispatch-send`, `dispatch-check`, `dispatch-reply`, `dispatch-capability-discover` |
| **Relay** | 13 | `relay-query`, `relay-set`, `relay-discover`, `cast-spell`, `relay-health` |
| **Moderation** | 16 | `label-create`, `list-mute`, `list-bookmark`, `list-followset-create`, `moderation-filter` |
| **Marketplace** | 16 | `marketplace-discover`, `marketplace-call`, `listing-create`, `listing-search` |
| **Safety** | 14 | `canary-session-create`, `canary-group-create`, `canary-duress-signal`, `safety-activate` |
| **Blossom** | 10 | `blossom-upload`, `blossom-mirror`, `blossom-verify`, `blossom-repair` |
| **Privacy** | 10 | `privacy-commit`, `privacy-prove-range`, `privacy-prove-age`, `privacy-publish-proof` |
| **Zap** | 9 | `zap-send`, `zap-balance`, `zap-make-invoice`, `zap-decode` |
| **Wallet service** | 5 | `wallet-grant`, `wallet-grants`, `wallet-revoke`, `wallet-refill`, `wallet-serve` |
| **Vault** | 9 | `vault-create`, `vault-encrypt`, `vault-share`, `vault-rotate` |
| **Workflow** | 7 | `trust-score`, `verify-person`, `identity-setup`, `relay-health`, `feed-discover` |
| **Signet** | 7 | `signet-badge`, `signet-vouch`, `signet-credentials`, `signet-challenge` |
| **Communities** | 5 | `community-create`, `community-feed`, `community-post`, `community-approve` |
| **Badges** | 4 | `badge-create`, `badge-award`, `badge-accept`, `badge-list` |
| **Groups (NIP-29)** | 20 | `group-inspect`, `group-invite-create`, `group-forum-comment`, `group-delete` |
| **Articles** | 3 | `article-publish`, `article-read`, `article-list` |
| **Calendar** | 3 | `calendar-create`, `calendar-read`, `calendar-rsvp` |
| **Wiki** | 3 | `wiki-publish`, `wiki-read`, `wiki-list` |
| **Search** | 3 | `search-notes`, `search-profiles`, `hashtag-feed` |
| **Scheduling** | 4 | `post-schedule`, `post-queue-list`, `post-queue-cancel`, `publish-event` |
| **Community NIPs** | 2 | `nip-publish`, `nip-read` |
| **Utility** | 23 | `decode`, `validate-event`, `verify-event`, `gift-wrap`, `gift-unwrap`, `kind-info`, `nip44-encrypt`, `tombstone` |
| **Sync (NIP-77)** | 1 | `sync-plan` (pull/push are explicit CLI and SDK operations) |
| **Handler** | 2 | `handler-publish`, `handler-discover` |
| **Catalog** | 2 | `search-actions`, `execute-action` |

Use `search-actions` to find tools by keyword, then `execute-action` to run them.

Protocol foundations: [semantic event validation](docs/event-validation.md),
[NIP-77 reconciliation](docs/sync.md), and [relay-scoped NIP-29 groups](docs/nip29-groups.md).

## Dispatch: AI-to-AI Collaboration

Dispatch lets AI agents collaborate over encrypted Nostr DMs. Any MCP-capable client can send structured tasks to other agents and receive results back.

**13 message types:** send, check, reply, ack, status, cancel, refuse, failure, query, propose, capability-publish, capability-discover, capability-read.

**NIP-89 capability discovery:** Agents publish what they can do. Other agents discover capabilities by topic, then route tasks to the right collaborator automatically.

```
dispatch-send("alice", "think", "Analyse the trade-offs of NIP-44 vs NIP-04")
dispatch-check()                    → inbox with pending tasks
dispatch-reply(taskId, result)      → send results back encrypted
```

All messages are NIP-44 encrypted. Recipients are resolved by name, NIP-05, npub, or hex.

## Identity Resolver

Every tool that accepts a recipient uses universal identity resolution. You never need to look up hex pubkeys manually.

Accepted formats:
- **Name** -- `"alice"` (resolved from your dispatch contacts)
- **NIP-05** -- `"alice@example.com"` (HTTP lookup)
- **npub** -- `"npub1abc..."` (NIP-19 decode)
- **Hex** -- `"a1b2c3..."` (64-character passthrough)

## Scheduled Posting

Sign events now, publish later. Events are signed immediately with your current key, then held in a queue until the scheduled time.

```
post-schedule("Good morning!", "2026-04-01T08:00:00Z")
post-queue-list()          → view pending scheduled posts
post-queue-cancel(id)      → cancel before it publishes
```

## NIP Coverage

nostr-bray implements or integrates the following NIPs:

| NIP | What |
|-----|------|
| **NIP-01** | Events, signing, relay protocol |
| **NIP-02** | Follow lists |
| **NIP-05** | DNS identity (lookup, verify, relay hints) |
| **NIP-09** | Event deletion |
| **NIP-11** | Relay information |
| **NIP-17** | Private DMs (gift wrap, default) |
| **NIP-19** | bech32 encoding (npub, nsec, nprofile, nevent, naddr) |
| **NIP-23** | Long-form articles (kind 30023) |
| **NIP-22** | Schema-correct comments for group forums |
| **NIP-29** | Relay-scoped groups, chat, forums, invitations and administration |
| **NIP-32** | Labels |
| **NIP-40** | Expiration tags |
| **NIP-42** | Relay auth |
| **NIP-44** | Encrypted payloads v2 |
| **NIP-45** | Event counts |
| **NIP-46** | Nostr Connect (bunker) |
| **NIP-47** | Nostr Wallet Connect: pay BOLT-11 invoices, balance, invoices, and scoped spending connections over one wallet. NIP-44 v2 only |
| **NIP-49** | Private key encryption (ncryptsec) |
| **NIP-50** | Search |
| **NIP-51** | Lists (mute, pin, follow sets, bookmarks) |
| **NIP-52** | Calendar events |
| **NIP-54** | Wiki pages |
| **NIP-57** | Zap receipts (kind 9735) are read. bray pays BOLT-11 invoices over NIP-47 but does not build kind 9734 zap requests or resolve LNURL, so it cannot yet zap a profile or note by itself |
| **NIP-58** | Badges |
| **NIP-65** | Relay list metadata |
| **NIP-72** | Communities |
| **NIP-77** | Negentropy ID reconciliation with truthful REQ fallback |
| **NIP-78** | Application-specific data |
| **NIP-85** | Trust rankings |
| **NIP-89** | Recommended applications (dispatch capability discovery) |
| **NIP-96** | HTTP file storage (Blossom) |
| **NIP-99** | Classified listings |
| **NIP-A7** | Spells (kind 777 — cast saved queries) |
| **NIP-VA** | Verifiable attestations (kind 31000) |

## Configuration

### Config file (recommended)

Create `~/.config/bray/config.json` (or `~/.nostr/bray.json`):

```json
{
  "bunkerUriFile": "/Users/you/.nostr/bunker-uri",
  "relays": ["wss://relay.damus.io", "wss://nos.lol"],
  "trustMode": "annotate"
}
```

Secrets are referenced by **file path** (`bunkerUriFile`, `secretKeyFile`, `nwcUriFile`) so they never appear in the config itself.

`trustMode` is `strict` (hide content from untrusted pubkeys), `annotate` (show trust scores) or `off` (no filtering). The default is `annotate`; an unrecognised value falls back to `annotate`. The `TRUST_MODE` environment variable overrides the config file.

Search order: `BRAY_CONFIG` env var > `$XDG_CONFIG_HOME/bray/config.json` > `~/.nostr/bray.json`.

### Environment variables

| Variable | Description |
|----------|-------------|
| `BRAY_CONFIG` | Path to config file |
| `BUNKER_URI` | NIP-46 bunker URL (safest) |
| `BUNKER_URI_FILE` | Path to bunker URI file |
| `NOSTR_SECRET_KEY` | nsec, hex, or BIP-39 mnemonic |
| `NOSTR_SECRET_KEY_FILE` | Path to secret key file |
| `NOSTR_NCRYPTSEC` | NIP-49 encrypted key |
| `NOSTR_NCRYPTSEC_PASSWORD` | Password for ncryptsec |
| `NWC_URI_FILE` | Path to a private `0600` file containing the NWC bearer URI |
| `BRAY_MAX_PAYMENT_MSAT` | bray's ceiling on any one payment, in msat (default `5000000`, 5,000 sats) |
| `BRAY_MAX_DAILY_MSAT` | bray's ceiling on spending in any rolling 24 hours, in msat (default `20000000`, 20,000 sats) |
| `BRAY_WALLET_SERVICE` | Set `1` to register `wallet-grant`, `wallet-refill` and `wallet-serve` |
| `DISPATCH_IDENTITIES` | Path to the dispatch identities markdown table (name and hex pubkey). The dispatch tools are registered only when this is set; `dispatchIdentities` in the config file does the same |
| `BRAY_HOME` | Directory for bray's state files (default `$XDG_CONFIG_HOME/bray`, else `~/.config/bray`) |
| `NOSTR_RELAYS` | Comma-separated relay URLs |
| `NOSTR_FORBID_PUBKEY` | Comma-separated npubs or hex this process must never sign as. See below. |
| `TOR_PROXY` | SOCKS5h proxy for Tor |
| `NIP04_ENABLED` | Set `1` to enable legacy NIP-04 DMs |
| `TRUST_MODE` | `strict`, `annotate` (default) or `off`. See the config file section above |
| `TRANSPORT` | `stdio` (default) or `http` |
| `PORT` | HTTP port (default 3000) |
| `BIND_ADDRESS` | HTTP bind address (default `127.0.0.1`) |
| `BRAY_HTTP_TOKEN` | Bearer token the HTTP transport requires in the `Authorization` header. If unset, bray generates a random token and prints it once on stderr; a token you supply is never echoed |

All secret env vars are deleted from `process.env` before parsing can fail.
Raw `NWC_URI` is refused; use `NWC_URI_FILE` or `wallet connect <nwc-file>` so
the bearer credential never appears in a process environment, command argument
or MCP tool argument. The wallet must speak NIP-44 v2 encryption for NWC;
wallets that only offer NIP-04 are refused.

### Keys this process must never be

An agent that comes up holding the wrong key is indistinguishable from one
working correctly. Every signature verifies, every tool succeeds, and the
only symptom is that `whoami` quietly answers with somebody else's npub —
which the driving model has no reason to doubt, because it is its own tool
telling it.

The worst version is a **principal's** key: a person's own. An agent signing
as its principal can attest that it belongs to itself, and approve its own
requests, because it *is* the principal those checks look for.

```bash
NOSTR_FORBID_PUBKEY=npub1yourownkey...,npub1anotherhuman...
```

or `forbidPubkeys` in the config file. Either takes npubs or hex. Activating
one of those keys throws instead — at startup, on `identity-switch`, and on
`bunker --persona` alike, because the check sits at the moment an identity
becomes active rather than at any one entry point. An entry that cannot be
parsed is an error too: a list nobody can read must not silently permit
everything.

The active npub is printed on stderr on every start, so the answer to "which
key is this?" does not depend on asking the agent.

## Spending limits

**The hard limit is the wallet's own.** Point `NWC_URI_FILE` (or
`wallet connect <file>`) at a connection your wallet issued with a spending
budget. Whatever bray does, and whatever a model asks of it, the wallet will
not pay past that budget. Everything below is bray policing itself, which is
worth having but is not the same thing.

On top of that, every payment bray makes (`zap-send`, `marketplace-pay`, the
CLI's `zap-send` and `wallet pay`, the SDK, and payments made through the
scoped connections below) is checked before anything is sent:

- **Per payment:** at most `BRAY_MAX_PAYMENT_MSAT` (default 5,000 sats).
- **Per day:** at most `BRAY_MAX_DAILY_MSAT` in any rolling 24 hours (default
  20,000 sats), counting a 1% (minimum 1 sat) fee reserve until the real fee
  is known. Attempts are written to `payment-ledger.json` in the state
  directory before the wallet is asked, so a restart does not hand the
  allowance back.
- **Once per invoice:** an invoice is never paid twice, and an attempt whose
  outcome is unknown is only retried after a lookup shows it failed.

`confirm: true` is set by the model, so it is not a human approval. When your
MCP client supports elicitation, `zap-send` and `marketplace-pay` also ask
you directly and pay only on an explicit yes; clients without elicitation
fall back to `confirm`, with the caps still applying. `zap-send` is not in
the default tool list either: it is reached through `search-actions`.

## Handing out a wallet connection

`zap-send` spends through the NWC URI you configured. That URI is an
unbounded capability over the wallet behind it: every method it supports, no
ceiling, until it is rotated. Handing one to an agent hands over everything.

`wallet-grant` issues scoped spending connections over that one wallet: one
wallet, one balance, and several narrower ways in. They are not separate
wallets. The tools that mint or widen spending authority (`wallet-grant`,
`wallet-refill`, `wallet-serve`) are registered only with
`BRAY_WALLET_SERVICE=1`; `wallet-grants` and `wallet-revoke` are always
available.

```
wallet-grant   { name: "research-agent", methods: ["get_info","pay_invoice"],
                 budgetMsat: 50000, maxPaymentMsat: 5000 }
wallet-grants  # what exists, what it may do, what it has spent
wallet-revoke  { nameOrId: "research-agent" }
wallet-refill  { nameOrId: "research-agent", budgetMsat: 50000 }
wallet-serve   { action: "start" }
```

`wallet-grant` writes the new connection's `nostr+walletconnect://` URI to a
`0600` file under `wallet-connections/` beside the grants file and returns
the path; the URI itself never appears in a tool result.

What a connection may do is an allowlist, and the default grants no spending
and does not disclose anything: `get_info` and `make_invoice`. The others are
opt-in per connection, and **a connection that can spend must carry a
budget** - there is no unlimited grant to issue by accident. A connection
sees only itself:

- `get_balance` reports the connection's remaining budget, never the
  wallet's balance.
- `lookup_invoice` answers only for invoices that connection issued or paid;
  anything else is reported as not found.

The rules exist because a payment cannot be recalled:

- A request is answered **once**. Its id is persisted *before* the payment is
  attempted, so a process that dies mid-payment comes back knowing not to try
  again - a relay will hand the same signed request over twice.
- Requests on one connection are **serialised**, so two arriving together
  cannot both read the same remaining budget.
- A request older than five minutes is not answered, whatever its own
  `expiration` tag claims.
- Each connection has **its own service key**: two grants share nothing a
  relay can correlate, and revoking one is deleting a key.
- The budget is charged what the **invoice** says, decoded here, plus the
  routing fee: a fee reserve is held until the wallet reports the real fee.
  Invoices that state no amount are refused. A budget checked against a
  figure the payer supplied is not a budget.
- A definite refusal from the wallet (insufficient balance, say) gives the
  budget back, and the connection is not told why the wallet refused.
- bray's own per-payment and daily caps apply to these payments as well.
- A claimed payment whose preimage does not settle the invoice is refused
  rather than passed on. Repeating an unproven claim would make this service
  the one telling the lie.

Grants live in `wallet-grants.json` (0600, per identity), and they are
answered **only while `wallet-serve` is running** - which is to say, only for
as long as this process is alive. That is worth telling whoever you hand a URI
to: a connection that works while an MCP session is open is a different
promise from one that works overnight.

The file is the record, shared by every bray process on the machine. Only one
process may serve the grants at a time, the serving process re-reads a grant
before every request, and every change is a locked update of the file, so a
revocation or refill made from any process applies to the next request and
cannot be written away by another.

## CLI

```bash
npx nostr-bray whoami                    # show your npub
npx nostr-bray post "hello from bray!"   # publish a note
npx nostr-bray persona work              # derive a work persona
npx nostr-bray prove blind               # create a linkage proof
npx nostr-bray --help                    # see all commands
```

## Use as a library

The package is also a TypeScript SDK (ESM only). `nostr-bray/sdk` is the factory API:

```ts
import { createBray } from "nostr-bray/sdk"

const bray = await createBray({
  sec: process.env.NOSTR_SECRET_KEY, // or bunkerUri: "bunker://..."
  relays: ["wss://relay.damus.io", "wss://nos.lol"],
})

await bray.post("gm nostr")
console.log(bray.npub)
bray.destroy() // zeroise key material
```

`defaultBray()` builds the same client from the environment variables above. The handlers behind each tool group are exported as subpaths, so you can import one group without the rest:

| Import | What it gives you |
|--------|-------------------|
| `nostr-bray` | `createBray`, `defaultBray` and the handlers of every group below, re-exported |
| `nostr-bray/sdk` | `createBray` and `defaultBray`, the `BrayClient` factory API |
| `nostr-bray/types` | Type-only exports of the public config and result types |
| `nostr-bray/identity` | Key derivation, personas, linkage proofs, Shamir backup, migration, NIP-05 |
| `nostr-bray/social` | Posts, DMs, feeds, blossom, groups, articles, badges, calendar, communities, wiki, scheduling |
| `nostr-bray/trust` | Attestations, ring signatures and spoken tokens |
| `nostr-bray/relay` | Relay lists, queries, counts, intelligence, outbox publishing, spells, NIP-42 auth, relay HTTP calls |
| `nostr-bray/zap` | NWC payments, NWC file loading and the payment guard |
| `nostr-bray/safety` | Duress personas and CANARY sessions, groups and beacons |
| `nostr-bray/event` | Generic event building and publishing, NIP-13 proof of work, NIP-59 gift wrap and unwrap |
| `nostr-bray/event-validation` | Semantic event validation against the kind registry |
| `nostr-bray/util` | Decode and encode, NIP-44, ncryptsec, filters, NIP browsing |
| `nostr-bray/workflow` | Composite flows such as trust scoring, person verification and relay health |
| `nostr-bray/dispatch` | Dispatch protocol messages, capabilities and identities |
| `nostr-bray/marketplace` | L402 and x402 discovery, payment, calls and listings |
| `nostr-bray/privacy` | Commitments and zero-knowledge range, age and threshold proofs |
| `nostr-bray/moderation` | Labels, mute lists, pin lists, follow sets, bookmarks |
| `nostr-bray/signet` | Signet badges, credentials, policy and challenges |
| `nostr-bray/vault` | Dominion epoch-based encrypted vaults |
| `nostr-bray/handler` | Publish and discover MCP-capable handlers (kind 31990) |
| `nostr-bray/musig2` | BIP-327 MuSig2 key, nonce, partial-sign and aggregate primitives |
| `nostr-bray/sync` | NIP-77 reconciliation: plan, pull and push |
| `nostr-bray/admin` | NIP-86 relay management API calls |

## Documentation

- **[Usage Guide](./docs/guide.md)** -- walkthroughs for identity, DMs, attestations, payments, and duress
- **[Examples](./examples/)** -- MCP config files and CLI workflow scripts
- **[Contributing](./CONTRIBUTING.md)** -- setup, architecture, testing, and conventions

## For AI Assistants

See [llms.txt](./llms.txt) for a concise summary optimised for AI context windows, or [llms-full.txt](./llms-full.txt) for complete tool documentation with parameter details.

## Part of the ForgeSworn Toolkit

[ForgeSworn](https://forgesworn.dev) builds open-source cryptographic identity, payments, and coordination tools for Nostr.

| Library | What it does |
|---------|-------------|
| [nsec-tree](https://github.com/forgesworn/nsec-tree) | Deterministic sub-identity derivation |
| [ring-sig](https://github.com/forgesworn/ring-sig) | SAG/LSAG ring signatures on secp256k1 |
| [range-proof](https://github.com/forgesworn/range-proof) | Pedersen commitment range proofs |
| [canary-kit](https://github.com/forgesworn/canary-kit) | Coercion-resistant spoken verification |
| [spoken-token](https://github.com/forgesworn/spoken-token) | Human-speakable verification tokens |
| [toll-booth](https://github.com/forgesworn/toll-booth) | L402 payment middleware |
| [geohash-kit](https://github.com/forgesworn/geohash-kit) | Geohash toolkit with polygon coverage |
| [nostr-attestations](https://github.com/forgesworn/nostr-attestations) | NIP-VA verifiable attestations |
| [dominion](https://github.com/forgesworn/dominion) | Epoch-based encrypted access control |
| [nostr-veil](https://github.com/forgesworn/nostr-veil) | Privacy-preserving Web of Trust |

## Support

For issues and feature requests, see [GitHub Issues](https://github.com/forgesworn/bray/issues).

If bray is useful to you, a tip is always welcome:

- Lightning: `profusemeat89@walletofsatoshi.com`
- Nostr zaps: `npub1mgvlrnf5hm9yf0n5mf9nqmvarhvxkc6remu5ec3vf8r0txqkuk7su0e7q2`

## Licence

MIT