If verify_events is set in the configuration, chorus rejects invalid events in all cases.
If an event has a '-' tag, it must be submitted by an AUTHed user that matches the pubkey of the event, else it is rejected.
If open_relay is true, all other events are accepted. If false, the remaining rules apply.
Chorus accepts all events submitted by AUTHed authorized users.
Chorus accepts relay list metadata (kind 10002) from anybody.
Chorus accepts all ephemeral events from anybody.
Chorus accepts all events authored by an authorized user, irrespective of who submits it. Chorus always verifies such events irrespective of the verify_events configuration setting.
Chorus accepts all events that tag one of the authorized users.
If you wish to change these rules, change the source code at nostr.rs:screen_incoming_event()
Chorus does not serve any DM (kind 4) or GiftWrap (kind 1059) unless the connection is AUTHed and the user matches either a tagged person or the author of the event.
If open_relay is true, all other events are served. If false, the remaining rules apply.
Chorus serves all relay list metadata (kind 10002) events queried.
Chorus serves all ephemeral events.
Chorus serves all events to AUTHed authorized users.
Chorus serves all events which were authored by an authorized user.
Filters which are broad are considered scrapers and are not serviced. Scraping is any filter where all of the following are true:
idsis missing or emptyauthorsis missing or empty- There are no
#Xtag filters
If you wish to change these rules, change the source code at nostr.rs:screen_outgoing_event()
WebSocket frames and messages are limited to 1 MB (slightly less for messages due to some overhead).
Each connection has a memory buffer used for JSON deserialization that is no larger than the WebSocket message. No more than one such buffer exists per connection, and memory allocation is generally tightly controlled.
Every connection is IP banned for 2 seconds after disconnection, whether or not the connection was well behaved. We don't think clients should ever reconnect immediately. If chorus is run directly (not behind an nginx proxy), this IP banning is more efficient because it happens prior to SSL setup.
A maximum of 32 subscriptions are allowed by default (per connection), although this is
configurable with the max_subscriptions configuration setting.
Chorus fully complies with NIP-01
Chorus fully complies with NIP-04
The chorus relay does not supply kind 4 DMs to anybody except the tagged recipient and the author.
REQs for such disallowed events do not generate any error condition, but the events are not supplied.
Chorus fully compiles with NIP-09.
Chorus both deletes matching events (matched by id and pubkey) as well as remembering these (id,pubkey) pairs to reject such events subsequently submitted.
Chorus fully complies with NIP-11.
Chorus does not support NIP-26.
Chorus does not support NIP-28.
Chorus does not support NIP-40.
Chorus fully complies with NIP-42.
Chorus immediately sends an AUTH to every client as soon as the connection is setup.
Chorus continues to serve clients irrespective of whether they have AUTHed or not.
Chorus does not support NIP-45.
Chorus does not support NIP-50.
The chorus relay does not supply kind 1059 GiftWraps to anybody except the tagged recipient and the author.
REQs for such disallowed events do not generate any error condition, but the events are not supplied.
Chorus fully compiles with NIP-65.
Chorus accepts kind 10002 events from anybody, and serves such events to anybody.
Chorus does not support NIP-94.
Chorus does not support NIP-96.