mimblewimble/grin

Version config files so that new grin server doesn't use obsoleted old configs?

Closed

#1,686 opened on Oct 8, 2018

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)Rust (991 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (4,876 stars)
PR merge metrics
 (Avg merge 6d 11h) (25 merged PRs in 30d)

Description

John Tromp @tromp 16:37 we need to version these config files so that new grin server doesn't use obsolete old configs?!

Gary Yu @garyyu 16:39 Good point! I remember @quentinlesceller had a similar question about how to add new added config item for the existing runing node. Perhaps some progress on this topic?

Contributor guide

Research direction
The issue discusses versioning config files for the Grin cryptocurrency server to prevent use of obsolete configurations. It references a conversation between developers but lacks a detailed specification. Investigate the repository's existing config file structure and loading logic (e.g., src/bin/grin.rs or config directory). Review linked comments for any proposed approaches. Consider implementing a config version field and migration mechanism similar to semantic versioning or database migrations. Check if any config files or related issues provide examples of versioning.
Tech stack
rust
Domain
backenddevopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rustconfig file handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40