K9 DAO Roundtable of Dogs #21 (1/21/2026) AGENDA
Attendees
Turtle
Buzz
Shane
Queen
Sentinel
Couch
Hero
Dream
Archangel
Danger
Did not attend
Seth
Vote Outcome: Post-Exploit Strategic Pathway Snapshot vote has concluded and Option #5 has won. Immediate priorities now shift from “options discovery” to execution planning: chain selection vote + settlement mechanics token timeline + working closely with DAO lawyer to ensure everything is done safely/correctly
Chain selection vote targeted for 2/1/2026 via Snapshot. Will include all relevant options from community.
Shibarium Operations Sunset Decision DAO has determined a sunset date of 2/25/2026 for Bonecrusher and all Shibarium operations.
Workstreams underway (in progress):
Website + dApp changes in process that highlight the sunset date and user action items for infrastructure shutdown. Additional infrastructure planning, relocating K9 docs, user-facing FAQ and step-by-step guidance legal review of all materials/statements/terms
Shibarium Bridge Status + “Bridge Issue” Explanation
Since the re-enablement of validator delegation withdrawals on the Shib side, there seems to be an accounting mismatch with how much BONE is perceived to be released. An error that was caused post-hack by the Shib team and giving troubles to the knBONE bridge The K9 devs are working on a solution without any guidance, insight, or docs but are working through it this week and hope to find a solution for the affected users this week (aiming for solution by 1/25/26) It does not pose a long term problem, just something that K9 needs to retroactively find a workaround through whatever changes Shib made.
It seems most users have been able to claim their BONE since the meeting, but some users still may be experiencing delays.
Agent IX Issue Caught (Process + Risk Handling)
Quick incident review: what was caught (high-level) A high severity exploit was discovered that would allow malicious actors to compromise Agent IX and the server it operates on. The team reacted immediately upon discovery of this issue and has shutdown the Agent IX tool and server. impact assessment (who/what was affected) It does not appear that Agent IX was compromised due to the swift reaction of the team after discovering the exploit and subsequent potential vulnerability mitigation status and what’s changing going forward Discussions around how Agent IX should exist moving forward based on Option #5 Potential to scale/monetize as a product for the DAO Service remains offline until updates can be made and above strategic decisions are clear.
New Website + Platform UI Overhaul
New website underway and how it supports the pivot: clearer product positioning post-Shibarium dedicated “Sunset Hub” UX (deadlines, actions, FAQs, links) migration / claims UX (once new chain is voted on)
UI/copywriting: legal-led language updates (risk-managed phrasing, consistency across forum/site/docs).
Legal Discussions
Review legal guidance on: how we describe the exploit impact + replacement approach wording around “compensation” vs “replacement / settlement” user instructions and liability framing tone consistency: “lawyer-approved” copy across all public channels What can realistically be built next (to satisfy community + protect runway)
Frame the “next build set” in terms of: time-to-ship cost-to-ship ability to generate usage/revenue ability to tie value back to KNINE Candidate “realistic” next builds to discuss (not committing tonight): Airdrop tool commercialization path (pricing, go-to-market, integrations) Agent IX repositioning + monetization mechanics token-gated services / TG automation multisend / tooling suite expansion based on existing work SHIB yield tool on Ethereum etc
Timelines on the new token (Option #5 execution timeline)
Establish a public-facing milestone timeline (draft tonight, finalize after chain decision): chain decision date contract deployment + verification date claims contract/security review window liquidity bootstrapping window claim launch window post-launch timeline (first 30/60/90 days)
Hard date on when new decision for future is made vs. putting treasury into liquidity Feb 1st - snapshot vote including all relevant chains mentioned in forum proposal.
PROPOSALS FOR REVIEW
Chain Vote: Where Should the Stolen 25% KNINE Be Minted? — (REVIEW + SET DATE)
Confirm final candidate chains and evaluation criteria (liquidity, ecosystem fit, grants, security, UX, infra cost). Confirm whether the vote is ready tonight vs “temperature check → Snapshot.” 2/1/2026
ShibCrusher: A Liquid Staking Protocol for SHIB on Ethereum with KNINE Utility Integration - (REVIEW ONLY)
Viability review: where would SHIB yield actually come from, and is this “liquid staking” in the strict sense? Action request (if any): community research on existing SHIB yield sources that are credible and scalable. Stake SHIB → Earn KNINE (Shibcinerator) Identify best yield without much/any IL Roundtable proposal/product research around this
Proposal: Migrate K9 Finance DAO to Arbitrum (Settlement + Treasury) and Relaunch with Yield Vaults + DAO-Owned Liquidity Tooling - (REVIEW ONLY)
Likely out of scope (costs, timelines, treasury limitations) Identify what overlaps with Option #5 execution vs what is “Phase 2+”. Not feasible without a grant