Repository navigation
Notify Discord when new hotkeys get committed and active weights - #143
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The independent reveal monitor now sends Discord INFO messages when a successful commit first allocates weights to a new hotkey, and again when a matching weight row is observed active. Messages include the hotkey, UID, share, and block; active weights are distinguished from network-wide emissions.
The monitor seeds its inventory from existing active recipients, persists announced hotkeys and pending activation notices across restarts, and queues failed informational deliveries for retry. Ordinary share changes do not reannounce a hotkey. Reveal error alerts and recovery messages continue independently. Publication is never paused or restarted by the monitor.
Consumer: the deployed
cacheon.chain.weight_reveal_monitorprocess. Casualty: the previous error/recovery-only notification behavior. Net production LOC: +33. Docs describe the notification lifecycle and persisted retry queue.Validation: 32 focused monitor, commit-publication, and fallback tests pass, including first allocation, activation, dust rounding, superseded commits, delivery retries, restarts, unchanged recipient sets, and preservation of read-only journal access. Ruff, documentation checker, strict MkDocs build, LOC, and surface checks pass.
Deployed by restarting only the independent monitor; the publisher PID is unchanged. The existing private webhook file is reused and is not present in this diff.