Title: Pair AKT With TERP & THIOL After the Migration

[hard-nett]

Authors Note: Hi! This proposal is coming in after an extensive collaboration with LLM's in order to be able to provide more granular details about our flow and trajectory we intend to take. I want to see Akash Network continue to win, as i believe in the approach, principles and culture leaders and contributors of akashs protocol displays.

SO, if you are reading this or even sharing with your llms to summarize, THANK YOU for taking the time to do so. Any questions or clarity that comes i will use LLM's I have access to for helping provide detailed responses and clarity as needed, just want to be up front about this.

---

Pair AKT With TERP & THIOL After the Migration

TL;DR

In 2023, Terp governance gifted 2.1M TERP and 2.85M THIOL to Akash's community pool, and they've sat idle since. Once Akash migrates under AEP-79, these IBC tokens can't be carried to the new chain, so they have to be spent on akashnet-2 before then. We propose allocating them now, along with pairing AKT, and holding everything in veto-able custody with no positions opened during the migration. After the migration, they'd be paired as TERP/THIOL, AKT/THIOL and AKT/TERP on Osmosis or Penumbra.

• *Ask: about 205,175 AKT (4.26% of today's pool; 6.18% if 343-345 pass), plus the pool's existing TERP and THIOL. Pairing AKT is set at 70% of the TERP/THIOL floor value; the rest of the TERP and THIOL pairs TERP/THIOL.
• Only cost: $7,200 for operations ($200 a month for 36 months, starting at first deployment).
• Accountability: a custody subDAO on Terp, a parent veto DAO with Akash members that can veto by two-thirds, 2/2 key custody on Penumbra, and monthly public reports.
• Term: a yearly refresh vote, with a full Akash governance review on 2030-04-20.

📄 Full proposal, budget, path, guardrails and simulation: permissionless.money/alpha/akash

Goal

We want to turn idle community-pool assets into working liquidity for AKT, with Akash keeping oversight through the migration and after it.

Funding

Line	USD	AKT ≈	Status
Liquidity pairing	$133,359.01	194,665	Held for Akash, deployed after the migration
Operations	$7,200	9,455	The only cost
Total	*$140,559.01	205,175	4.26% of today's pool; 6.18% if 343–345 pass

The USD amounts are fixed. The AKT amounts were calculated at the 2026-10-19 price of $0.685069 and will be recalculated when the proposal is submitted. Funding comes in a single payment, and no follow-up spend proposals are planned. Any operations AKT that isn't used goes back to the community pool, or to the treasury that replaces it, at the 2030 review or if the program winds down early.

Timeline

1. Now to [date]: community feedback here and in the SIGs and WGs.
2. [date]: on-chain vote with a 7-day voting period. Before the vote, we'll publish the multisig address and the parent veto DAO nominees.
3. After the vote passes: governance votes on Akash and Terp reconnect the IBC connection between the two chains, and TERP/THIOL move to Terp custody.
4. Until cutover: we hold everything and open no positions.
5. After the AKT claim: liquidity is deployed in stages.

References

• AEP-79, the Akash chain migration [link]
• Precedents: Prop 316 (market-making liquidity) and Prop 341 (relayer gas funding)
• Separate proposal: Private Payments for Akash's Reserve Marketplace [link]
• SIG/WG notes and recordings [add]

Open questions for the community

Who should sit on the parent veto DAO, and how long should the veto window be? We'd like your input on both before the vote.

---

• Edited 2026-10-19: ask retuned to the smaller community pool (see the update in the comments).

---

[hard-nett]

Open questions for the community

Who should sit on the parent veto DAO, and how long should the veto window be? We'd like your input on both before the vote.

Authors Note: after joining and sharing this proposal in the community working group today, Joe from Akash provided two specific feedback point to this initial proposal which in essence is "1. why should the community care about this proposal", and the second being in regards to our intentions of at minimum, "2. what to do with the existing community pool assets if the proposal is not supported".
Iterating our proposal page to include these details, however will answer here, which is:

1.a: Terp Network community is a part of the Akash Community. We actively utilize akash providers for network RPC & sentry node deployments, contributed passively to the akash-omnibus repo, and have curated our own rust client library for deployment bid lifecycles.
1.b: Akash network priority is scaling where its markets are accesable, away from its sovereign L1. By supporting an 3rd party stewardship of deploying liquidity into more DEX's, this overall resonates with that priority, and also can provide direct additional opportunities for akash community members

2: In the scenario we truly want to avoid being this proposal is not supported, we will not coordinate the retrieval of the supply of TERP or THIOL that was gifted to akash network, and expect it to be permenantly gone from circulation, as has occurred with Stargaze, Osmosis, Omniflix, and Evmos allocations.

[hard-nett]

Update (2026-10-19): ask retuned to the smaller community pool

Since we opened this thread, #342 passed (1,605,394 AKT), and Overclock Labs' Q3 requests #343, #344 #345 (1,492,246 AKT together) are in voting until 2026-10-21. If all of them pass, about 3.32M AKT would be left in the pool. To keep our footprint proportionate, we've set the pairing AKT at 70% of the TERP/THIOL floor value instead of 100%. The roughly 30% of TERP and THIOL without matching AKT will pair TERP/THIOL with each other. The ask is now about 205,175 AKT ($133,359.01 pairing + $7,200 operations at $0.685). That's 4.26% of today's pool, or 6.18% if 343-345 pass, and about 6.74% together with our separate research proposal. Custody, the hold through the migration, the three pairs, the veto structure and operations are all unchanged. The summary above and the proposal page are updated to match.