Stable List Traversal in GraphQL: Adopting Relay Cursor Connections
Offset pagination skips items and slows deep pages. Learn how Relay Connections use opaque cursors and deterministic ordering for stable GraphQL list traversal.
Loading…
ReadMeFeed / Community knowledge
#relay
Real questions. Useful conversations. Find the people who know your stack.
Reducing Noise in Waku Relay v2 with Content‑Addressed Deduplication
Learn how Waku Relay v2 uses SHA‑256 hashes and a Bloom filter to drop duplicate messages, saving bandwidth while preserving privacy guarantees that make Waku suitable for decentralized messaging.
wakuDeploying a Waku Relay Node with Store for Offline Message Delivery
Run a Waku Relay node with the Store plugin and verify that offline subscribers receive missed messages after reconnection.
dockerUsing Waku Relay’s Store‑and‑Forward to Retrieve Missed Messages
Learn how to configure a Waku Relay’s store‑and‑forward feature so light clients can query recent messages after going offline, with a step‑by‑step example and notes on trade‑offs.
Designing Cursor Pagination in GraphQL: Trust Boundaries, Sort Contracts, and Failure Modes
Cursor pagination in GraphQL only works if you treat cursors as untrusted input, commit to an immutable sort contract, and monitor the specific ways keyset pagination fails.
graphqlConfigure Waku Relay for Store‑and‑Forward Messaging
Learn how to enable Waku Relay’s store‑and‑forward feature so offline subscribers receive messages after they reconnect.
Using Waku Relay with Lightpush for Bandwidth‑Efficient Message Delivery in Mobile dApps
Learn how to enable Waku Relay’s Lightpush feature to reduce bandwidth for intermittent mobile dApp clients, with a working Node.js example, limits, and pitfalls.
Dial timeout due to private IP advertisement in Waku Relay
Dial timeout due to private IP advertisement in Waku Relay When a Waku Relay node is started with the default bootstrap list and no explicit public address, it successfully discovers peers via mDNS in a local test environment but, in a production deployment, logs show a dial timeout or missing address error because the node continues to advertise only privat