smartcontractkit / smartcontractkit/chainlink-solana
registerContracts in gauntlet-solana should not depend on Environment
Open
Nobody has claimed this yet.
gauntlet
- Dominant language
- Go
- Stars
- 92
- Forks
- 68
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 28
Description
This function has still some issues, essentially:
- Depends on an static path to read artifacts. (What if those artifacts are not in the FS?)
- Depends on the environment to load the program Ids. (What if some
gauntlet-solanaconsumer chooses another way to store their ProgramIds? We would be forcing them to include it into the env)
Originally posted by @RodrigoAD in https://github.com/smartcontractkit/chainlink-solana/pull/284#discussion_r845033360
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 at the registerContracts implementation in gauntlet-solana and trace how it reads artifacts and program IDs. Done means registration no longer requires a static filesystem artifact path or Environment-provided program IDs, while preserving the function's existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100