From edcb30e23cd9a62af87714b8e54c3ee84fff230c Mon Sep 17 00:00:00 2001
From: Aaron Blankstein <aaron@blockstack.com>
Date: Thu, 16 Apr 2020 09:50:51 -0500
Subject: [PATCH] fix: 1429 - bug in nft initialization which can lead to panic

---
 src/vm/database/clarity_db.rs | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/vm/database/clarity_db.rs b/src/vm/database/clarity_db.rs
index 6b4e4be8c..485fa974d 100644
--- a/src/vm/database/clarity_db.rs
+++ b/src/vm/database/clarity_db.rs
@@ -505,10 +505,6 @@ impl <'a> ClarityDatabase <'a> {
         let data = NonFungibleTokenMetadata { key_type: key_type.clone() };
         let key = ClarityDatabase::make_metadata_key(StoreType::NonFungibleTokenMeta, token_name);
         self.insert_metadata(contract_identifier, &key, &data);
-
-        assert!(!self.store.has_entry(&key), "Clarity VM attempted to initialize existing token");
-
-        self.put(&key, &data);
     }
 
     fn load_nft(&mut self, contract_identifier: &QualifiedContractIdentifier, token_name: &str) -> Result<NonFungibleTokenMetadata> {