Repository navigation
CryptoDungeon: correct REStake bot addresses, drop chains we no longer validate - #5197
Merged
tombeynon merged 3 commits intoAug 24, 2026
Merged
Conversation
The advertised dungeon bot address is one our operator does not hold. The bot that actually runs signs as dungeon1yg5wsmyzxfdk9cgk5q3rgqa7maa38e4dxknnhc (confirmed in its own run log, and the only REStake operator on our infrastructure); the previously listed address derives from a different mnemonic entirely and no process of ours holds it. Existing on-chain grants are unaffected either way - a registry entry only tells new delegators where to point. run_time drops to the single 21:00 run the bot actually performs, rather than advertising a 09:00 run that has no cron behind it.
…lidate Same correction as the dungeon entry, applied to cosmoshub: the advertised bot address is not one we hold. 31 delegators had granted to it and it has broadcast two transactions in its lifetime, so their autocompounding has effectively never run. The bot that does run signs as cosmos1yg5wsmyzxfdk9cgk5q3rgqa7maa38e4dg9v4ar. Removed stargaze, juno and osmosis - we no longer validate there (juno and osmosis are unbonded on chain, osmosis also jailed). atomone keeps its listing but loses its restake block: that validator is still bonded with delegators, so delisting it would cost them visibility, but our operator does not run atomone and should not advertise that it does. run_time is the single 21:00 run the bot actually performs.
Ninjaxan
changed the title
Restores atomone's restake block. The operator now runs atomone as well as cosmoshub and dungeon, and the address is the one derived from the mnemonic we hold rather than the atone1w6su... the entry previously advertised. Still three chains: stargaze, juno and osmosis stay removed - we no longer validate there.
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
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.
Two things, both about our entry telling the truth about what our operator actually does.
1. The advertised REStake bot addresses are not ones we hold.
Our operator signs as
…yg5w…; the entry advertised…w6su…, which derives from a different mnemonic entirely (not an HD-index variant) and no process of ours holds. Corrected on all three remaining chains:On Cosmos Hub that means 31 delegators granted to an address that has broadcast two transactions ever. The bot that does run settled 6 delegators on dungeon on its most recent run, and now runs all three chains.
Existing on-chain grants are unaffected — a registry entry only tells new delegators where to point, so this cannot revoke or redirect an authorization that already exists.
2. Dropped chains we no longer validate.
stargaze,junoandosmosisremoved — juno and osmosis are unbonded on chain, osmosis also jailed.run_timeis now the single21:00run the bot actually performs, rather than advertising an unbacked09:00.