smartcontractkit / smartcontractkit/chainlink
Tipcap calculation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Hi,
I'm trying to develop various trading strategies, and a crucial element of this strategy is predicting the commission parameters that the oracle pays when creating a transaction to update prices on the Base network. The key parameter here is tipCap.
Based on the source code of block_history_estimator.go, tipCap is calculated as the value that is greater than X% of transactions over Y blocks. This rule works in about 50% of cases, but for example, for block 25961829, it doesn't seem to work—the actual value is slightly lower than what my algorithm predicts.
Could you please advise what other factors might influence this calculation?
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 with block_history_estimator.go and trace how tipCap is derived from transactions across the configured block range. Compare the calculation with the reported Base block 25961829 and identify which inputs or conditions account for the difference. Done means documenting the influencing factors or confirming a reproducible calculation defect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100