Resilience — In the Face Of — Adversity
The Uramaki journey has been in the works for quite sometime by a highly experienced and visionary team in the crypto space, The MAKI Team.
The team at Uramaki kick-started the MAKI movement; of which broke through all stats and milestones that were initially set out, and within a matter of 6 days only — saw substantial and unmatched rapid growth on multiple aspects; Twitter, Discord, White-List and Airdrop participants, in preparation for the Uramaki launch.
The experience for both the community and the team alike, was nothing short of Glorious.
But even with the most experienced, proven record, reputable, heavily funded and venture-capital (VC) backed startups in the space; security breaches do happen and they happen often.
Security breaches are more often than not so damaging that it takes the project / business to a complete shutdown due to the inability to withstand such a technical, reputational, emotional, let alone the financial burden that comes with it too. We’ve seen this happen many times with other protocols and projects, the most recent unfortunate instance was with Alliance Block yesterday with a hacker exploit that brought the entire protocol to halt. Trading included.
Sadly, we caught ourselves in a similar situation during our initial launch process. A security breach caused the Uramaki project to halt, only mere minutes after launch.
Background: During our initial testing rounds, the team opted into improving a dApp feature functionality and planned to have it ready for launch. With the crunch of time left to launch, this objective necessitated the need to bring in a 3rd party Dev (referred to as 3dev from here on out) to assist with couple of auxiliary front-end tasks.
The security breach took place when 3dev was accidentally granted access to a production virtualized-servers farm — via incorrect cloud access-permissions — that contained sensitive information, i.e private keys. The server(s) otherwise are protected behind multiple firewalls and unreachable to the public world.
Given the front-end & dApp errors and issues that occurred at launch, we expected a malicious act was being carried out since our final testing rounds cleared all issues. By the time we realized what was happening, the 3rd party Dev (3dev) had beaten us to the LP / Treasury and the rest is history.
Sad, disappointed, devastated, ashamed, you name it, the Team was pretty much on the same sinking boat as the community, and it was disastrous.
It is however our responsibility, and our responsibility only.
Take the easy road — and give up, or live up to our core values — both as individuals and collectively as a team — to get back up, show our resilience in the face of adversity, pull all the available resources and put in all that it takes, to move forward and onward with our original plans.
The MAKI team sees the immense potential in this community, alongside the protocol, and will not let your collective efforts, combined with ours, go to waste.
We promised, and it is one of our core values that we live up to our promises.
All funds necessary to properly relaunch MAKI and make everyone whole — 1:1 of funds — including LP and Treasury, has been secured and funded by the Uramaki Team.
As the relaunch funding has been secured, We now can concentrate on the subsequent & crucial tasks:
- Preparation & Development of New Protocol Contracts
- Extract the necessary data needed for the airdrop of the new token.
This is quite a complicated and lengthy process, where we figure out the eligibility criteria based on multiple different factors and processes:
- The Snapshot taken at the moment of LP withdrawal (https://arbiscan.io/tx/0x0c092c139d5eea203a52496e9161a01f46d2bba8d5389e7b3c2c7c3f87172faf.
- Unclaimed Public Presale tokens
- Unclaimed Private Presale tokens
- sMAKI stuck in the warm-up contract (staked MAKI)
- Bonds eligible for MAKI vesting (requires a new vesting contract)
- Vesting of Private Sale (requires a new vesting contract)
- MAKI Holders
- sMAKI Holders
Any trading / transfers that took place after the malicious LP withdrawal, will not be looked into or considered. This is common practice since the LP post the incident was not provided by the protocol or the team.
3. Thorough Testing Protocols of all new contracts to ensure an absolute flawless relaunch.
The above process is rather a lengthy process and will take time. Even though we’re headed in the right direction, there is still a lot of work to be done before a viable relaunch takes place.
We also would rather have a flexible operating window than a fixed date to relaunch, and expect the window to take around 3 weeks, give or take.
The majority of time will be spent on improving our overall security protocol, test all contracts, stress test the front end and ensure our relaunch will be as flawless and secure as humanly and technically possible.
We will revisit the relaunch timeline during the last days of February, and likely will have a clearer picture of progress and readiness to announce a relaunch date.
We stated numerous times that we’re just getting started, and if anything, where we are today and the content of this medium article proves just that.
We are just getting started. Everyone will be made whole — MAKI Lives On.
Together, we will get through the adversity and only become stronger than ever, both as a team and as a community — The MAKI Army.
Now let’s all get back to work, and push MAKI to where it belongs. The MAKI rebirth isn’t “simply” about making you whole, it’s about a complete reset and the march to success from scratch again — yet more secure coupled with an even deeper and stronger belief, in the Uramaki future.
As we prepare for The Uramaki Rebirth, progress updates will be provided.
-The MAKI Team
- Website: https://uramaki.io
- Twitter: https://twitter.com/Uramaki_io
- Discord: https://discord.gg/uramaki
- Telegram: https://t.me/uramakianns
