From a541855c747c2642e82e7b97cba4d94d0136aee2 Mon Sep 17 00:00:00 2001
From: Ninjaxan <drleeberman@gmail.com>
Date: Sun, 23 Aug 2026 14:27:47 -0500
Subject: [PATCH 1/3] CryptoDungeon: correct dungeon REStake bot address and
 run_time

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.
---
 CryptoDungeon/chains.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CryptoDungeon/chains.json b/CryptoDungeon/chains.json
index 40b863b4eb..7f3a7513ff 100644
--- a/CryptoDungeon/chains.json
+++ b/CryptoDungeon/chains.json
@@ -33,8 +33,8 @@
       "name": "dungeon",
       "address": "dungeonvaloper1aj5jlmvqp8dd26rsec6624szthlazdn25leye3",
       "restake": {
-        "address": "dungeon1w6su2zgdsvufhwl8pdcuephttz2vjw290k5t78",
-        "run_time": ["09:00", "21:00"],
+        "address": "dungeon1yg5wsmyzxfdk9cgk5q3rgqa7maa38e4dxknnhc",
+        "run_time": "21:00",
         "minimum_reward": 100000
       }
     },

From 275a15b3e88131eefdfb82c433aac9fd05efdc5f Mon Sep 17 00:00:00 2001
From: Ninjaxan <drleeberman@gmail.com>
Date: Mon, 24 Aug 2026 07:01:39 -0500
Subject: [PATCH 2/3] CryptoDungeon: fix cosmoshub bot address, drop chains we
 no longer validate

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.
---
 CryptoDungeon/chains.json | 38 +++-----------------------------------
 1 file changed, 3 insertions(+), 35 deletions(-)

diff --git a/CryptoDungeon/chains.json b/CryptoDungeon/chains.json
index 7f3a7513ff..daf3505fd4 100644
--- a/CryptoDungeon/chains.json
+++ b/CryptoDungeon/chains.json
@@ -6,26 +6,8 @@
       "name": "cosmoshub",
       "address": "cosmosvaloper13x4pynlp86prhcmtns742kgsgu7pjtzj4djh7s",
       "restake": {
-        "address": "cosmos1w6su2zgdsvufhwl8pdcuephttz2vjw29p9td5u",
-        "run_time": ["09:00", "21:00"],
-        "minimum_reward": 50000
-      }
-    },
-    {
-      "name": "stargaze",
-      "address": "starsvaloper13x4pynlp86prhcmtns742kgsgu7pjtzj0m9tz2",
-      "restake": {
-        "address": "stars1w6su2zgdsvufhwl8pdcuephttz2vjw294eusld",
-        "run_time": ["09:00", "21:00"],
-        "minimum_reward": 5000000
-      }
-    },
-    {
-      "name": "juno",
-      "address": "junovaloper13x4pynlp86prhcmtns742kgsgu7pjtzjeknkwx",
-      "restake": {
-        "address": "juno1w6su2zgdsvufhwl8pdcuephttz2vjw29hhgknq",
-        "run_time": ["09:00", "21:00"],
+        "address": "cosmos1yg5wsmyzxfdk9cgk5q3rgqa7maa38e4dg9v4ar",
+        "run_time": "21:00",
         "minimum_reward": 50000
       }
     },
@@ -40,21 +22,7 @@
     },
     {
       "name": "atomone",
-      "address": "atonevaloper13x4pynlp86prhcmtns742kgsgu7pjtzjuy3vwr",
-      "restake": {
-        "address": "atone1w6su2zgdsvufhwl8pdcuephttz2vjw2909h2zy",
-        "run_time": ["09:00", "21:00"],
-        "minimum_reward": 50000
-      }
-    },
-    {
-      "name": "osmosis",
-      "address": "osmovaloper13x4pynlp86prhcmtns742kgsgu7pjtzjz4a3nk",
-      "restake": {
-        "address": "osmo1w6su2zgdsvufhwl8pdcuephttz2vjw29f7cazw",
-        "run_time": ["09:00", "21:00"],
-        "minimum_reward": 200000
-      }
+      "address": "atonevaloper13x4pynlp86prhcmtns742kgsgu7pjtzjuy3vwr"
     }
   ]
 }

From 58f12fa9a621d22db074cd5a3f0051001a80927b Mon Sep 17 00:00:00 2001
From: Ninjaxan <drleeberman@gmail.com>
Date: Mon, 24 Aug 2026 08:31:22 -0500
Subject: [PATCH 3/3] CryptoDungeon: keep atomone on REStake, with the address
 we hold

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.
---
 CryptoDungeon/chains.json | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/CryptoDungeon/chains.json b/CryptoDungeon/chains.json
index daf3505fd4..f21a3dcaa0 100644
--- a/CryptoDungeon/chains.json
+++ b/CryptoDungeon/chains.json
@@ -22,7 +22,12 @@
     },
     {
       "name": "atomone",
-      "address": "atonevaloper13x4pynlp86prhcmtns742kgsgu7pjtzjuy3vwr"
+      "address": "atonevaloper13x4pynlp86prhcmtns742kgsgu7pjtzjuy3vwr",
+      "restake": {
+        "address": "atone1yg5wsmyzxfdk9cgk5q3rgqa7maa38e4dx9sjtm",
+        "run_time": "21:00",
+        "minimum_reward": 50000
+      }
     }
   ]
 }