Not even going to talk to khaleelkazi for at least a couple days. Not even going to tag him in this post. Guy has been going 100% for weeks working on this thing, and the damn plane has crashed into the mountain.
Oh no!
Who's fault is this!?
This is not a question that matters much at this point.
What are we going to do about this?
Postmortem
Hacker got like...
The wLEO side doesn't matter.
wLEO is dead.
At least this version of it anyway. The only way forward from here is the decentralized solution that we waived to get farther ahead... oops. This means we'll probably have to airdrop the dev fund (5M coins) onto those ~800k coins that got diluted and destroyed on wLEO after the hack.
Still leaves the ETH side.
This is the problem, because we can't print ETH. I hear money was transferred to a Binance account, guess what else I heard?
The community321 account trying to make a fake transaction of 1M coins to the @wrapped-LEO bot?
https://etherscan.io/tx/0x347ac7badadd741643a2db1c148f08523c78c05468e121f7edd795d2a6ec27b1
An Ethereum transaction to create 100M wLEO?? Weird.
There's a lot of evidence I am not sharing.
This clusterfuck needs time to resolve, in one way or another.
Give the Founders & dev team the time to put something together.
Lots of weird evidence out there and random accusations can be made.
Let's try to avoid that and just give the situation a couple days to unfold.
I hear khal printed fake wLEO to save the remaining 120 ETH in the pool.
We'll get the official numbers later.
My take on what happened here will be omitted for the time being.
Just remember, this hack is a matter of stolen Ethereum .
LEO is pretty much #safu in this situation.
I keep wanting to say more but it can wait.
I'll just kill it here.
Woah, not that I hadn't had the thought. But to see it like this is surreal, even for me.
Shit just got serious..
Sad to hear that wLEO won't recover from this.. At least as it was. Even scarier to think who's behind it, if this turns out to be true..
It makes me angry when bad people ruin the work of good people.
It makes me especially angry when bad people ruin the work of good people on multiple occasions.
This is why we can't have nice things, friend. :D
:(
Looking forward to when you have enough evidence to write a full exposé.
Write the original from the leofinance.io domain and send all of that juicy traffic back.
Posted Using LeoFinance Beta
@community321 is not owned by STInc, it was created by someone random appears to be created by @bdvoter - no relationship to Steemit at all, probably someone thinking that was the bug and trying to cash in on the action.
correct (although I tried to send the funds to a burn address, so I wasn't really trying to "cash in")
just logged into this account (wow 112 notifications) and yep I'm still owned by @smitop
The attitude from this post should be for anyone that joined this project long before wLEO or at least not for that. At the moment the best weapon is patience and we need to let the LEO team address the issues first and than talk to the community.
LEO is here to stay and those deserving will thrive in the end!
Posted Using LeoFinance Beta
Hi there @patrickulrich, @edicted. I control @community321 on the Hive chain. I do not, and have never, controlled it on the Steem chain. I am not related to Stinc in any way.
Explanation:
I was on Twitter, and heard something bad was going on with WLEO involving a security issue. So I figured I'd investigate, and see if I could figure out what happened. I used @community321 to sign the transaction since I already had it setup on the device I was using. I tried just trying to trick the server into sending tokens to the burn address (notice the address in that tx is 0x00...), to try to see what the issue was. AFAIK my attempt failed (perhaps because the server was shut down before it saw my tx, or perhaps the security issue was something different).
Ha yeah sorry I threw your name out there as a Red Herring because other evidence was looking quite bleak. In no way, shape, or form do I think your account had anything to do with the hack.
wtf - that is a stinc (steem witnesses) account now, right?
Posted Using LeoFinance Beta
There's so much weird evidence out there I'm not even speculating yet till I get more info.
crypto people are tiring - if more time was spent on building the industry instead of scamming it, we'd all be doing well.
Posted Using LeoFinance Beta
No.
Cool.
Usually when a business or a project gets a hit from a cheap shot like these two things can happen.
You Die, or you Try.
If you try and you handle it well then you get out of the situation :
Leo got some very nice leadership and Hardcore members.
I see Leo survive and get stronger from this, and I am not saying this as a catchy phrase of pointless optimism but as a prediction.
Now about the dirtball who stole 100k+ well scammers and this kind of prics got a special place in space hell.
It just leaves me with a sour taste in my mouth that this industry so often seems to have just as many people who want to scam others as it has good people who authentically want to build something.
It's bad for LEO and TeamLeo... but it's also bad in the sense of perpetuating an image of the cryptosphere as the domain of hackers and scammers.
Some of the things you allude to here are very interesting... look forward to future installments!
=^..^=
Posted Using LeoFinance Beta
You've sucked me down a rabbit hole.
The Hive @community321 claims to not be the same @community321 from JS and co. Instead it was claimed by that account to be @smitop. I've yet to find confirmation from the @smitop account though they've also not been active since.
The community321 account is a total red herring imo.
I just threw it out there because it was a safer thing to say than what other evidence points to.
In my opinion this dents a whole lot of trust and psychological cripples the growth of Leo. It's coming at a time when leo was making headways and so many listing is starting to take place. This is hurting but hopefully it can be resolved really soon.