Open
Description
Problem Statement
Some networks that are deprecated are not in the list. However, these networks are still needed for legacy reasons in substreams applications. Currently, there's no way to access information about these deprecated networks through the registry.
Proposed Solution
Add deprecated networks to the registry with a deprecated flag to distinguish them from active networks.
Registry Changes
- Add a deprecated boolean field to network entries
- Include deprecation_reason field (optional) for documentation
- Include deprecated_date field for tracking
This would allow the registry to contain both active and deprecated networks, with clear marking of their status.
Implementation Notes
The registry would include all networks (active and deprecated). Libraries that fetch from this registry could be modified in their respective repositories to filter out deprecated networks by default, with an option to include them when needed.
Benefits
- Legacy Support: Downstream applications can access deprecated network information when needed
- Historical Record: Maintains a complete record of all networks that have existed
- Flexibility: Libraries can choose how to handle deprecated networks based on their needs
- Documentation: Provides context for why networks were deprecated
Impact
- Registry will be larger as it includes deprecated entries
- Potential breaking changes for people fetching the registry directly and not filtering out the deprecated one. But can be fixed with the next point.
- Libraries consuming this registry may need updates to handle the deprecated flag appropriately
Metadata
Metadata
Assignees
Labels
No labels