
LIMITLΞSS 🐺👑
13.4K posts

LIMITLΞSS 🐺👑
@goodguyaugust
Pod soon 🎙️ Legal matters ⚖️ Crypto OG (2016) 👨🏾💻 Former Intelligence 🐿️ Real Estate Investor 🏘️ Top 1% Sportsbettor 🏈





Sorry Oregon fans, people like baseball games where people show up. God knows there would be a total of 15 people at games if they were held anywhere on the west coast


It’ll be No. 1 UCLA vs. No. 3 Oregon 🍿




🇪🇺CBMT is advancing forwards in the EU We just saw Siemens the FIRST CBMT transaction CBMT was initially tested in Germany with banking giants The infrastructure was made possible thanks to Oracle And as we know... Oracle's DLT offerings are made possible thanks to $QNT



Pyth Network Suffers Hermes and Core Feed Downtime Pyth Network reported an outage affecting Pythnet/Hermes, disrupting its core price feeds and sponsored feeds for over four hours. The team said validators are coordinating a restart after identifying the root cause of the issue. The incident may affect DeFi protocols relying on Pyth oracle data for trading, lending, and liquidation operations.






We’re sharing our completed post-mortem on the April 18th incident, prepared with @Mandiant and @CrowdStrike. We are publishing both an executive summary and the full report at the link below. Over the past four weeks, we’ve worked with hundreds of partners to help them understand their current security posture, and harden it where appropriate. We’ll continue this work, alongside taking additional proactive steps for the benefit of not only our partners, but also the ecosystem as a whole. We want to extend our thanks to our partners for their support and patience this past month. There’s a reason that over $12 billion has moved across the network in the past four weeks, and why the world’s most valuable asset issuers have stood by our side: they believe in us, in what the LayerZero protocol has to offer, and in the value of modular, isolated, application-controlled security. The work continues. And we look forward to continue showing up for the applications that trust us with their business, as well as the broader ecosystem. layerzero.network/blog/layerzero…

Today we announced progress toward our goal of advancing 24/7 collateral mobility. DTCC’s Collateral AppChain, a shared infrastructure platform for collateral, will leverage the Chainlink Runtime Environment (CRE) and @chainlink data standard to enable near real-time collateral management across financial markets and blockchains. The integration will enable the seamless pairing of asset prices, valuations, and movement, with the aim of overhauling how market risk is managed globally and unlock greater capital efficiency. This milestone reflects our broader vision to enable 24/7, near real-time collateral management across the global financial system. Read the full announcement: dtcc.com/news/2026/may/…



New post mortem confirms what we already knew: @LayerZero_Labs' centralized infrastructure was infiltrated by North Korean hackers, which resulted in the $292 million rsETH bridge exploit Turns out this required only a single engineer to be socially engineered, whose laptop was fully compromised for over 6 weeks without detection before exploit was executed, an insane single point of failure and lack of adequate monitoring This only builds on LZ Labs' extensive history of poor opsec, including trading memecoins like "McPepes" on production multisig keys, which weren't rotated for years and Bryan lied about and said was just "PEPE OFT testing" (3 keys on a 2-of-5 LZ Labs multisig were at risk of phishing attacks for years) And nevermind the fact I called out the EXACT centralization risk that resulted in the rsETH exploit 2 years ago, directly to Bryan, who lied and said no project was using LZ Labs DVN in 1-1 config (in reality, multiple projects were) Given it's now abundantly clear to anyone paying attention that LZ Labs' poor opsec was the root cause vulnerability in this situation, but its not clear to me why exactly LZ Labs is not footing the entire bill of the exploit given it was their infra that was compromised, which was used in a config they actively supported and monetized for years Furthermore, LayerZero's extensive roster of VC backers have been awfully quiet during this whole incident, not contributing a single dime to the rsETH recovery fund, despite funneling more than $300 million in funding into the infra that was compromised, including a raise just a few months prior I don't want to belabor the same points again, but I am so fucking tired of pointing out the risks of centralized, insecure VC-slop infra only to watch it inevitably get hacked and destroy DeFi’s reputation in the process This entire situation could’ve been avoided if people had just listened to the warnings that I and many independent security researchers have shared over the years about LayerZero We, as an industry, can do much better, I'm glad to see high quality teams migrate to secure-by-default infra








We’re sharing our completed post-mortem on the April 18th incident, prepared with @Mandiant and @CrowdStrike. We are publishing both an executive summary and the full report at the link below. Over the past four weeks, we’ve worked with hundreds of partners to help them understand their current security posture, and harden it where appropriate. We’ll continue this work, alongside taking additional proactive steps for the benefit of not only our partners, but also the ecosystem as a whole. We want to extend our thanks to our partners for their support and patience this past month. There’s a reason that over $12 billion has moved across the network in the past four weeks, and why the world’s most valuable asset issuers have stood by our side: they believe in us, in what the LayerZero protocol has to offer, and in the value of modular, isolated, application-controlled security. The work continues. And we look forward to continue showing up for the applications that trust us with their business, as well as the broader ecosystem. layerzero.network/blog/layerzero…




