Skip to content

Frizzy WL #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
radumihaipopa wants to merge 2 commits into from
Closed

Frizzy WL #22

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4c5a94
Frizzy WL
radumihaipopa Nov 21, 2022
34594a9
Update whitelist_request_template.md
radumihaipopa Nov 21, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 17 additions & 44 deletions LKMEX-whitelist/whitelist_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,58 +1,31 @@
# Template to request LKMEX `transferRole`

## Transferability

To conserve its energy and protect its benefits, old and new LKMEX will no longer be transferable, subsequently bound to
the account where it is currently held. Some limited transfers for LKMEX will continue to be allowed - check the
economics paper for more details.

Other services and products beyond xExchange can request transfer roles which will have to be authorized by governance
votes. Before the xExchange (Maiar DEX 2.0) launch, projects can submit a request to be whitelisted via Github.

We will consider eligible for transferRole only projects and smart contracts serving as catalysts for user adoption and
those who bring valuable use cases (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 it adds a new file in the LKMEX-whitelist
folder by filling in the existing template document. The name of the document should be the name of the project.

Note: Projects will lose the transfer role after upgrading the contract. You need to make a new pull request, where
new code updates brought to the smart contract must be explained and motivated.

Projects can also lose their `transferRole` status if the Smart Contract is being used in ways that go against LKMEX
principles. Questionable activities will be reviewed by the MultiversX team and any Project or Smart Contract found in
breach of the rules will automatically lose their transferRole status.

Whitelisted projects will be given a transferRole to the wrappedLKMEX tokenID, which is a token that does not
have energy and is used only by whitelisted projects.

The whitelisted projects will need to wrap the LKMEX they want to deposit or use. By wrapping it, the LKMEX will
temporarily “lose” its energy but the energy can be recovered and regained by unWrap it back.

Projects will be able to use the wrappedLKMEX to deposit and use in the whitelisted Smart Contracts. Users who will
get/claim wrappedLKMEX and will need to unWrap it in order to gain its original energy and convert it back to LKMEX v2
in order to enter liquidity or farms.

wrappedLKMEX does not have the benefits of the LKMEX v2, only after unwrapping you gain all the benefits.

## Name of the project
[Fill in]
Frizzy (FRIZZY-0153d1)

## Description of the project
[What does the project do?]
Frizzy is a 7777 NFTs collection of a cartoonish, red haired character that was inspired by our toddler (collection created by myself & my wife). The purpose of the project stands in creating a brand and helping children causes. We are now committed in helping Victor, the little boy who suffers of SMA, we have created 2 NFT collections for him. In parallel we are developing a children's book that we will launch on Amazon KDB.

More info https://linktr.ee/thefrizzyboy

## Purpose
[Why does the project need a transfer role for LKMEX?]
Our CDO was created early this year and we send our Discord verified holders monthly rewards in LKMEX.

To farm LKMEX on the DEX we have been using this address
https://explorer.elrond.com/accounts/erd14g90e39lylknqt32uwk0dde0u6fdr95vvk7wg5d89w9myd5mn5lq3zl7e2
and for distribution we use this address
https://explorer.elrond.com/accounts/erd195sm9czu7ufa9373plj4ku5ny2vne0jt0gquu4m8fr0n3nw9gsgqagatj2

We started distributing LKMEX on 14th March this year and done it monthly ever since.

## Address of Smart Contract
[address][link on explorer]
Our distribution is done through a python script, not a SC.

## Smart Contract Code
[Post link to github]
N/A

## Description for every Smart Contract functionality
[Post link to github]
N/A

## Number of users
## Average LKMEX used during the previous month

Our last distribution was on 18th October and we distributed ~3M LKMEX to 209 users. Our next distribution will happen these days and it will have ~6M LKMEX, as we turned the LKMEX farm into a LP and have greater rewards. We expect the farm to produce even more next month, around 8M at least.