STR1P3
2.6K posts

STR1P3
@STR1P3_e
In Crypto since 2015 | Still have no idea what's going on | Futurist









@marcobrondani SUDDENLY?! You speak as if you weren’t around for the years the community had been pointing out every detail that would lead to precisely this outcome.






Dear @alexsmeelenz VP nepo-clown show Came out for an encore wETH it all as you wash millions of tokens from kucoin to mexc Even @thinkagents, aka not not ASM Truly the worst







(2 left) This was the most stressful day of my life. ((This is a 2-parter, see my comment in the thread for part 2.)) In the weeks prior, every single person on our team had multiple attempts at breaches of all of our personal devices and social accounts. We met to make clear that no links should be trusted. The day before launch, we were rushing to complete the pre-reveal asset. When it was done, we sent it to Jason (CTO) to implement. We were expecting the Blaze team to do the contract. We later found out that Jason had debts with them, and to cut corners, he instead had his right-hand man, Saravana, make it. 1st mistake. Saravana, instead of being a gud solidity dev, used the OpenSea template contract to save time. The contract was secure. But because Jason was worried the large (2,000+) allowlist would make gas expensive if it was coded into the contract itself, he used a webservice that the contract communicated with to allow allowlisters. 2nd mistake. Jason greatly underestimated demand, and the attention we had drawn. But ultimately, I was the CEO, and I took responsibility for the decision to move forward, not fully aware of what might happen. In the final lead-up, I was speaking in a Space with Accelerate Art. Their team is basically “the” cabal, if there ever was one. Just before I got up to talk, I got a message from Jason. Our site being DDOS’d. He quickly put a fix in. As I got up to speak on the Space, the mint began. I was distracted, refreshing the mint count constantly. Immediately, it started FLYING. My phone was blowing up, at first in celebration. “Dave” then got into the Space and on stage. He spoke and immediately began harassing me. We were at 1,000. 2,500. 3,500. Then Jason realized what was happening. Panic. I jumped off the Space. We pulled the plug after ~5,500 mints were taken, subverting the allowlist, giving access to free mints. This all happened in the span of 5 minutes. The secondary market flooded with below-mint prices. It all happened so fast. We were cooked. A deluge of messages in Discord struck. Many bots and new faces. We were being ridiculed relentlessly. I remember MaxPoker and Somnium mocking us in our Discord, referencing “buttered toast” and tools. I found the main party responsible for the swarm of mint-botting tools, and confronted their lead. He encouraged even more people to agitate us. Jason called me. He tried to prime me for even worse news. Few people knew about this, because I wanted to hunt the perp. A hacker going by “Oscar” had infiltrated Saravana’s computer, and hijacked our contract. He wanted a ransom of ~2ETH to give it back. We paid it, and luckily, got it back. I took control of it personally and quickly changed permissions and the royalty fee destination. We called around to get any advisors we could to help us figure a path forward. We asked Jason to give us discrete details on what just happened. We hosted another Space to announce everything. On that space, the lead from the mint-botting tools group came on. I was still so frazzled. But for years, I have sat with this BIG question mark. This guy, “Zion” (NFT Sensei), a New Zealand dev, felt compelled to chest-pound about their stolen mints and say it would allow his people to buy McDonald’s. Video below. Jason was asked to step down, but fix the mess first. We fielded hundreds of service tickets and manually verified and airdropped over 1,500 Relics to those who were supposed to receive them. Jason paid the fees. Blaze made the swap contract and the V2 contract. The damage was done. But we did keep going. After the mint incident, Alex reached out. He sent me a breakdown from their CTO to tell us what went wrong. It was kinda “loaded” at times. They also waived the $75k investment. We continued to pay it anyway. This loaded post-mortem was leaked to someone in our team and circulated before we could even meet and go through it. Alex insisted it was kept to only a few parties. (see below)












