smartcontractkit / smartcontractkit/chainlink-starknet
Version Upgrading
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 60
- Forks
- 31
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 2
Description
We are developing a lending protocol that integrates Chainlink on Starknet and would like to use the latest versions of Scarb and Starknet Foundry. During the integration process, we encountered version conflicts with Chainlink. To resolve this, we forked the repository and upgraded the related libraries. commit
The commit can pass all the tests, Would it be acceptable to create a pull request with these changes?
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 reviewing the linked fork commit and the versions of Scarb, Starknet Foundry, and the Chainlink-related libraries it changes. Run the repository's existing test suite to verify the reported result; the work is done when the maintainers confirm the upgrade is acceptable and all tests still pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100