Q: How do multiple filters with limits combine in a Nostr REQ query?

Each filter gets its own subquery with its own ORDER BY and LIMIT, then branches are combined with SQL UNION for dedup. There is no global limit, so three filters with limits 10, 20, and 30 can return up to 60 events.

Q: Does the Quartz event store support NIP-01 id prefix matching?

No, ids and authors are exact-match only against the full 64-character hex values. Shorter prefixes are logged as errors by the Filter constructor but still sent, and they simply never match anything.

Q: Why does my event store return same-timestamp events in a different order?

The id ASC tiebreak on equal created_at only applies when useAndIndexIdOnOrderBy is true, which is off in both the client default and geode relay preset. Same-second ordering is otherwise unspecified, so any newest-N result is valid.

Q: What happens when a NIP-09 deletion targets another deletion event?

A kind-5 can delete another kind-5, which removes its tombstone rows and makes previously deleted events re-insertable. This is a documented known quirk; some external implementations deliberately diverge by treating deletion-of-a-deletion as a no-op.

Question 1

How do I implement a Nostr event store that matches Quartz behavior?

Accepted Answer

Treat the SQLite EventStore in nip01Core/store/sqlite as the reference implementation and follow the numbered rules in this contract. Assert parity with the commonTest suites, using FsParityTest as the in-repo pattern for holding a second engine to the same semantics.

Question 2

Are since and until filters inclusive in Nostr event store queries?

Accepted Answer

Yes, both are inclusive in the Quartz SQLite store: since compiles to created_at >= and until to created_at <=. An event whose created_at equals both bounds still matches the filter.

Question 3

How do multiple filters with limits combine in a Nostr REQ query?

Accepted Answer

Each filter gets its own subquery with its own ORDER BY and LIMIT, then branches are combined with SQL UNION for dedup. There is no global limit, so three filters with limits 10, 20, and 30 can return up to 60 events.

Question 4

Does the Quartz event store support NIP-01 id prefix matching?

Accepted Answer

No, ids and authors are exact-match only against the full 64-character hex values. Shorter prefixes are logged as errors by the Filter constructor but still sent, and they simply never match anything.

Question 5

Why does my event store return same-timestamp events in a different order?

Accepted Answer

The id ASC tiebreak on equal created_at only applies when useAndIndexIdOnOrderBy is true, which is off in both the client default and geode relay preset. Same-second ordering is otherwise unspecified, so any newest-N result is valid.

Question 6

What happens when a NIP-09 deletion targets another deletion event?

Accepted Answer

A kind-5 can delete another kind-5, which removes its tombstone rows and makes previously deleted events re-insertable. This is a documented known quirk; some external implementations deliberately diverge by treating deletion-of-a-deletion as a no-op.

event-store-semantics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Core Features & Use Cases

Quick Start

Frequently Asked Questions about event-store-semantics

Related Skills

nostr

update-web-assets

nostr-relay-builder

test-helper