Be sure to follow us on our social channels:
Medium
Telegram
Telegram Official Announcement Channel
Github
Official TOKEN ADDRESS
We try to avoid making noise about small changes (that can be more confusing than helpful for the public) , but this one we had to declare before we launched in the interest of transparency and increasing user trust:
Our token contract address has changed from our first audited contract address.
This does not (and did not) affect you in any way, as no one currently holds any $ZMBE token. However, this could have been a suspicious change if you have been watching out github repo and checking our token address to whitelist before we launch. (We hope all of you are doing your due diligence with every project.)
The old and unusable contract addresses are listed on our gitbook documentation HERE.
The correct and OFFICIAL TOKEN ADDRESS IS 0x50ba8BF9E34f0F83F96a340387d1d3888BA4B3b5
What Happened?
Upon pairing the front end and back end for integration, our main backend dev noticed a small unintended feature in the original token contract.
The noticed feature was that the "unlock grave function" called a method that withdrew BNB to the treasury but withdrawing BNB to the treasury was originally a function that could only be called by the contract owner. So it worked when our main dev tested the feature, but did not apply to anyone else testing the feature. This small unintended feature needed a quick tweak before we launched, lest our team not recover the BNB that needed to sent to the treasury address upon calling the unlock grave.
What We Did to Resolve this Issue
The issue has been resolved already and the contract redeployed. You can see the changes below.
Our team has submitted this change to Techrate for an update to our original audit and expect them to make the necessary changes when they get to it. See our original audit here.
Nothing within the contract has changed, but for peace of mind, please see the below for a reference. (Please note our masterchef is called "DrFrankenstein". We like to party and have fun.)
As you can see above (please also check the github repo for our old contract AND the new OFFICIAL contract below, along with our full techrate audit report), there has been no change to the logic of our contract in any substantial way. We have provided a link to our gitbook above with both the contract sections, which you can cross reference with our live github repo if you are concerned about this change.
As there is no substantial change to our token contract, we do not seek to get another audit at this time until we begin applying for Certik, since techrate will be updating their audit to our new contract and the change is minor.
We have updated all our gitbook, github repo and linktree accordingly with the correct token address information and will state the old one in a "strikethrough" token and is not our official token.
Our OFFICIAL TOKEN ADDRESS is0x50ba8BF9E34f0F83F96a340387d1d3888BA4B3b5
What It Means For You
As stated above, our token has not been launched with any liquidity so therefore this change means very little to our future users and token holders. We offer this update and announcement as means of being transparent and on the record about how hard our devs are working to ensure we deploy a safe and secure contract.
We do not anticipate any unforeseen issues here. Please mark the OFFICIAL TOKEN ADDRESS and see our forthcoming token information release statement with full tokenomics and basic information, along with our forthcoming LITE PAPER.
ZOMBIE ON!
Welcome to RugZombie - An Overview
Utility = Value (and why RugZombie Team are builders)
RugZombie - The Problem & The Solution
RugZombie - Main Features (Part 1)
RugZombie - Main Features (Part 2)
Security and Scams (Part 1)
Common Questions and Answers
The information shared in these docs, our roadmap, our lite paper and white paper, and social channels such as this blog, is not financial advice and should not be misconstrued as such. The primary purpose of these documents is to provide potential token holders with pertinent information in order for them to thoroughly analyze the project and make an informed decision. Engaging in cryptocurrency projects involves substantial risk and it is strongly advised that you consult with a financial professional prior to your participation.
These documents do not constitute a prospectus or offer document of any sort and is not intended to constitute an offer of securities or a solicitation for investment in securities in any jurisdiction.
Neither RugZombie nor any of its contributors or creators shall be held liable or responsible for any errors or omissions concerning this project or for any damage you may suffer from your participation or as a result of failing to seek competent financial advice from a financial professional. This white paper is not in any way intended to create or put into implicit effect any elements of a contractual relationship.
