useCurrentBlockTimestamp should return a number
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
(1) useCurrentBlockTimestamp should be a number and (2) it might be the same as useBlockNumber
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 by locating the implementation and usages of useCurrentBlockTimestamp, then compare it with useBlockNumber. Determine whether the timestamp should be numeric and whether the two hooks are intended to share behavior. Done means the return type and relationship between the hooks are clarified and the affected behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100