Basic Security Information
Team Information Below, Keep Scrolling for Security Features
The core team of contracted developers has chosen to remain anonymous to the public at this time, but we have doxxed with one another before launch, and have set up a number of security features that we believe will generate trust from token holders:
● Good Code: Our code is transparently placed on GitHub and audited available for you to review;
● Migrator Code removed by safeowner (read below);
● Time-Lock on Masterchef Contract (6 Hours) (read below);
Audits: TechRate and Hashex, considering others. Audits don’t make a project safe, but they show good-faith effort by developers because audits cost money and time. We will also welcome community audits through active crypto community voices and plan to acquire a few of these.
emergency withdraw feature (in case of DDOS attack)
Multi-signature treasury wallet and developer wallet
● KYC with selected firms and/or exchanges;
and eventually
● Community Governance (eventually) to further de-risk our platform

Why Anonymous Team (we know, it sounds bad)

While a generally accepted practice in DeFi, anonymous teams create a risk for all parties involved, especially end users of tokens. Many rugged projects have anonymous teams which allow them to act in bad faith toward their token holders without risk.
At the same time, our team knows the unique problems facing developers and see the risk doxed devs carry as a result for their transparency. There is no simple solution. Anonymity allows us to really rely on the strength of our code, added security features, and decentralized efforts, while protecting our personal lives from being harassed by some of you unsavory folk (you know who you are).
It also requires that token holders do their own due diligence and research before buying or selling in a risky market like cryptocurrency.
Members of our team have KYCed to members of the media for publication, and all our longterm contract developers are KYCed using blockpass. You may have to take our words for it, but we are concerned about security more than you :)

How Many Are on the Team?

Our team is a combination of core contracted developers/founders, contract workers, community leaders, and YOU! RugZombie is a defi project that fair-launched. Our project is for the community!
Our "core" dev team has multiple members currently, and we are actively adding more as our project grows. Only one member has access to the deployer wallet, and a few founders have access to a multisignature treasury.
We have a number of community leaders and experts who actively manage our socials, SEO and web traffic, marketing, partnerships, design and other efforts.
Interested to join our team? Click Here.

What About all the Other Contract Features?

There are a lot of contract features that certain defi projects have eliminated or locked upon launch. They do this to give public assurance that they are not a scam. This is admirable, however, these features are in the code for a reason and to eliminate them or lock them comes with significant drawbacks.

Migrator Code (moved to safe-owner contract)

For instance, goose finance was the first to remove the migrator code on the BSC. This feature allows for upgrade in the future of a project, and removing it is basically like saying a project does not intend to upgrade to a future version. Our project is a long term project, so we are doing what is best for the project, even if it goes against the norm for new BSC projects. Other notable projects that have kept this code are Pancakeswap and Sushiswap.
After community request and careful review from our devs, we are implementing a safe-owner contract on our Migrator Code to deepen trust in the public around our project.
The drawback of removing this code is that migrating to new DEX must be a manual process.
This safe-owner contract can be found at THIS LINK.

Time-Locked Masterchef

We have implemented a 6 hour time-lock on the masterchef (dr. frankenstein) contract. The contract can be viewed HERE.

Locked Liquidity

Locked liquidity and burned liquidity addresses left an entire generation of projects on v1 of pancakeswap. We don't intend to limit ourselves in this manner by burning our liquidity wallet.
At the end of the day, community trust and confidence are important to us, but so is doing what is right for the project. We will not add/remove features that will prevent future growth because early token holders need assurances.
We currently do not have locked liquidity, but plan to lock it at the appropriate time. Please note most of our LP is community provided.
We expect our community to do their own research and due diligence. If you are uncomfortable with the features in our code, you do not have to be involved in our token. No one is forcing users or token holders to participate. At launch we deliberately chose to not lock liquidity for some development related reasons, such as moving our Liquidity to major exchanges, etc.
Last modified 3mo ago