oasisprotocol / oasisprotocol/oasis-core
beacon: Make obtaining historical epoch transition points less painful
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Due to the beacon being the driver of timekeeping, obtaining the height at which a given past epoch transition occurred requires going back through history. While what exists now will function, it is slow, especially if the epoch is far in the past.
This could/should be improved somehow, if we believe such queries will be common.
Note: People already shouldn't be running nodes where arbitrary users can spam queries.
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 beacon code that resolves historical epoch transition heights and measure queries for epochs far in the past. The issue does not identify files, tests, or a specific design; done would require an agreed improvement that makes these lookups substantially faster without enabling arbitrary-user query abuse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100