# GFP-4: Blacklist Multichain Contract

**URL:** <https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144>\
**Category:** Final GFPs\
**Tags:** approved-to-vote, approved\
**Created:** [January 21, 2024, 4:36pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144 "2024-01-21T16:36:08Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![LordFrumpsalot](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/lordfrumpsalot/32/44_2.png) [@LordFrumpsalot](https://forum.guardfdn.com/u/LordFrumpsalot)\
**Post date:** [January 21, 2024, 4:36pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/1 "2024-01-21T16:36:08Z")

</div>

### Abstract

$GUARD used Multichain protocol to bridge to Arbitrum and Polygon chain. This was to expand its outreach. Multichain was exploited however and many crypto assets using Multichain, including $GUARD have suffered. This proposal is to blacklist the Multichain contract, 0xCDd28a3033a6DC1472a1403156B426905bF127bA which will prevent it from transferring any of the GUARD tokens that it holds.

### Proposal Category

Process

### About the Team

The KS team consists of individuals with a diverse skill set.  
Wizard, Owner and Founder of KnightSwap. Runs a Development Firm that has full capability for Web 2/Web 3 projects from beginning to end  
Frumpo/Lord Frumpsalot, Operations, Risk Analysis, Project Manager for KS. A Guardian of TGA.  
RealJayDee, Backend Support Manager  
V, Community Manager  
Arrow, Graphic Artist

### Motivation

To avoid the impacts of the exploit, Blacklisting the Multichain Address from selling which contains large amounts of $GUARD, can minimize the exploit’s impact and provide an opportunity forward to preserve the value of $GUARD on Polygon and Arbitrum chains.

### Benefit to Guardian Ecosystem

The main benefit in implementing this proposal is to begin creating a pathway to preserving the value of the $GUARD tokens on the Polygon and Arbitrum chains. This in turn should protect the holders of $GUARD on those chains.

### Rationale

In order to keep the value of $GUARD and accounting accurate, Multichain’s address needs to be blacklisted as it was not intended for that address to have access to sell. Multichain was meant to be a locking mechanism to allow for $GUARD to move to other chains and unlock as they were bridged back. By Blacklisting, it gives an opportunity for a solution to preserve the value of $GUARD on the other chains. Otherwise, Multichain can sell at a moment’s notice and double counting would occur.

### Specifications

GUARD smart contract on BNB chain  
Multichain contract: 0xCDd28a3033a6DC1472a1403156B426905bF127bA

### Steps to Implement

1. Schedule Blacklist of Multichain contract 0xCDd28a3033a6DC1472a1403156B426905bF127bA
2. Wait 3 days for Guard timelock
3. Push transactions through

### Timeline

5 days after passing proposal

### Overall Cost

0

---

<div class="post-metadata">

**Author:** ![DennisD](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@DennisD](https://forum.guardfdn.com/u/DennisD)\
**Post date:** [January 21, 2024, 11:52pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/2 "2024-01-21T23:52:11Z")

</div>

Sounds like a good idea

---

<div class="post-metadata">

**Author:** ![Monkehking](https://avatars.discourse-cdn.com/v4/letter/m/49beb7/32.png) [@Monkehking](https://forum.guardfdn.com/u/Monkehking)\
**Post date:** [January 22, 2024, 11:40am UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/3 "2024-01-22T11:40:53Z")

</div>

I think this should be implement asap, as it is it leaves Guard vulnerable and adds no benefit as it is.

---

<div class="post-metadata">

**Author:** ![SeanK](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/seank/32/12_2.png) [@SeanK](https://forum.guardfdn.com/u/SeanK)\
**Post date:** [January 22, 2024, 12:33pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/4 "2024-01-22T12:33:52Z")

</div>

Another solid idea, and agree this needs to be done asap to mitigate risk

---

<div class="post-metadata">

**Author:** ![RozK](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/rozk/32/60_2.png) [@RozK](https://forum.guardfdn.com/u/RozK)\
**Post date:** [January 23, 2024, 7:58am UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/5 "2024-01-23T07:58:22Z")

</div>

Feel like this needs to implemented asap.

---

<div class="post-metadata">

**Author:** ![EJNoble](https://avatars.discourse-cdn.com/v4/letter/e/dec6dc/32.png) [@EJNoble](https://forum.guardfdn.com/u/EJNoble)\
**Post date:** [January 23, 2024, 2:40pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/6 "2024-01-23T14:40:05Z")

</div>

Agreed, a top priority!

---

<div class="post-metadata">

**Author:** ![gregory](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/gregory/32/4_2.png) [@gregory](https://forum.guardfdn.com/u/gregory)\
**Post date:** [January 29, 2024, 7:08pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/7 "2024-01-29T19:08:25Z")

</div>

Hey everyone. Thanks for all the participation!

This post has been archived per the Governance Framework. New replies are no longer allowed. We’re moving into the Draft Phase! Follow this post as new updates will be posted below!

---

<div class="post-metadata">

**Author:** ![gregory](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/gregory/32/4_2.png) [@gregory](https://forum.guardfdn.com/u/gregory)\
**Post date:** [January 29, 2024, 7:08pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/8 "2024-01-29T19:08:31Z")

</div>

Archived on January 29, 2024, 7:08pm UTC



---

<div class="post-metadata">

**Author:** ![gregory](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/gregory/32/4_2.png) [@gregory](https://forum.guardfdn.com/u/gregory)\
**Post date:** [February 15, 2024, 11:28am UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/9 "2024-02-15T11:28:31Z")

</div>

Hey all,

The voting period has closed for this proposal and it has been accepted with a 100% pass rate. The proposal is now following the steps outlined in the implementation section.

The multichain contract has been submitted for blacklisting, **but has not yet been blacklisted**.

The Guard contract has a 3 day timelock. This waiting period serves as a crucial mechanism to ensure transparency, security, and protection against malicious activities or hasty decision-making.

We now wait for the 3 day timelock to take effect. Once the timelock time passes, the blacklist will go through, and an update will be posted in this thread.

---

<div class="post-metadata">

**Author:** ![gregory](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/gregory/32/4_2.png) [@gregory](https://forum.guardfdn.com/u/gregory)\
**Post date:** [February 25, 2024, 6:05pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/10 "2024-02-25T18:05:11Z")

</div>

Update:

We had multiple proposals wrap up at the same time. As such we’ve scheduled multiple modifications to the guard contract. After the 3 day wait, blacklisting of the multichain address didn’t go through for some reason. It might’ve been missed when we were scheduling in the other modifications.

To solve this we’ve re-input blacklisting the multichain contract into the time lock and we’re awaiting the passing of the 3 day wait time. Once passed the blacklist will go through, and an update will be posted here.

---

<div class="post-metadata">

**Author:** ![gregory](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.guardfdn.com/gregory/32/4_2.png) [@gregory](https://forum.guardfdn.com/u/gregory)\
**Post date:** [March 1, 2024, 4:17pm UTC](https://forum.guardfdn.com/t/gfp-4-blacklist-multichain-contract/144/11 "2024-03-01T16:17:05Z")

</div>

The multichain contract has been blacklisted per the community vote!
