paritytech / paritytech/jamtart

jip-3-spammer: validate jam-tart stability and ingestion pipeline

Open
#22 0 comments 0 reactions 1 assignee View on GitHub

@michalkucharczyk is already working on this.

Since Jul 17, 2026.

Dominant language
Rust
Stars
18
Forks
3
Avg merge
3d 15h
Merged PRs (30d)
3

Description

Run the spammer to generate high-volume synthetic JIP-3 events and stress-test jam-tart itself.

Tool: https://github.com/michalkucharczyk/jip-3-spammer

Note: the tool probably needs an update to PROTOCOL_VERSION=1 (equivalent of https://github.com/paritytech/jamtart/pull/15/commits/a34ab6d0946a3b2961acee14035b31d1b77f8448).

Goal

jam-tart is stable and production-ready for Toaster: it handles 1024 validator connections and runs continuously for 24h+ under full load.

Verify
  • 1024 concurrent connections
  • Sustained event throughput
  • DB writes keep up
  • WebSocket fanout
  • No crashes, memory leaks, or bottlenecks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.