defi-registry-manager

To update a DeFi registry across multiple repositories, identify the registry type (token, protocol, chain, or network), follow the specific checklist for that type, update all related files across frontend, Rust core, server, and admin tooling, and run validation checks to ensure data consistency.

The best way to synchronize configurations across codebases is using an automated four-step workflow: identify the registry type, apply the corresponding checklist, update all impacted files including RPC endpoints, and validate changes to eliminate registry drift.

DeFi registry drift occurs because the registry is spread across multiple codebases requiring coordinated updates; without a centralized workflow to enforce file updates and validation across frontend, server, and core, data becomes inconsistent.

Yes, this registry automation workflow supports adding new DEXes, token addresses, and network endpoints by enforcing a four-step checklist that updates all affected files across frontend, Rust core, server, and admin tooling repositories.

To validate changes after updating DeFi protocols and chains, you must run the final validation step in the four-step workflow, which checks all updated files across the multiple repositories to ensure data integrity and eliminate registry drift.

Yes, you can use this skill to add new network endpoints and RPC configurations because the workflow explicitly handles Rust core, frontend, server, and admin tooling files to ensure synchronized updates across all codebases.