Describe the Bug(s)

Issue 1: Stale Node ID Data Retention

• The system fails to update gestalts with new Node IDs when a node is destroyed and recreated. Old cryptolinks are not automatically removed, causing outdated information to persist.

Issue 2: Inefficient Discovery Mechanism

• The background discovery system lacks transparency and does not work well with multiple cryptolinks, failing to prioritize the most recent cryptolinks. Manual rediscovery does not update the gestalt with a new Node ID, leading to stale data issues.

To Reproduce

1. User A discovers User B's Node ID with polykey identities discover.
2. User B destroys their node and recreates a new one, leaving the old cryptolink intact.
3. User A attempts to rediscover User B, but the old Node ID remains visible.

Note: For the demo, in order for us to solve for this, manual deletion of the cryptolink on GH was required after deleting the old node.

Expected Behavior

• The discovery mechanism should handle the dynamic nature of nodes and their cryptolinks efficiently.
• A manual rediscovery command should force the system to update the gestalt with new Node IDs.
• A new command should be available to delete old cryptolinks.
• A precedence system for handling cryptolinks should be established, prioritizing the most recent ones.

Proposed Solutions

• Implement an identities status command for progress feedback on discovery tasks.
• Add a feature for manual rediscovery to update Node IDs immediately.
• Create a systematic approach to handling and cleaning up cryptolinks when nodes are destroyed.

Screenshots/Logs

(attach relevant screenshots or logs here, when recreating the issue.)

Platform

• Device: MacBook Air (2021 Mac M1)
• OS: macOS (latest)
• Version: Latest release v0.2.6

Additional Context

• Discussions from Discord

Links to Related GitHub Issues

• Background Discovery Mechanisms: GitHub Issue #691
• identities status Command: GitHub Issue #162
• Vault Sharing With GestaltIDs: GitHub Issue #626

Notify maintainers

(Use git blame or refer to Discord conversations to identify relevant contributors.)