Forwarded from teleLakel
These messages support:
— text formatting: bold, italic, underline, strikethrough, monospace, spoilers, highlights, links, formatted dates, superscript, subscript, and inline formulas;
— message structure: six heading levels, paragraphs, dividers, footers, collapsible sections, code blocks, and standalone mathematical formulas;
— lists and quotes: bulleted and numbered lists, checklists, regular quotes, pull quotes, and quotes with nested formatting;
— tables: rows, columns, headers, and formatted text inside cells;
— media: photos, collages, slideshows, videos, and audio;
— other blocks: locations with maps, and multiple content types combined within a single message.
@telelakel | #new_tgbeta
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
Security researcher finds Zcash vulnerability allowing 'unlimited' counterfeit minting; ZEC drops 31%
link
From
link
TLDR
Researcher spots Orchard bug enabling unlimited fake ZEC mints; devs patch fast, exploitation doubtful. ZEC tanks 31% on disclosure.
Vuln Details
Taylor Hornby used AI to crack under-constrained Orchard circuit in May. Full exploit worked in tests; fixed June 1 after four years live.
- Shielded Labs calls it serious yet contained by privacy mechanics.
- Team eyes supply-proof upgrade plus new pool.
Market Reaction
Drop hit hardest post-X announcement, now hovering near $410 amid fresh scrutiny. No confirmed drains reported.
From
Discovered a new method for detecting if someone is using Incognito in Chrome:
Write 512 tiny 1-byte responses into a scratch Cache API cache, then read:
http://navigator.storage.estimate().usageDetails.caches
Normal Chrome: ~393kb
Incognito: ~85kb
Why? When you're in incognito, Chrome writes to memory instead of disk, which leaves less metadata residue
Posted by Alain Meier, 10 hours ago
On May 4th an APYX affiliated wallet (0xD17) incorrectly supplied $3m USDC directly to a Morpho market using the Morpho Blue address itself as the onBehalfOf parameter.
https://etherscan.io/tx/0x0059fc47ba71f427fb91927183647e89d702acfb9ded42661bc44611463643e6
This means the entire deposit was credited to morpho itself and thereby lost and permanently stuck.
It appears they realized seven days later and used $3.6m of collateral to borrow back that $3m USDC from the market. To this day the wallet remains both the largest borrower and primary supplier in this apyUSD PT market.
Notably, at the current spot prices this position has already become under collateralized, however the oracle used in the market is preventing it from being liquidated.
The market uses a "fundamental" oracle that is meant to be the minimum of the APYX system collateral ratio or 1. However, until just the past day the collateral ratio oracle has had not been updated since depoloyment.
It does appear the team has begun updating the collateral oracle to reflect the true backing which has begun to lead to liquidations. So far liquidations on this market over the past couple days have been manually done by the APYX team itself with the apxUSD backing and holding the mark to market loss on the balance sheet, since the market cannot clear them profitiably even accounting for the liquidation bonus.
Worth noting the APYX has claimed this wallet is not theirs and is not holding backing assets of apxUSD itself. However, shared signer executions, funding practices, overall value amounts and cross wallet transfer matches would suggest otherwise.
Posted by Schlag, 2 hours ago
Do It by Code
On May 4th an APYX affiliated wallet (0xD17) incorrectly supplied $3m USDC directly to a Morpho market using the Morpho Blue address itself as the onBehalfOf parameter. https://etherscan.io/tx/0x0059fc47ba71f427fb91927183647e89d702acfb9ded42661bc44611463643e6…
a better explanation (from gemini):
The $3 Million Typo
Someone affiliated with the APYX team tried to deposit $3 million USDC into a lending platform called Morpho. However, whoever made the transaction filled out the "recipient" box wrong. Instead of crediting their own wallet, they credited the Morpho smart contract itself. You can actually see this exact mistake in the first image you sent. Because of how smart contracts work, that $3 million is now permanently stuck and essentially burned.
The Desperate Loan
A week later, they realized their massive mistake. To get liquid cash back, they took $3.6 million worth of another crypto asset they owned and used it as collateral to borrow $3 million USDC from that exact same lending market.
The Broken Price Checker
Here is where it gets dangerous. The value of their $3.6 million collateral dropped. In normal DeFi, if your collateral drops too low, the system automatically sells it to pay off your loan (liquidation). But that wasn't happening here because the system's "oracle" — the code that tells the lending platform what the collateral is currently worth — was frozen. The second image shows exactly this: the oracle was tricking the system into thinking the asset was worth 0.953, but the real market price was only 0.901.
The Bailout
The APYX team finally started updating the broken price checker to reflect reality. Now that the system is seeing the true, lower price, that massive loan is starting to get liquidated. Because the real price is so bad, no normal automated trader wants to buy the collateral. So, the APYX team is quietly doing the liquidations themselves and eating the financial losses to keep the system from collapsing.
The Lie
To top it all off, the APYX team publicly claims this clumsy wallet does not belong to them. However, blockchain sleuths have looked at how the wallet is funded and operated, and the evidence strongly points to it being controlled by the APYX team.
Essentially, they lost $3 million to a typo, took out a bad loan to cover it, relied on a broken price feed to avoid getting liquidated, and are now secretly eating the losses while denying the wallet is even theirs! Let me know if you want me to clarify any part of it.
The Empty Field That Wasn't: GPS Broadcasts a Numbers Station
🔸GPS satellites broadcast encrypted material in a 176-bit field called Subframe 4, which has been publicly available for nearly two decades. Researchers analyzed 12.16 million observations and found the content is consistent with the military's Over-the-Air Distribution (OTAD) global rekeying network.
05 Jun 2026
💬 comments
🌍 @hackernews_summary
🔸GPS satellites broadcast encrypted material in a 176-bit field called Subframe 4, which has been publicly available for nearly two decades. Researchers analyzed 12.16 million observations and found the content is consistent with the military's Over-the-Air Distribution (OTAD) global rekeying network.
05 Jun 2026
💬 comments
🌍 @hackernews_summary
Meta confirms 1000s of Instagram accounts were hacked by abusing its AI chatbot
Article, Comments
Article, Comments
"According to the data breach notice filed with Maine's attorney general's office late on Friday, Meta notified at least 20,225 people that their accounts had been compromised, including 30 people in Maine. "
i was reading the SQLite source
and found that DELETE does not actually shrink the database file
deleted pages are placed onto an internal freelist inside the file
new inserts reuse those free pages before growing the database again
the file itself only gets smaller when you run VACUUM
delete everything from a 1GB database and the file is still 1GB until you compact it
Posted by trish, 5 hours ago
and found that DELETE does not actually shrink the database file
deleted pages are placed onto an internal freelist inside the file
new inserts reuse those free pages before growing the database again
the file itself only gets smaller when you run VACUUM
delete everything from a 1GB database and the file is still 1GB until you compact it
Posted by trish, 5 hours ago
Re: LLMs are eroding my software engineering career and I don't know what to do
> I don't know what to do.
Ride the wave. You rode it when websites/webapps were the wave. I came into software industry before internet, kept changing my horse. You are never too old to learn new tricks. The new wave create new kind of work and workers. Be one of them. Ride the beast, master the tools. It's the same game again.
zkmon, 15 hours ago
> I don't know what to do.
Ride the wave. You rode it when websites/webapps were the wave. I came into software industry before internet, kept changing my horse. You are never too old to learn new tricks. The new wave create new kind of work and workers. Be one of them. Ride the beast, master the tools. It's the same game again.
zkmon, 15 hours ago
Tiny hackable CUDA language model implementation
🔸The project implements an autoregressive sequence model using a transformer architecture that can process byte streams from various sources. It trains on text data but can model any byte stream, including DNA/RNA sequences, compressed data, and executable binaries.
08 Jun 2026
💬 comments
🌍 @hackernews_summary
🔸The project implements an autoregressive sequence model using a transformer architecture that can process byte streams from various sources. It trains on text data but can model any byte stream, including DNA/RNA sequences, compressed data, and executable binaries.
08 Jun 2026
💬 comments
🌍 @hackernews_summary
The "Simplicity Paradox" in programming
1. A tool is created because existing tools are too complex.
2. People love it because it's simple.
3. People start asking for edge-case features (e.g., "Can I add an annotation for a specific PostgreSQL data type?", "Can I add a regex validator for this string field?").
4. The tool adds these features, becomes complex, and a new tool is created to replace it.
1. A tool is created because existing tools are too complex.
2. People love it because it's simple.
3. People start asking for edge-case features (e.g., "Can I add an annotation for a specific PostgreSQL data type?", "Can I add a regex validator for this string field?").
4. The tool adds these features, becomes complex, and a new tool is created to replace it.
This media is not supported in your browser
VIEW IN TELEGRAM