Routing table

[hide-on-bush-x]

Summary

This pull request introduces significant improvements to the routing table and node management functionalities within the validator. The changes include the implementation of a new RoutingTable class, updates to the NodeManager for better handling of TEE addresses, and comprehensive test coverage for the new features.

Key Changes

1. RoutingTable Class:

   • Implemented a new RoutingTable class to manage miner addresses.
   • Added methods to add, remove, and clear miner addresses.
   • Implemented methods to retrieve all addresses or addresses associated with a specific miner hotkey.

2. NodeManager Updates:

   • Updated the NodeManager to use the RoutingTable for managing TEE addresses.
   • Added logic to clear existing addresses for a hotkey before adding new ones.
   • Improved logging for better traceability of address management.

3. Database Schema:

   • Updated the RoutingTableDatabase schema to enforce a unique constraint on the address column.
   • Allowed multiple records with the same uid and hotkey.

4. Test Coverage:

   • Added comprehensive tests for the RoutingTable and RoutingTableDatabase classes.
   • Ensured tests cover adding, updating, deleting, and retrieving addresses.
   • Verified unique constraint enforcement through test cases.

Testing

• All new features are covered by unit tests.
• Tests are run using an in-memory SQLite database to ensure isolation and repeatability.
• The test suite can be executed using the command: python -m unittest discover tests.

Additional Notes

• The .gitignore file has been updated to exclude database files generated during testing.
• The Validator class now initializes a RoutingTable instance for managing TEE addresses.

closes #7

[hide-on-bush-x]

Edge case found:
When a hotkey get deregistered, their addresses are not being cleaned

[grantdfoster]

should be self.get_tee_addresses(node) for clarity

[hide-on-bush-x]

Good catch

[grantdfoster]

not familiar w/ sqlite - are there other potential errors that could happen here? And, if so, do we want some retry logic?

[hide-on-bush-x]

there must be some other errors to catch, will take a look