smartcontractkit / smartcontractkit/chainlink-cosmos
Terra code IDs should not be hardcoded in Gauntlet
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This data should be input into Gauntlet fetched from an external source (RDD), similar to Solana program IDs.
Why are these hardcoded here instead declared at codeIDs/{network}.json file?
Seems inconsistent with:
- packages-ts/gauntlet-terra-contracts/codeIds/bombay-testnet.json
- packages-ts/gauntlet-terra-contracts/codeIds/mainnet.json
Originally posted by @krebernisak in https://github.com/smartcontractkit/chainlink-terra/pull/19#discussion_r781090437
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 by comparing packages-ts/gauntlet-terra-contracts/codeIds/bombay-testnet.json and codeIds/mainnet.json with the Terra code IDs currently hardcoded in Gauntlet. Trace how Solana program IDs are fetched from the external RDD source, then determine the corresponding Terra entry point. Done means Terra IDs come from the external source consistently rather than duplicated hardcoded values.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100