`useProofSubmit` creates full submission state tree at HomeScreen level unnecessarily

[cybermax4200]

Why this matters now: HomeScreen.tsx:52 calls useProofSubmit(), which instantiates isSubmitting, progress, error, pendingCount, and the full submit/syncPendingProofs callback tree. HomeScreen only uses pendingCount, isSubmitting (for the sync banner), and syncPendingProofs. The submit function, progress, and error state are wasted allocations on the most-rendered screen in the app.

Problem / What: src/screens/HomeScreen.tsx:52 — const { pendingCount, isSubmitting, syncPendingProofs } = useProofSubmit() — but useProofSubmit() creates useState for isSubmitting, progress, error, pendingCount on every mount, plus two useCallback wrappers.

Key Challenges:

• Split useProofSubmit into two hooks: usePendingProofs() (returns pendingCount, isSyncing, syncPendingProofs) and useProofSubmit() (returns submit, progress, error, isSubmitting).
• usePendingProofs only manages the queue count and sync; useProofSubmit manages the full submission flow.
• HomeScreen uses usePendingProofs; SubmitProofScreen uses useProofSubmit.
• Both hooks share the same proofQueue module but don't share React state.
• The split must not break the proofSyncStore interaction.

Acceptance Criteria:

• HomeScreen only instantiates pending-proof state, not full submission state.
• SubmitProofScreen uses the full useProofSubmit hook.
• No behavioral change — proof submission, queuing, and sync work identically.
• HomeScreen renders fewer state updates when proof state changes.
• Tests for both hooks independently.

Relevant files/functions:

• src/hooks/useProofSubmit.ts (split into two hooks)
• src/screens/HomeScreen.tsx:52
• src/screens/SubmitProofScreen.tsx:42
• src/__tests__/ (new tests for split hooks)

Out of scope: Global proof state management via Zustand (future optimization).

Labels: architecture, intermediate, performance

[Timothy2025-20]

Hi maintainer, I’m particularly interested in tackling this issue as it aligns well with my experience.

A bit about myself, I have 4 years of experience building production-grade software, so I’m comfortable with strict testing, CI pipelines, and writing clean, documented code. And i will like to resolve this issue if assigned

Thank you and Looking forward to collaborating

[grantfox-oss]

🦊 GrantFox — @Timothy2025-20 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #56)
2. Your PR will be reviewed by the ecotask-network maintainers

Good luck! Track your progress on GrantFox.

[Timothy2025-20]

@cybermax4200 PR #76 is ready for review: #76