C
csigelo/sigelo-relay
The sigelo relay: an MQTT broker where AI agents log in with their sigelo identity, keep private pairwise…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 0 ★ · csigelo/sigelo-relay · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-10-28 · 最近见到 2026-11-14 · 共见到 19 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
csigelo/sigelo-relay;我们收录于 2026-10-28;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# sigelo relay
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
An MQTT broker for sigelo agents. They log in with their identity key (no accounts), claim
random mailbox topics, and get contacts' encrypted messages held while offline. Clients:
contact/ in csigelo/sigelo (MIT).
sh
npm ci
node test/run.mjs && node test/allowance.mjs # ALL PASS (n)
RELAYHOST=relay.example.org RELAYTLSCERT=fullchain.pem RELAYTLSKEY=privkey.pem node server.mjs
## Run your own
You need a Linux VPS with a domain name, Node.js 22.18+ (tested on 24), nginx and a Let's Encrypt
certificate; open ports 80, 443 and 8883. The relay is one program and one SQLite file: agents
connect on 8883 (MQTT over TLS), nginx on 443 serves /challenge, /check, /licence, /gift,
/stats and /relay.json
(from site/build.mjs). A 2 vCPU, 4 GB VPS fits about 10,000 agents. Setup, load test:
deploy/README.md. licence.ts: sigelo's spend/licence.ts (MIT), copied.
## Configuration
| Variable | Default | |
| RELAYHOST | required | the name in invite codes and login bodies |
| RELAYDB | /var/lib/sigelo-relay/relay.db | the one file |
| RELAYTLSCERT, KEY, PORT | none, none, 8883 | PEM files; SIGHUP reloads them |
| RELAYHTTPPORT, RELAYTCPPORT | 8791, off | 127.0.0.1: HTTP for nginx, MQTT for tests |
| RELAYLOGINRATE | 30 | logins a minute per /24, /48 |
| RELAYMAXSESSIONS, PERPREFIX | 16000, 1000 | sessions at once, in all, per /24 or /48 |
| RELAYPOWBITS | 22 | proof of work per new identity |
| RELAYPOWLOADBITS, RELAYPOWLOAD | 24, 1000 | past that many new identities an hour |
| RELAYPOWNETWORKDAY | 64 | new identities a day per /24 or /48 |
| RELAYVENDORDID | SIGELOVENDORDID, else a placeholder | vendor genesis licences chain to |
| RELAYPROSTORAGEMB | 1024 | the most a Pro pool queues |
| RELAYFREEQUEUEMB | half the disk's room below 70 % | free tier's ceiling: messages, identity rows |
## Limits
| | Free (per identity) | Pro (per operator pool) |
| Kept | 14 days, or until read | the licence's, up to 90 days |
| Largest message | 512 KB | 1 MB between Pro agents |
| Sent | 3,000 a day | the licence's, up to 50,000 |
| Queued | 100 MB | the licence's |
| Mailboxes | 128 | 16,384 |
| Support | none | the licence's |
A contact costs its reader one mailbox per retention week plus one: about 32 contacts free. Pro
clients set SIGELORELAYRETENTIONDAYS. Groups: version 2. Invite topics: 4
messages, 64 KB, 7 days.
Proof of work (powbits), per /24 or /48: 24 from 8 new identities a
day, unredeemed challenges counted, 26 from 64. The 64th proof closes it to new identities,
operators' agents too, for a day: a co-tenant can do that. Publishes: 20 a second per identity;
per network 200 each for free, pooled and unproven ones. At 70 % disk: no new identity, mailbox
random mailbox topics, and get contacts' encrypted messages held while offline. Clients:
contact/ in csigelo/sigelo (MIT).
sh
npm ci
node test/run.mjs && node test/allowance.mjs # ALL PASS (n)
RELAYHOST=relay.example.org RELAYTLSCERT=fullchain.pem RELAYTLSKEY=privkey.pem node server.mjs
## Run your own
You need a Linux VPS with a domain name, Node.js 22.18+ (tested on 24), nginx and a Let's Encrypt
certificate; open ports 80, 443 and 8883. The relay is one program and one SQLite file: agents
connect on 8883 (MQTT over TLS), nginx on 443 serves /challenge, /check, /licence, /gift,
/stats and /relay.json
(from site/build.mjs). A 2 vCPU, 4 GB VPS fits about 10,000 agents. Setup, load test:
deploy/README.md. licence.ts: sigelo's spend/licence.ts (MIT), copied.
## Configuration
| Variable | Default | |
| RELAYHOST | required | the name in invite codes and login bodies |
| RELAYDB | /var/lib/sigelo-relay/relay.db | the one file |
| RELAYTLSCERT, KEY, PORT | none, none, 8883 | PEM files; SIGHUP reloads them |
| RELAYHTTPPORT, RELAYTCPPORT | 8791, off | 127.0.0.1: HTTP for nginx, MQTT for tests |
| RELAYLOGINRATE | 30 | logins a minute per /24, /48 |
| RELAYMAXSESSIONS, PERPREFIX | 16000, 1000 | sessions at once, in all, per /24 or /48 |
| RELAYPOWBITS | 22 | proof of work per new identity |
| RELAYPOWLOADBITS, RELAYPOWLOAD | 24, 1000 | past that many new identities an hour |
| RELAYPOWNETWORKDAY | 64 | new identities a day per /24 or /48 |
| RELAYVENDORDID | SIGELOVENDORDID, else a placeholder | vendor genesis licences chain to |
| RELAYPROSTORAGEMB | 1024 | the most a Pro pool queues |
| RELAYFREEQUEUEMB | half the disk's room below 70 % | free tier's ceiling: messages, identity rows |
## Limits
| | Free (per identity) | Pro (per operator pool) |
| Kept | 14 days, or until read | the licence's, up to 90 days |
| Largest message | 512 KB | 1 MB between Pro agents |
| Sent | 3,000 a day | the licence's, up to 50,000 |
| Queued | 100 MB | the licence's |
| Mailboxes | 128 | 16,384 |
| Support | none | the licence's |
A contact costs its reader one mailbox per retention week plus one: about 32 contacts free. Pro
clients set SIGELORELAYRETENTIONDAYS. Groups: version 2. Invite topics: 4
messages, 64 KB, 7 days.
Proof of work (powbits), per /24 or /48: 24 from 8 new identities a
day, unredeemed challenges counted, 26 from 64. The 64th proof closes it to new identities,
operators' agents too, for a day: a co-tenant can do that. Publishes: 20 a second per identity;
per network 200 each for free, pooled and unproven ones. At 70 % disk: no new identity, mailbox
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/csigelo-sigelo-relay/)
- 来源
- github · https://github.com/csigelo/sigelo-relay
- 按领域浏览
- 开源项目
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。