NotoriousPtG

2.7K posts

NotoriousPtG banner
NotoriousPtG

NotoriousPtG

@NotoriousPtG_2

Account for posts by @NotoriousPtG

Katılım Ocak 2025
1 Takip Edilen57 Takipçiler
Sabitlenmiş Tweet
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
Starting in Jan. 1, 2025, @NotoriousPtG will post from this handle. This handle will follow very few other accounts. I read the posts of the accounts I follow on my original handle.
English
1
1
9
3.6K
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@LidoFinance Will you stop collecting fees on profits to make up for the haircut?
English
1
0
5
665
Lido
Lido@LidoFinance·
1/ On April 18, an attacker drained 116,500 rsETH (~$292M) from Kelp's cross-chain bridge. rsETH markets on Aave and other lending venues were frozen shortly thereafter.
English
29
47
324
117.7K
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@airbrown79 SCIF was not a central part of my claim. My central claim was that classified info is not leaking en masse to foreign nations via smart monitors. Even if they exist outside of a SCIF, classified networks are not connected to the open Internet.
English
1
0
0
15
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
That’s irrelevant. Palmer’s contention was that “unbelievable amounts” of classified information is being leaked to foreign countries through smart TVs/monitors. So the issue I was addressing is can classified info lawfully be viewed on a smart monitor connected to the open Internet.
English
0
0
0
19
Owen Stone
Owen Stone@battledoge69·
@NotoriousPtG_2 @smuglydismissed You have moved the goal post. Your OP said it needed to be air gapped which is factually incorrect. SIPR is not an air gapped system. But classification works in levels. Some information may require that level of security but almost all of it does not.
English
1
0
1
13
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@gridpane @PalmerLuckey @anduril @Jason Actually we had some good back-and-forth. And lots of people made substantive comments. Learned a lot. Is “dumb dumb” the level of your everyday vocabulary?
English
1
0
0
471
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@PalmerLuckey 🤝 All for solving any leaking that is happening to the detriment of national security. And commercial trade secrets would be vulnerable to this leak vector as well.
English
0
0
1
119
Palmer Luckey
Palmer Luckey@PalmerLuckey·
@NotoriousPtG_2 Okay. In the real world, almost all mishandling of classified information by government and industry is accidental, and I care more about solving that than pointing at a rulebook and insisting it doesn't actually happen.
English
1
0
11
459
Chris "Brutal American" A.
@NotoriousPtG_2 You're mixing statements, requirements, and regulations either to purposely obfuscate or because you have no clue what you're talking about.
English
1
0
4
89
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
I doubt that is happening en masse. There are severe consequences. If happening at a defense contractor, the company can get barred from being granted future government contracts and the individuals can go to prison. Again, no issues with the contention that sensitive unclassified info may have some exposure to this leak vector. And aggregation of unclassified info can become classified info.
English
0
0
0
50
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@PalmerLuckey Yes. I’m not including illegal behavior that can land you in prison. No issue with your point about sensitive unclassified information (and even risks to commercial trade secrets).
English
2
0
0
442
Palmer Luckey
Palmer Luckey@PalmerLuckey·
@NotoriousPtG_2 This new argument is only true if your definition of "can't" is "you aren't supposed to do it"
English
1
0
13
400
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@aqua______regia @smuglydismissed OK, fine. Also, I’m not denying that sensitive unclassified information that can be exposed to the open internet can be aggregated into classified info.
English
1
0
0
40
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
Whether or not it was a hack of Aave doesn’t matter at all. In the end, Aave users are going to lose money. Aave marketed its multi-collateral nature. Its community owns the fact that one of the collateral types had a security hole.
Nicki Sanders@nickisanders

There’s been a lot of talk about “Aave getting hacked” over the last 24 hours, but that’s not actually what happened. The root issue was a ~$290M exploit on Kelp DAO’s rsETH bridge, where an attacker was able to mint or steal a large amount of rsETH and then use it as collateral across DeFi. That’s where Aave comes in. The attacker deposited that rsETH and borrowed over $200M in ETH against it. Once the exploit became known, that collateral was effectively worthless, which created massive bad debt across the protocol. Aave itself wasn’t hacked. Its contracts held. The issue was what was accepted as collateral and how risk from one system can spill into another. This is the part people tend to miss. DeFi doesn’t break in isolation anymore. A single failure, like a bridge exploit, can cascade into lending markets, liquidity stress, and emergency freezes across multiple protocols. We’re also seeing this right after the Drift exploit earlier this month. Different root causes, but a similar pattern: composability means shared risk. The takeaway isn’t that Aave is broken, it's that bridges remain one of the weakest points, collateral assumptions matter as much as code security, and risk doesn’t stay contained the way people expect. DeFi is getting more powerful, but also more interconnected, and that cuts both ways. How do we move forward from this?

English
0
0
2
593
NotoriousPtG
NotoriousPtG@NotoriousPtG_2·
@DMHandy1984 @RacerTimC @Jason It sounds like you agree with me (and disagree with Palmer) that “unbelievable amounts” of classified information is NOT being leaked to foreign nations through this channel. Sensitive unclassified information may be exposed to some extent.
English
1
0
0
64