[Living Ticket][Infra] Dima's Dynamic Backlog (because infra is key)

[Olshansk]

Note

Living Ticket as infra requirements change all the time

--- First Draft ---

Tickets

• Look at what’s necessary? Shannon (view)
• E.g.

Revisit TODOs

• poktroll repo
• infrastructure repo
• path repo

Chain Halt Reorg Playbook

• Resources:
  • Take the chain_halt_recovery branch
  • Take this notion doc: https://www.notion.so/buildwithgrove/Reorg-Playbook-Chain-Halt-05-02-2025-1e7a36edfff680218187f6cef2be5bce?pvs=4
• Put together a playbook

Chain Halt Recovery Playbook

• Using new Cosmos feature: add bulk upgrade

Shannon MainNet Tasks

• Snapshot Infrastructure
  • Deploy infrastructure on MainNet
  • Document playbook on MainNet
• Validators
  • Take down severs
  • Deploy to k8s
• Dashboard
  • Mirror Beta Dashboard to MainNet
  • Backup Grafana dashboards as json

Shannon BetaNet

• Document Playbook for Infrastructure Maintenace

PATH Alerts

• Revisit what exists -> Think about it -> Update alerts
• Write a playbook / document -> share with team

Shannon Alerts

• MainNet Alerts
  • Ensure blocks are moving at least every hour
  • Last signed block
• AlphaNet
  • Ensure blocks are moving at least every hour
• BetaNet
  • Ensure blocks are moving at least every hour

[Olshansk]

More "little thing" from @okdas

[Olshansk]

@okdas Top of my mind priorities:

1. MainNet Observability: Ensuring we have visibility so we can keep iterating on reducing chain size: https://github.com/buildwithgrove/infrastructure/issues/147

2. Snapshot Infrastructure: Not looking into improving the snapshots themselves, but simply migrating the existing infra to be more stable.

3. Infra migration: A plan to migrate our infra before the end of the summer. This is related but most of it is in your head: https://github.com/buildwithgrove/infrastructure/issues/80

---

Request: Please share your personal list of TODOs so it's easy to track (and refer back to).