Tabizen💢🏯 (@Tabizens) header
Tabizen💢🏯 (@Tabizens) profile picture

Official X community of @TabiVibe U CAN FULLY BE URSELF HERE 💢 Tabizen Honor Roll👉:https://nitter.gq/t.co/ObgdesJFek

Singapore
Joined March 2024
Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)Photo by Tabizen💢🏯 (@Tabizens)
possibly the most expensive laptop in crypto history 😇
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annou…
1
1
120
GOOGL dropped 10% , partly because Google Search growth slowed. More people are turning to AI instead of searching on Google. And as AI agents get better at handling everyday tasks, even more people will stop relying on Google Search. This is probably just the beginning.
5
1
4
422
Tabizen💢🏯 retweeted
The next step after enforcing policy is making policy legible to the agent.
14
11
39
9,983
Tabizen💢🏯 retweeted
Sometimes, a simple “I get you” is warm enough.
18
5
36
9,102
Tabizen💢🏯 retweeted
Congratulations! @odagius @BNBStandard
A bell heard far beyond Times Square. Congratulations @odagius @BNBStandard!
17
7
1
51
14,516
GTabi. somehow it's monday again. back to vibe coding.
6
1
3
341
Tabizen💢🏯 retweeted
138M+ x402 payments and counting. The next bottleneck isn’t “can agents pay?” It’s “who decides the limits, and how hard are they enforced?” Identity stays with the user. Control plane stays with the vault. 💢
Agentic commerce is growing fast. Cumulative x402 transactions on @base: 58.8k in Q3 2025. 138.5M in Q3 2026. Transactions under a dollar do not make fiscal sense for a credit card network. Stablecoins that settle for under a cent do, so AI agents can pay per API call.
11
9
34
8,879
Tabizen💢🏯 retweeted
Still on the road. Still moving.
53
10
2
76
13,934
Tabizen💢🏯 retweeted
“Give the agent $100” is not a risk policy. A real funding policy needs dimensions. PredictClaw’s Vault overlay can now express constraints such as: Per transaction How much can move at once? Per window How much can move cumulatively? Time When does the budget reset? This is where agent capital starts becoming programmable.
7
8
36
9,294
AI is making it easier to find vulnerabilities in code that's been running for years. Secure execution is becoming more important than ever...
🔐 Node.js security updates are now available! New releases for Node.js 22.x, 24.x & 26.x address multiple vulnerabilities, including high-severity issues. Review the details and update your systems to stay secure. 🔗 nodejs.org/en/blog/vulnerabi… #NodeJS #Security
2
1
3
323
Tabizen💢🏯 retweeted
Keep the identity. Upgrade the control plane. 💢
16
9
1
42
10,577
Tabizen💢🏯 retweeted
From there, users can choose the workflow they actually need: → read-only → EOA → Predict Account → Predict Account + Vault
14
8
34
10,352
Gtabi, back to build 💢
4
4
340
Tabizen💢🏯 retweeted
Monday: Brain loading… Coffee ready. Human still buffering.
12
5
1
37
9,042
8x growth in small-business agent users is pretty impressive. But getting people to try agents is one thing. Getting agents to actually work across the apps, payments and systems businesses rely on is another. That's where the real challenge lies.
European businesses are rapidly expanding their use of AI agents. More than half of the AI use among our EU enterprise and business customers now involves these tools, and the number of small business users has grown 8x across the region. Our latest Economic Research report explores Europe’s shift toward agentic AI—and the opportunity to turn broader adoption into deeper use. openai.com/index/the-eus-nex…
2
2
285
Tabizen💢🏯 retweeted
…anyway, back to building.
24
11
3
55
13,637
isn't it supposed to be uptober?
2
4
273
Tabizen💢🏯 retweeted
We don’t want ERC-8192 to become a Tabi-specific execution framework. The goal is a minimal, composable execution primitive. Three questions we’re actively pressure-testing: 1. Is the Core / Extension boundary right? 2. Is fund-and-action generic enough? 3. Is the Base execution model clear enough for builders? Builders: break the abstraction. That’s how standards get better.
26
15
2
52
12,762
Tabizen💢🏯 retweeted
Bears don’t kill projects. They kill weak conviction.
23
9
44
11,049