# End of Phase II

**Published by:** [QuickFinch](https://paragraph.com/@quickfinch/)
**Published on:** 2022-05-04
**URL:** https://paragraph.com/@quickfinch/end-of-phase-ii

## Content

-The day this article is released, 1st of March ,marks the launch date of our new smart contract and token. The hard work of our development team is coming to fruition, and with this we thank them for it. In this article we will dive into the most prominent features we have implemented; how to claim the new tokens; links to our official sites that contain detailed information; and some future developments. As mentioned in our previous article, the Journey of Phase II — continued, a snapshot of all the addresses holding any amount of our current old CYBR tokens was taken. The new CYBR token, that utilizes our new smart contract, was airdropped to all holders in that snapshot. For more experienced users using a MetaMask wallet, simply copy and paste the new smart contract address, using the “import token” on the Ethereum Main-net. The address of the new smart contract token 0x438a6e42813118548c065336844239b63ad4fcfd. For beginners, refer to our step by step process pdf with pictures that explain each step in detail. If you are having troubles, feel free to join the Discord and ask for some help. Be aware that the old CYBR token will still show in your wallet, with the amount you had prior to migration. This amount of CYBR will monetarily be worth nothing after the liquidity has been migrated to the new token. Think of it as a reminder of where we all came from, and how far we’ve come. Cheers! Our new smart contract is not like any other you have seen for a project this size. We are very proud of what all we have accomplished, again thanks to the dev team. We managed to add all of the functions we had planned to incorporate and more. We designed the contract with a large scope of utility for both the current features and future one. By already implementing functions that we will be utilizing down the line, we save costs and headaches in the future . Like for example, our Polygon bridge function which will allow us to ultimately act as the primary L2 for CYBR as of now. We truly do not want to limit ourselves in functionality and interoperability, to expand Cyber Enterprise all the way… well you know… up there…1 Contract Read Functions: Cyber (CYBR) Token Tracker Reads| Etherscan Contract Write Functions: Cyber (CYBR) Token Tracker Writes| Etherscan Our contract includes several features, like blacklisting, bot mitigation, liquidity pool support and token burning support. By support functions, we mean functions that enable us to do so and be transparent in what goes on behind the scenes. Because as functions in our smart contract, they are publicly accessible to our users via Etherscan, and any changes emit a viewable event. We will have a brief overview of the most prominent functions here, but a more detailed description can be found on our “Contract Explanation pdf”. Additionally, we have ran over 30 iterations of contract testing. When it comes to security, we take it very seriously. That is why we spared no time when it came to eliminating potential misuses of our smart contract. We value the investment of our community, and will take no risks in this regard. Multiple scenarios of potential misuse were recreated. In testing the bot mitigation, blacklist, and other custom functions, all went as planned. As of today, after a successful migration of funds and reallocation of CYBR to all holders, we are now an authentic UniSwap V3 pair. As of writing this article, March 1st 2022, neither UniCrypt or TeamTrust by Trust Wallet have developed a token locker for UniSwap V3 liquidity pools. There is currently no locking method for UniSwap V3 pairs. That being said, the are under development and hopefully coming in the following months. Locks are done differently on Uni V3, as they are no longers ERC20 LP tokens, but rather erc-721s provided by UniSwap. That is the one major difference on how UniSwap V3 works in comparison to V2. CYBR ERC-721 Liquidity Token: https://etherscan.io/token/0xc36442b4a4522e871399cd717abdd847ab11fe88?a=198702 As soon as a reputable company develops a way to lock ERC-721 LPs, we will abide and follow suit. We have even pondered the thought of developing our own method of locking, but for now it’s locked in Odysseus’s gun safe. Those of you that have been with us since the start of the journey, and those of you who are new, will see we the Cyber Team have nothing but the best intentions for this project, for our community. We have so much to show, to do, and to accomplish. An odyssey of a lifetime is what we’re aiming for, not a shipwreck. CYBR ERC-721 Liquidity Owner: https://etherscan.io/address/0xf273aec6fbdc2920afa7425ece575a432fd0844f I, Odysseus, would like to thank everyone for allowing us to take the extra time to develop the contract and create something truly special. I would also like to thank the community in entrusting us with the liquidity migration and reallocation of the new CYBR token. I also appreciate community member Vito Luciano is stepping forth, and taking responsibility of the Medium (: CYBR Under Construction Website: https://thecyberenterprise.com/ CYBRC Website: https://thecybercreditors.com// Youtube Channel: TheCyberEnterprise — YouTube DexTools: https://www.dextools.io/app/ether/pair-explorer/0x367340c85e1fde271506ccda21a424f9fbde8d9c Contract: 0xd409bb122cc1cdaa5c1530f1e7ff1512345477b9 OpenSea: https://opensea.io/collection/cybernators-2026 Discord: https://discord.gg/thecyberenterprise Telegram: https://r.cybr.army/telegram-en Twitter: https://twitter.com/thecyberinu Medium: https://thecyberenterprise.medium.com New Reddit: https://www.reddit.com/r/TheCyberEnterprise/ Old Reddit: https://www.reddit.com/r/TheCyberInu/ Instagram: https://www.instagram.com/thecyberinuofficial/

## Publication Information

- [QuickFinch](https://paragraph.com/@quickfinch/): Publication homepage
- [All Posts](https://paragraph.com/@quickfinch/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@quickfinch): Subscribe to updates