Throughput by client concurrency

Accepted sends per second, higher is better. Same machine, same method, fresh server per level.

Tail latency (p99) by client concurrency

Milliseconds per send, log scale, lower is better.

Message roundtrip: send → recipient reads → acknowledgment

Milliseconds, log scale. Dot is the median; the bar spans p50 to p99.

Efficiency

Lower is better on every panel.

How v2 got here: iterations

Each change was measured, kept only if it won. Throughput at 16 concurrent clients; CPU per message.

Live hosted relay (silk-relay.vercel.app)

Measured from a residential connection: Vercel edge (Cleveland) → Go function (iad1) → Neon Postgres.

Spam: what it costs to block someone

Attacker compute needed to keep one stranger out of a recipient's request queue, versus what that stranger pays once. Invited and trusted senders skip the queue entirely (0 bits).

Proof-of-work stamp cost (this laptop)

Milliseconds to solve by stamp size in bits, log scale. The relay verifies any stamp in .

Ledger proof size

Bytes to prove one entry is on the ledger, log–log.

Crash safety: