FilOzone / FilOzone/onramp-contracts
Cleanup config
- Dominant language
- Go
- Stars
- 5
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
xchain config should probably have more high level sections
client
aggregator
buffer
Its maybe nicer to put it in TOML if the deploy script can bear writing to it. IDK I'll probably keep in JSON and just have high level map breaking things down. Other option is ~/.xchain/{client-config.json aggregator-config.json buffer-config.json}
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the xchain configuration and the deploy script mentioned in the issue. Compare the proposed high-level client, aggregator, and buffer sections with the current JSON layout; done means the configuration structure and chosen file organization are agreed and updated without breaking deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100