Every kind that matters
The events blaster republishes whatever your client signs and sends to wss://blaastr.com, including:
- Kind 0 profile metadata, so your name, picture and NIP-05 show up everywhere
- Kind 1 notes and replies, kind 6 reposts and kind 7 reactions
- Kind 3 follow lists and kind 10002 relay lists, so other clients can find you
- Kind 30023 long-form articles and other addressable events
- Zap receipts, lists, badges and app-specific kinds
What isn't blasted
Ephemeral events (kinds 20000–29999, such as NWC requests and relay AUTH) are never broadcast, and the same event id is only sent once every 30 days. Events can be up to 1 MB, though many relays set lower limits of their own.
Blast events from code
POST a signed event to https://blaastr.com/api/event, or up to 50 at once to /api/events, and get the same OK message a relay would send. No API key: the signature identifies the author. Add ?publish_at= to schedule it for later.
See where each event landed
Log in with a NIP-07 extension or NIP-46 signer to see, for every event from the last 7 days, which relays accepted it, which rejected it and why, and which never answered. Reblast an event to the relays that missed it with one click, or get a signed webhook when each broadcast settles.
Questions
Can I blast events signed by someone else?
Anyone may submit an event, but it is only broadcast if its author has an active subscription. That makes it safe to relay events for your users from an app.
How fast are events blasted?
The relay answers OK as soon as the event is queued, and publishing to relays usually finishes within seconds.
Are there limits?
Per pubkey there is a per-minute rate limit and a daily cap on events plus reblasts. Normal posting never comes close; the limits are listed in the docs.
Ready? Subscribe your npub, read the docs or browse the live relay list.