Pinned Tweet
What is @Veildotcash ?
Veil is a privacy protocol on @base that uses zk-SNARKs to provide users with onchain privacy.
What makes Veil different than others, is that it only allows "verified" users to enter these pools.
Using social data / onchain data only certain users can join these pools.
Link: veil.cash
Docs: veildotcash.gitbook.io/veil-…
why is Grok bot so slow?
Only real issue i'm having. No reasoning traces also mean i haven't got a clue what its up to or stuck on.
Who was in charge of picking these coins. Jfc.
brutal.
BREAKING: Microsoft, $MSFT, is offering buyouts to 60,000 workers as part of the company’s efforts to cut costs amid AI adoption, per Bloomberg.
Personnel on select teams in the US, Canada, India, and the UK at a vice president level and below will be eligible.
This reflects ~27% of Microsoft's total workforce.
The boys have started swapping gamer tags in the trenching group. That’s how cooked onchain is at the minute.
Apex retweeted
If you don’t want to deal with kimchi or kols or some other bullshit CT drama and just went to trade with the pros, there’s an app for that
@DefinitiveFi
think its time to put the big boy pants on and look at AWS for my projects. I already use it daily for Bedrock and a devbox.
Terraform / Cloudformation -- any input?
hell of a morning rotating stuff for @Veildotcash
firstly, user funds where never affected. they can't be, as we never have control over them in the first place.
But We have a small stack, that ruins the relayer + indexer to help the site run a bit smoother. Worker wallets and API keys all rotated out now.
Feel for the @Railway team, great product i've enjoyed for years.
Bro just one more security patch bro. I swear bro just one more patch and it'll be secure bro.
Please bro just one more patch. This one fixes all the vulnerabilities bro I swear.
hell of a morning rotating stuff for @Veildotcash
firstly, user funds where never affected. they can't be, as we never have control over them in the first place.
But We have a small stack, that ruins the relayer + indexer to help the site run a bit smoother. Worker wallets and API keys all rotated out now.
Feel for the @Railway team, great product i've enjoyed for years.
An urgent notice from the Railway team
blog.railway.com/p/security-…
"Runs on Opus 5.5"
it's so over for dots and grok bot.
lmao. I've had similar exchanges before.
Security called me at 6:12 AM today.
"Patch every PHP server immediately."
I asked what happened.
"Two critical vulnerabilities. Remote code execution. No authentication required."
Cool.
How many PHP servers do we have?
According to inventory: 12
According to reality:
Nobody knows.
We found one running WordPress.
Three running old internal tools.
One under someone's desk.
Two inside vendor appliances.
A forgotten employee directory from 2016.
And a server named:
PHP-OLD-DO-NOT-TOUCH
Naturally, that one runs payroll exports.
Then we found a PHP 5.6 box.
I asked who owned it.
The documentation said:
BRIAN.
Brian left in 2019.
We called Brian.
He said:
"Oh wow, that's still running?"
Excellent.
By 8 AM, leadership joined the incident call.
CEO:
"Can hackers actually get in?"
Security:
"Potentially yes."
CEO:
"Without a password?"
Security:
"Yes."
CEO:
"Then why do WE need passwords?"
Not the lesson.
Finance asked if we could wait until the weekend to patch because downtime affects revenue.
Security explained that the alternative was letting strangers execute code on our servers.
Finance asked for a cost comparison.
At 9:17, someone suggested temporarily taking the vulnerable websites offline.
Marketing refused.
"Our campaign is live."
So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.
We finally patched everything we could find.
Then our scanner discovered another PHP server.
Hostname:
TEMP-PHP-2014
Uptime:
4,512 days.
Nobody knows what it does.
Nobody owns it.
Nobody can shut it down.
But every time we block network access, the warehouse stops printing shipping labels.
Security has classified it as critical infrastructure.
It is running PHP 5.4.
The vulnerability has existed longer than half our employees.
The emergency patch took four hours.
Finding out what PHP actually runs took eleven.
The internet isn't held together with code.
It's held together with servers everyone is afraid to turn off.
Apex retweeted
Never deleting this app.
Replying to @JustLingonberry @ThePHPF
aren't you the moron that exposed your API keys on stream/uploaded your .env files and lost $90,000 and cried about it on your X lol
xitter.cf/JustLingonberry/status…
you're a real dev for sure!






















