OpenZeppelin / OpenZeppelin/compact-tools
dev: bound proving and balanceTx in the fragmented deploy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 31
Description
`txTimeoutMs` in `packages/deployer` covers finalization, indexer catch-up, and the dust settle, but proving and `balanceTx` inside `submitTxAsync` (`services/deploy-tx.ts` `submitClassified`, and the insert path in `deployer.ts`) run with no ceiling.
A hung proof server stalls the run silently between the halving log lines. The halving loop re-proves on every retry, so its worst case is unbounded too.
Race the submit against its own timeout and surface it as a distinct failure, so the operator sees "proof server not responding" instead of a silent hang. Noted as a follow-up in #174.
Contributor guide
No contributing guide indexed for this repository
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 in packages/deployer and trace txTimeoutMs through services/deploy-tx.ts, especially submitClassified, then inspect the insert path in deployer.ts and submitTxAsync. Confirm how proving and balanceTx behave during halving retries. Done means both paths have a bounded timeout and expose a distinct proof-server timeout failure instead of hanging silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100