Transparency to the Max: A Statement from $LUPE Token’s Creator
In effort to remain fully transparent about the happenings behind the Lupecoin Project, we wanted to release this update regarding recent concerns that have been brought to our attention. These concerns came directly from members of our community in addition to a few well-known exchanges we submitted “Token Listing” applications to.
The following statement has been made by the creator of the original Lupe Chummies token:
Dear members of the crypto community,
As stated in our previous article, the Lupecoin Project started as a fun endeavor to shed some joy and happiness amongst “frens” on Twitter. I never expected it to gain so much traction so quickly and become something that many experienced individuals would rally behind to create something special. Initially, I set out to launch the token quickly in order to provide a tangible product that “frens” could begin to share for fun and spread the joy. Not knowingly, I created the token using a smart contract compiler code template that was outdated (for respect to other tokens that utilize the very same solidity contract, we will not mention the contract’s version). In hindsight, it was a reactive decision that if it had been done properly from the start would not have had the coding errors that it did.
As you know we’re walking on a more serious path now. Luckily, it has been brought to our team’s attention by both members of our community, and some well-known exchanges we submitted listing applications to, that there are some concerning flaws to our smart contracts coding (Please view the image below). You can clearly see and verify on etherscan, there are, indeed, some “compiler bugs” within our solidity contract. As one would guess, no respectable established exchange would want to have anything to do with a token that has bugs within its coding. This has obviously become a concern for our team, as well as those within our amazing community. As a result, we want to find a way to get rid of the flaws within the coding. We want to offer a trustworthy token that has great potential.
So how do we remedy this? What solution does our team propose?
I will always stay true to the original Lupecoin Project’s promise, which is rewarding our “frens” for staying the course, standing with us, and finding happiness among fellow “frens.” You gave us much joy and laughter and we all love and respect you for this.
So now, it’s time for progress. The inability to learn from one’s mistakes is where failure begins. But we’ve learned. Because of the mentioned past occurrences, I now have a clear understanding of what went right and where problems arose, which has enabled us to set a plan for course correction to create an unquestionably solid and secure token that will replace $LUPE. Going forward, this endeavor has evolved from “simply for fun” to becoming a legitimate token with real value. Since the inception of the Lupecoin Project, we have teamed up with experienced coders who have substantial amounts of domain and coding knowledge and are contributing their expertise and energy in order to be part of this project.
As stated, we are creating a new token with several significant differences from $LUPE. The most important is updating the code to a more secure and bugless solidity contract version (Please view the image below). Furthermore, the name and ticker will be slightly updated. Instead of Lupe Chummies ($LUPE) being the official token it will now be Lupecoin ($LUPX). The supply will be double from the original supply of 300M, set at 600M. The reasoning behind the increase in supply was to take into account any future developments of the project (i.e. exchange listings, dApps, future giveaways, etc.). In addition to our more secure and updated contract we have also included language within the coding that would allow us to “burn” $LUPX tokens should we find that the higher amount is not necessary.
Our supporters who received $LUPE will be getting a 1:1 airdropped amount in $LUPX. Following the airdrop you will be able to keep $LUPE simply for sentimental value, otherwise you will have the option of sending them to the following ETH Address to “burn” the supply: ENS-BurnAddress. If you have been waiting the last couple of weeks for an airdrop, we haven’t forgotten about you. We have your addresses ready to deploy the airdrop and will do so once the new token is ready and able to be airdropped.
These changes will allow for expedited exchange listings as well as allow a clean code to have utility with dApps built within the Lupecoin Project’s ecosystem. As a result of the flawed coding, we are also going to put on hold solutions to our Funds Safu ($SAFU) and our Space Force Coin ($SCF) tokens, which were also built upon the same outdated coding (Please view the images below) as $LUPE, so that we could focus on the most important of all tokens, $LUPX.
Side note: We will be outlining $LuPay’s solution to the compiler bugs flaws and announce it’s exciting and amazing utility in the coming weeks. Stay tuned!
In closing, we want you to continue to feel confident about the Lupecoin Project. We want you to “no be scare,” “no is worry,” and, most importantly, “be is happy.” We want you to have a token that has value, use case, and unique utility. We want to thank you for your love and support. YOU are the core of the Lupecoin Project, and our team will strive to deliver above and beyond your expectations!
From our diverse team of writers, coders, graphic designers, musicians, animators, meme artists, doctors, lawyers, military veterans, web developers, and crypto devs, we want to extend a truly heartfelt “Thank You.” We will be the hottest meme coin around! Here’s to learning from our mistakes and embracing this wonderful journey we embarked upon.
Upwards and Onwards!
Creator of Lupecoin
(On behalf of the Lupecoin Project)
