From 4402c3bba0eb4247dc794a3b3c3ec438c5cf1eeb Mon Sep 17 00:00:00 2001
From: Javier C <javier.m.costa@mantra.finance>
Date: Mon, 2 Dec 2024 14:18:02 +0000
Subject: [PATCH 1/2] ci: add support for stableswap deployments

---
 scripts/deployment/deploy_pool.sh | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/scripts/deployment/deploy_pool.sh b/scripts/deployment/deploy_pool.sh
index 1254920..0a3033a 100755
--- a/scripts/deployment/deploy_pool.sh
+++ b/scripts/deployment/deploy_pool.sh
@@ -22,6 +22,7 @@ function display_usage() {
 #  "swap_fee": "0.002",
 #  "burn_fee": "0",
 #  "pool_type": "constant_product",
+#  "amp_factor": 85,
 #  "pool_identifier": "pool_identifier",
 #  "assets": [
 #    {
@@ -48,6 +49,10 @@ function read_pool_config() {
 	burn_fee=$(jq -r '.burn_fee' $pool)
 	pool_type=$(jq -r '.pool_type' $pool)
 	pool_identifier=$(jq -r '.pool_identifier' $pool)
+
+	if [[ "$pool_type" == "stable_swap" ]]; then
+		amp_factor=$(jq -r '.amp_factor' $pool)
+	fi
 }
 
 function create_pool() {
@@ -84,6 +89,12 @@ function create_pool() {
 		asset_decimals+=($decimals)
 	done
 
+	if [[ "$pool_type" == "stable_swap" ]]; then
+		pool_type='{"'$pool_type'": {"amp": '$amp_factor'}}'
+	else
+		pool_type='"'$pool_type'"'
+	fi
+
 	create_pool_msg='{
                      "create_pool": {
                        "asset_denoms":["'${asset_denoms[0]}'","'${asset_denoms[1]}'"],
@@ -103,11 +114,13 @@ function create_pool() {
                          },
                          "extra_fees": []
                        },
-                       "pool_type": "'$pool_type'",
+                       "pool_type": '$pool_type',
                        "pool_identifier": "'$pool_identifier'"
                      }
                    }'
 
+	echo -e"\n$create_pool_msg\n"
+
 	echo -e "\e[1;31m⚠️ WARNING ⚠️️\e[0m"
 
 	echo -e "\e[1;32mCreating pool with the following configuration:\e[0m"

From 36a571a2cf727249317f2ffe01b6bda5c62893b1 Mon Sep 17 00:00:00 2001
From: Javier C <javier.m.costa@mantra.finance>
Date: Mon, 2 Dec 2024 14:18:17 +0000
Subject: [PATCH 2/2] chore: format security doc

---
 docs/SECURITY.md | 25 +++++++++++++++----------
 1 file changed, 15 insertions(+), 10 deletions(-)

diff --git a/docs/SECURITY.md b/docs/SECURITY.md
index 844d8bb..802b53e 100644
--- a/docs/SECURITY.md
+++ b/docs/SECURITY.md
@@ -1,23 +1,28 @@
 # Security Policies and Procedures
+
 This document outlines security procedures and general policies for the `mantra-dex` project.
-* [Reporting a Bug](#reporting-a-vulnerability)
-* [Disclosure Policy](#disclosure-policy)
+
+- [Reporting a Bug](#reporting-a-vulnerability)
+- [Disclosure Policy](#disclosure-policy)
 
 ## Reporting a Vulnerability
+
 Security is something we take seriously at MANTRA. Thanks for taking the time to improve the security of `mantra-dex`,
 we appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
 
-Please report security bugs by sending an email to security@mantrachain.io. Do not report it publicly on the GitHub 
-issues tracker. Your report should detail the necessary steps to reproduce the security issue. We will acknowledge your 
-email within 72 hours and send a detailed response indicating the next steps. After the initial reply to your report, 
-we will keep you informed of the progress towards a fix and full announcement and may ask for additional information 
+Please report security bugs by sending an email to security@mantrachain.io. Do not report it publicly on the GitHub
+issues tracker. Your report should detail the necessary steps to reproduce the security issue. We will acknowledge your
+email within 72 hours and send a detailed response indicating the next steps. After the initial reply to your report,
+we will keep you informed of the progress towards a fix and full announcement and may ask for additional information
 or guidance.
 
 Report security vulnerabilities in third-party modules to the person or team maintaining the module.
 
 ## Disclosure Policy
-If we receive a security bug report, we assign it to a primary handler. This person will coordinate the fix and release 
+
+If we receive a security bug report, we assign it to a primary handler. This person will coordinate the fix and release
 process, involving the following steps:
-* Confirm the problem and determine the affected versions.
-* Audit code to find any potentially similar problems.
-* Rollout the fixes.
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potentially similar problems.
+- Rollout the fixes.