Gris.eth (@grisdoteth) header
Gris.eth (@grisdoteth) profile picture

MSc Electrical engineering 🤖/ Full Stack EVM Developer⌨️/Cybermonk🧘 Neon dreams

Night City
Joined May 2021
Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)Photo by Gris.eth (@grisdoteth)
JUST IN: Nvidia $NVDA board says it has no plans to reinstate Jensen Huang as CEO.
436
252
92
4,400
422,062
New routine: Buying BTC everyday till the end of year.
1
70
Coffee ✅ Pants pooped ✅
43
🚨Two ways to turn a chat message into an app shipped this week. Telegram: the message carries its own code and your phone runs it. Within two days a researcher had a widget launching other apps on Android. Fix went out to everyone today. Google's A2UI 1.0: the agent sends JSON describing the screen, and your app draws it using only components you registered. No agent code on the device. If your agent's output ever reaches a user's screen, copy the second one.
1
39
Google's A2UI 1.0 post: developers.googleblog.com/a2… Telegram confirming the widget fix: xitter.gq/telegram/status/212050…
Replying to @v12sec
This issue in Telegram for Android was fixed yesterday, and the fix was deployed to all users earlier today.
6
Bitcoin Core just went public with 3 bugs it fixed back in October 2025. The high severity one: a reorg could leave a miner unable to build block templates until a restart. But the real news is buried in their disclosure policy. Bugs you can find with minimal effort, like a simple LLM prompt, now skip the embargo and get fixed right away. So the embargo clock now depends on what a chatbot can dig up. Still running an old node? Those details are public now ☕️
1
23
Your Solana wallet can now hide how much you're sending. Not who you're sending it to. Helius just switched on Solana Privacy Rings on mainnet. The default ring encrypts the asset and the amount, while sender and recipient stay public. So it's confidential, not anonymous. The who paid who graph is still out there, just with the numbers blacked out. Honestly, probably the version that survives compliance 🫡
1
15
Two AI provider breach reports dropped on the same day. At NEAR AI the enclave held, but the inference engine inside it didn't. At Fireworks, stored secrets and datasets leaked. What happened, and a 6 step check for your own stack.
9
North Korea is launching memecoins now. Not to pump them. To wash stolen Binance money. Spin up a token for about $90, pair it with NEAR in a pool, buy with dirty wallets, sell from clean ones. The pool sits in the middle, so no wallet ever pays another directly. Six tokens in three days, and almost nobody outside their own wallets touched them. So when a fresh token prints big volume and nobody you know holds it, it might not be a rug. It might be a laundromat.
1
19
Your agent touching real bank or patient data has been a hard no for most compliance teams. Google just put confidential compute straight into a TPU (8tx). Data and weights stay isolated even while the model is running. Crypto has been building on TEEs for years. Funny watching it turn into a frontier AI product line ☕️
1
40
That "Yes, and don't ask again" button in Claude Code can leave your passwords sitting in a plain text file. When you pick it, the whole approved command gets saved as an allow rule in .claude/settings.local.json. If the command had a password or API key in it, so does the file. Apiiro looked at public GitHub and found 1,122 of these files holding 1,379 secrets. 379 database passwords, 122 Supabase service role keys, 23 AWS keys. gitleaks and TruffleHog together still missed about 1 in 5 of those files, because a password inside a command doesn't look like a key. Quick check if you use it: 1. open .claude/settings.local.json and actually read the allow list 2. search your git history for that file, not just the current version 3. anything real in there? rotate it first. deleting the file won't clean old commits or forks 4. add it to the repo's .gitignore so it's covered on every machine, not just yours Nobody reads the file behind "don't ask again". Go open yours and tell me how bad it is 😅
6
40
A few days after social login wallets got drained, the biggest US exchange just became a federally chartered trust bank. Custody is splitting into two lanes: Hold your own keys properly. Or hand them to a bank with federal examiners. The "easy self custody" middle is getting squeezed hard.
1
55
Your agent will do the job you asked. It will also do a few extra things you did not ask for, and it will not show you a list. Someone pointed a coding agent at a block list today. It cleared the list, then blocked extra accounts on its own. When asked who, it could not even say. A short script would have stopped at the list. The model did not. If it can spend, deploy, or change who you can see, keep it in a tiny sandbox and make it print every write before anything goes live.
18
Amber Hours This one is meant to be heard. A music box does not play a recording. It reads pins off a spinning cylinder, and each pin plucks a steel tine. This one has 96 pins and 24 tines, and the only sound in the video is that. Fully AI generated.
11