OpenZeppelin / OpenZeppelin/guardian
Deployment & Scaling
Open
Nobody has claimed this yet.
cla: allowlist
tracking
- Dominant language
- Rust
- Stars
- 10
- Forks
- 20
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 43
Description
Tracking issue for Guardian deployment infrastructure and horizontal scaling — everything needed to ship, run, and scale Guardian instances reliably.
Parent: META - Guardian Management (#248)
Related issues
- #317 — Define and reach Guardian scalability target: 100k guarded accounts, 100 concurrent transacting users, 20k concurrent state readers
- #242 — Ensure horizontal scaling works correctly across multiple Guardian instances
- #240 — Build and publish multi-platform Docker images (ARM64 + x86_64)
- #235 — Prebuild and publish Docker image with each release
- #190 — Decouple Guardian canonicalization from API instances
- #243 — Establish in-repo documentation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the remaining unchecked related issue, #317, and review the completed issues #242, #240, #235, #190, and #243 for the existing deployment and scaling context. Done means defining and reaching the stated target of 100k guarded accounts, 100 concurrent transacting users, and 20k concurrent state readers; this tracking issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100