argumentcomputer / argumentcomputer/zk-light-clients
Network ID needs to be dynamic
- Dominant language
- Rust
- Stars
- 70
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/argumentcomputer/zk-light-clients/blob/93530ebedc1385e2c8fb0f82771673e199c60e6b/kadena/light-client/src/client/chainweb.rs#L240
There are multiple references to chainweb node in this file. Instead of using mainnet01 we need to supply this as an input during run time. For example we may need to run on devnet or testnet01.
One example where mainnet01 is hard coded.
let url = format!(
"{}/chainweb/{CHAINWEB_API_VERSION}/mainnet01/chain/{chain}/header",
chainweb_node_address
);
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at kadena/light-client/src/client/chainweb.rs around line 240 and inspect every reference to the Chainweb network identifier. Trace how the client is initialized to determine where the runtime value enters; done means devnet, testnet01, and mainnet01 can be selected without hard-coded mainnet01 references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100