"I fuck people over. That's how it is. Well, not just 'people', but actual people, obviously, I fuck them over. I fuck over companies, suppliers, just like they fuck me over. That's the whole point."
@lambda0xE are you not tired of fucking people over?
FURY breaks native FHE on Octra's PVAC codebase.
Also breaks Multi-slot LPN, and their chain is AHE
The founder is a serial Russian scammer, with lawsuits against him for failing to repay debt and scamming investors.
What now?
Now blog. We figured this was obvious.
https://t.co/uVJCBvGtiB
(But updated this time)
Thanks to everyone who contributed!
This blog will serve as a response to @octra's team.
Alexey, don't come for me about "doxing," that's answered at the end.
@nuzmetra@te_mpe_st you're saying corporate shells, $40K cashed out to exchanges, paid Messari reports, and a fabricated surname don't matter. it matters to the 611 Echo investors and everyone who bought wOCT at $0.20.
I assumed there'd be some legal attacks on us. I appreciate not doing that.
1. I sorta figured such. The mismatch with the code was odd. I'll take the majority of this part as a concession. However, in regards to the webcli and pvac_hfhe_cpp, we DID mention those! See the first image. We refer to that in the blog by name! (image attached)
2. So I'll take this as a concession as well. Hopelessly outdated shouldn't mean it has the decrypt-compute-reencrypt flow. I would love an explanation on that.
3. So what happens after? I mean, this doesn't address the major hold over the supply the developers seem to have, no? This equally reads as a concession.
4. Thank you for admitting the UK R&D entity was yours. This confirmation doesn't seem to address Kirill Sencharov and his link to you, David.
5. Again, this just feels like a concession. Admitting your team members can easily off-ramp to fiat.
6. I would appreciate details on this "incident." Who was the counterparty? Why did it require an immediate transfer? The issue is that you could claim anything as an incident. It's a black box for us. It also doesn't really address why this took 2 minutes 36 seconds, a figure in the original blog. Who executed that multisig, by the way?
7. So explain the address clustering. At least give a plausible explanation, maybe? This also doesn't address the LinkedIn cached data, which proves a correlation to Octra. Even https://t.co/cadywhCHlL proves a link to Octra!
8. So it's a self-imposed lock. No programmatic lock (from what we've seen) exists. Team may not have access to any other OCT, however, they control the single validator. They can mint, modify state, and more. This was discussed in the original blog.
You've left many questions unanswered. This didn't address our main points.
Where does David Amishav appear outside of Octra?
Why do you commit to repositories under the name "K" in UTC+2/3, a timezone matching Estonia?
What are the actual hardness assumptions of HFHE?
Why won't you address the main glaring issues defined in the blog?
Also, because Alex decided to say we weren't interested in dialogue, we'd like to let you know that we are very open to an open-letter style debate recorded on https://t.co/7yWjLrwRr1!
Funny story. Tail suggested I add an appendix debunking claims of doxing.
Fuck it, I'll debunk it here.
Firstly, we did not reveal anyone's non-business addresses. We revealed only what was strictly necessary for OSINT purposes. Doxing, as I see it, would require a motive of garnering harassment towards the doxed. This is not what we did.
As I told Lambda, we don't omit the two repos. We mention them by name. Sorry.
But please, Alex, tell me how exactly we were ignorant on blockchain functions!
Did you even read the blog?? Us tracing businesses across countries does not constitute as "dox attempts." If you'd like, I'm happy to have people who have experience in OSINT affirm my claims.
You pulling a moral trump card out of your arse is fucking infuriating.
We looked into @octra. We didn't find very good things!
From our eyes, Octra might just be a rug. Please read and give your thoughts. (P.S. @Bybit_Official and @binance , you should read this. They used your services.)
https://t.co/uVJCBvGtiB
@Hacker0x01 You should really look into your analysts, they're incompetent at best, and extremely stupid at worst.
Wouldn't be surprised if some of them turn out to be deliberate threat actors closing reports so they can leverage the vulnerabilities for themselves.
This is just straight bullshit to scare stupid iranians, heart does have an electromagnetic field that could be measured with an MCG, but it's indistinguishable from zero at 64 KMs because of the inverse cube law of magnetic fields, absolute horsecrap
NEW: The CIA used a secret tool called "Ghost Murmur" that uses AI to find heartbeats to rescue the U.S. airman who was stranded in Iran, according to the New York Post.
The secret technology was allegedly used for the first time in the field, according to the Post.
"The secret technology uses long-range quantum magnetometry to find the electromagnetic fingerprint of a human heartbeat and pairs the data with artificial intelligence software to isolate the signature from background noise," the Post reported.
"It’s like hearing a voice in a stadium, except the stadium is a thousand square miles of desert," the source said.
"In the right conditions, if your heart is beating, we will find you."
"The name is deliberate. ‘Murmur’ is a clinical term for a heart rhythm. ‘Ghost’ refers to finding someone who, for all practical purposes, has disappeared..."
"Advances in a field known as quantum magnetometry, specifically sensors built around microscopic defects in synthetic diamonds, have apparently made it possible to detect these signals at dramatically greater distances."
CIA Director John Ratcliffe appeared to hint at this technology on Monday, saying the CIA possessed "unique capabilities" but said he couldn't "tell you everything that you want to know."
President Trump also revealed during the press conference that the CIA spotted the officer from about "40 miles away."
Insane.