diff --git a/LKMEX-whitelist/ElrondArt.md b/LKMEX-whitelist/ElrondArt.md
new file mode 100644
index 0000000..12214a0
--- /dev/null
+++ b/LKMEX-whitelist/ElrondArt.md
@@ -0,0 +1,29 @@
+## Name of project
+ElrondArt
+
+## Description
+Since January 2022, we want to make beauty the trademark of Elrond's NFT community.
+We do a lot of tasks for the community such as assist/support other projects with concept art, provide a variety of styles for their collections and give our exclusive members the power to run the project. 
+Website: https://elrondart.io
+
+
+## Purpose
+We send to our holders weekly LKMEX depending on the collection they own.
+We currently use python script for the distribution but might invest in deploying a SC if our project get whitelisted.
+
+## Address of smart contract
+To be determined
+
+## Code of smart contract
+To be determined
+
+## Description for every functionality of the contract
+To be determined
+
+## Number of users
+
+Around 80 wallets
+
+## Average LKMEX used in last month
+
+During the last month we have distributed around 5 millions $LKMEX
\ No newline at end of file
diff --git a/LKMEX-whitelist/whitelist_request_template.md b/LKMEX-whitelist/whitelist_request_template.md
new file mode 100644
index 0000000..1c742b8
--- /dev/null
+++ b/LKMEX-whitelist/whitelist_request_template.md
@@ -0,0 +1,45 @@
+# Template for requesting transferRole for LKMEX
+
+Transferability
+In order to conserve its energy and protect its benefits, old and new LKMEX will no longer be transferable, being 
+henceforth bound to the account where it was initially locked. Some limited transfers for LKMEX will still continue 
+to be allowed - check the whitepaper for this.
+
+Other services and products beyond xExchange can request for transfer roel which will have to be authorized by the 
+governance. Before the xExchange (Maiar DEX 2.0)  launch, projects will be able to submit a request via Github to be 
+whitelisted. 
+
+Note that only projects and smart contracts that serve as catalysts for user adoption and that bring valuable use 
+cases will be considered eligible (for example use cases that go against the principles outlined above, where LKMEX 
+rules are overridden, re-enabling selling or buying will not be eligible). After the  xExchange (Maiar DEX 2.0) launch, 
+pre-whitelisted projects and SCs will potentially be revisited through a governance call.
+
+The project has to make a pull-request in the current repository, where he adds a new file in the LKMEX-whitelist 
+folder by filling in the current template document. The name of the document should be the name of the project.
+
+Note: the will lose the transfer role after you make an upgrade on the contract. The projects needs to make a new pull
+request, where he updates the new code of the smart contract and explains the changes.
+
+## Name of project
+[Fill in]
+
+## Description
+[What does the project do?]
+
+## Purpose
+[Why does the project need transfer role for LKMEX?]
+
+## Address of smart contract
+[address] [link on explorer]
+
+## Code of smart contract
+[Post link to github]
+
+## Description for every functionality of the contract
+[Post link to github]
+
+## Number of users
+
+## Average LKMEX used in last month
+
+