diay retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
Spent some time digging into $PRL, and it's one of the more exciting projects I've come across in a while so decided to do a post. The timeline for the thesis is probably longer, but the asymmetry of the success case is hard to ignore.
TLDR: proof of useful work (PoUW) with AI inference as the work mechanism feels like the missing piece for blockchains for a few reasons:
1) Super interesting synergy between blockchain and inference, where a) the chain helps inference by connecting a massive compute supply market with a growing compute demand market, driving inference costs down, and b) inference helps the network by onboarding a diverse set of existing GPU operators onchain, making the network more secure.
2) Key tech folk have suggested that in a post-fiat denominated world, the most apt store of value would be rooted in AI compute as opposed to random work (BTC) or stake (ETH). The more I think about this, the harder it is to see it any other way.
3) Block rewards drive inference costs down and provide mainstream access to invest in AI at the core of inference itself, as opposed to investing through a limited set of public vehicles.
On top of that, it's a stellar team at @prlnet. @WeinsteinOmri and @komargodski are some of the leading minds in PoUW.
Risks: The main risk is it's pretty early in terms of when a system like this could be broadly adopted. From an inference perspective, it's currently more expensive to use than OpenRouter (needs more scale), and it also only runs open-weight models (86% of inference spend is on closed models, i.e. Anthropic, OpenAI). The winds are shifting towards open models, but it may be a while before they hit critical mass.
From a crypto perspective, only 16% of the supply has been mined, so new supply will be a constant source of sell pressure while block rewards are high. Looking at BTC and ZEC, their strongest price runs came after more than half the supply was in circulation. For Pearl, that point is around late 2029.
Overall: superior incentive design, big macro tailwinds, long road ahead. NFA.
A lot of people think fomo's bad fills are due to fomo or the relay front-running their own users' trades. If this were happening, it'd be incredibly easy to see onchain.
The more likely issue is bad fills on the stable swap hop. There are known issues that cause slippage when you have to swap from USD to ETH/SOL to TOKEN, and it's amplified when you're swapping from USD on a different chain. The extraction in these cases happens at the route aggregator level.
Happy to look into any specific txs. But the fact that I haven't seen any proof of front-running tells me it's not the problem.
1
120
Another thing most people miss is that fomo doesn't have delegated access to user wallets. Most other apps can sign any transaction on a your behalf, which makes limit orders simpler, but makes it harder to be an app people keep large sums on
Replying to @0xUnihax0r
lol huh?
i said “building the tech is nontrivial” not “we dont want limit orders”
idk why ppl think we wouldnt want limit orders. its obviously something we want as well and will build.
most of these embedded wallets/terminals have delegated access and can just submit tx’s on ur behalf. fomo doesnt.
on top of that theyre all on one chain, not crosschain.
1
3
1,888
Building limit orders at scale is very different from vibe-coding limit orders. Fomo has found success in making trading on chain pleasantly simple. And there have been sacrifices to accomplish that- for example, people already complain about bad fills on market orders.
Now limit orders come with a drastic increase in the variance of trader expectations and technical complexity. Building them in a way that stays pleasantly simple and sufficiently performant for most traders is actually new territory. I’d argue it doesn't exist yet, and it will take time to get right.
If you are shitting on @fomo for not having limit orders because you think you can just "vibe code" it
then you do not know what it takes to build a good trading product
GOOD limit orders are hard.
I’ve personally used a terminal with poorly implemented limit orders and lost $10k+ because of it.
Getting this wrong is worse than not having it at all because the moment users can’t trust your execution, you lose them.
A limit order is not just:
“if price hits X → buy/sell”
That’s the easy part.
First, you need RELIABLE market data/indexing so you detect the trigger accurately and quickly.
Then you need the execution layer to actually work: routing, transaction construction, priority fees, retries, fallbacks, MEV protection, slippage controls, liquidity checks, etc.
Getting the trigger right means nothing if the trade itself executes like shit.
And meme coins make this even harder.
A token can move 10–20%+ while you go from:
price hits trigger → detect it → build tx → route it → land onchain
Your “limit price” and your actual fill can be very different things.
Now multiply all of this across chains.
Different execution environments, liquidity venues, routers/aggregators, RPC infrastructure, block times, MEV dynamics, transaction mechanics, and failure modes.
If you know Fomo- their goal isn’t to build the best terminal for one chain.
It’s to make the same trading experience work across ALL of them - the user shouldn’t need to care what chain, venue, or infrastructure is underneath.
The product should just work.
That means every new chain isn’t simply “add a button.”
You have to make sure the data, triggering, execution, and failure handling are reliable enough that the experience feels consistent everywhere.
I know many of you think you are exposing Fomo
But you are actually exposing how little you understand about trading infrastructure
1
1
252
diay retweeted
social trading this cycle is what will catapult crypto from the doldrums into mainstream society, will be a few traders who make 10M+ publicly this cycle and watching it live will be best show on the internet
e.g. qwerty up 2Ms in a week trading memes, equities, & crypto perps
Having worked at a brokerage, I’ve seen how much regulatory, ops, and dev go into making trading in America as seamless as it is today. But our reliance on a handful of able brokerages limits innovation. Stocks coming onchain means entering a golden era of financial apps
3
219
diay retweeted
It's time to pass the CLARITY act.
giving onchain builders in the US regulatory certainty will unlock an incredible amount of new innovation.
diay retweeted
subscriptions assume a human will use a service regularly enough to justify a monthly fee
agents don't work like that. they use a service once, get what they need, and move on.
per-request micropayments are clearly the right model for agents (cc fees are cost prohibitive) and there’s no better stack than x402 + usdc + base
Getting some motion finally clicker.xyz/position/23f3593…
Huge unlock for Base. Moving beyond the OP Stack means faster & more meaningful upgrades
A new, unified stack for Base Chain
Excited to share that we are evolving our technical roadmap, consisting of our own spec, code, and infra to accelerate the foundation of Base. This shift gives us the autonomy to ship protocol improvements more frequently and focus our resources on scaling to 1 gigagas/s.
What this means for builders:
- Higher Velocity: Targeting 6 hardforks per year to get you new features and fixes faster.
- Massive Scale: Targeting 1 gigagas/s to support high-throughput apps without congestion.
- Extreme Reliability: Targeting 99.99% non-empty blocks and predictable, low fees.
- Simpler Design: A maximally simple spec that’s easier to audit and build on.
Along with this, we will take a more active role in managing our own upgrade schedule and stack: allowing us to build what the ecosystem needs, at the speed it needs, while remaining deeply aligned with Ethereum.
Read the full technical breakdown here: blog.base.dev/next-chapter-f…
196
diay retweeted
The easiest way to print 6 figs on Base this month.
wallet.xyz/kien

























