From 2be8859be6bb94f56301cae9b7d0c6dc9a67fd81 Mon Sep 17 00:00:00 2001
From: ztorio <ztoriocoin@gmail.com>
Date: Fri, 24 Oct 2025 21:48:54 +0200
Subject: [PATCH] Create ztoriomigration

PR for migrating ztorio tokens to new pair
---
 ztoriomigration | 52 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 52 insertions(+)
 create mode 100644 ztoriomigration

diff --git a/ztoriomigration b/ztoriomigration
new file mode 100644
index 0000000..f32af55
--- /dev/null
+++ b/ztoriomigration
@@ -0,0 +1,52 @@
+---
+name: Migrating ZTORIO token from ZTORIO/SOL to ZTORIO/ZC pair
+about: Request to migrate ZTORIO liquidity from the ZTORIO/SOL pair to a new ZTORIO/ZC pair, re-deploy liquidity, and ensure a seamless transition for holders.
+title: '[Ztorio migration] Migrate liquidity to ZC pair'
+labels: 'work-request, ztorio-migration'
+---
+
+# Work Request
+
+**Note**: Use this for work requiring team access (permissioned protocol access, migrations, fee changes, etc.). If you're submitting code yourself, use "Code Contribution" instead.
+
+## What Should Be Built
+
+1. Remove liquidity from the current ZTORIO/SOL pool.
+2. Create a new liquidity pool for ZTORIO/ZC.
+3. Re-deploy the liquidity into the ZTORIO/ZC pool.
+4. If required, distribute migration compensation (airdrop or equivalent) to ensure holders remain unaffected.
+
+
+## Why Does This Matter?
+
+**Impact on the project:**
+
+Strengthens ZC as the base coordination asset
+
+Gives Ztorio a clearer role as cultural + narrative liquidity
+
+Creates a self-reinforcing internal market loop
+**Who benefits:**
+ztorio and zc
+
+**Expected outcome:**
+Seamless migration with no action required from holders.
+
+## Supporting Evidence
+
+**User demand / Data / Research:**
+<!-- Links to Discord feedback, similar projects, metrics, etc. -->
+
+
+---
+
+## Checklist
+
+- [v] Clear description of what to build
+- [v] Explained why this matters
+- [v] Provided supporting evidence
+- [v] Read [CONTRIBUTING.md](../../CONTRIBUTING.md)
+
+---
+
+**Note**: The ZC team currently reviews and prioritizes work requests. In the future, decision markets will determine which requests get built and rewards.