Area
frontend/src/circuits/, frontend/public/circuits/
Problem
The frontend embeds compiled circuit artifacts (frontend/src/circuits/*.json / frontend/public/circuits/*.json) for client-side proving. These are typically large, and there's no documented bundle-size analysis or lazy-loading strategy — a large initial payload directly hurts "Consumer-Grade UX" on slower connections.
Proposed change
Run @next/bundle-analyzer (or similar) against a production build, document current sizes, and lazy-load circuit artifacts per-page (deposit only needs shielded_pool.json, compliance only needs compliance.json/disclosure.json) instead of bundling all of them globally if that isn't already the case.
Acceptance Criteria
Open your PR against the dev branch, not main. All active development merges into dev.
Discuss this issue / coordinate work: join the DShield contributor Telegram group: https://t.me/+SiGHH24No9U2MDJk
Area
frontend/src/circuits/, frontend/public/circuits/
Problem
The frontend embeds compiled circuit artifacts (
frontend/src/circuits/*.json/frontend/public/circuits/*.json) for client-side proving. These are typically large, and there's no documented bundle-size analysis or lazy-loading strategy — a large initial payload directly hurts "Consumer-Grade UX" on slower connections.Proposed change
Run
@next/bundle-analyzer(or similar) against a production build, document current sizes, and lazy-load circuit artifacts per-page (deposit only needsshielded_pool.json, compliance only needscompliance.json/disclosure.json) instead of bundling all of them globally if that isn't already the case.Acceptance Criteria
just test,pnpm test,cargo test, ornargo testas applicable) pass locally and in CIOpen your PR against the
devbranch, notmain. All active development merges intodev.Discuss this issue / coordinate work: join the DShield contributor Telegram group: https://t.me/+SiGHH24No9U2MDJk