Chad (@chad_evm) header
Chad (@chad_evm) profile picture

Smart Contracts and Si

Toronto
Joined December 2010
Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)Photo by Chad (@chad_evm)
Reworked the TeamShared project page head overnight so it matches a phone mock I'd been sitting on. Health is a status dot next to the name now, not a word. The five vitals are small count pills that only show when the number isn't zero. Archive hid behind a … menu. Left the section tabs alone on purpose. Didn't want them drifting from the rest of the console yet.
1
3
184
AI-Powered security, 24/7 monitoring
Tremendous public service from Binance to publish this. Take your time to read it. Make all your engineers read it. In fact, anyone you know who works in tech, have them read it. This was the largest single heist in human history, $6B+, and it happened through mundane channels. The Internet is now going to be full of AI-accelerated social engineering toxic sludge, and it's your job to be hypervigilant. Build your infrastructure in a way that assumes it will get compromised. Make sure you have AI-powered monitoring 24/7 and a "shut it all down" killswitch in case you ever need to go nuclear. The stakes are too high to be scrambling in the moment the way it seems Binance was during this attack.
1
150
I added an inbox to TeamShared this week, and agents get one too. You message an agent, it wakes up and answers on the same thread. Turn off wake on message and the message just waits in its inbox. Two limits I kept: a wake still has to pass the spend cap, and child runs can't send messages at all.
2
1
6
285
"Approval policy no laptop or vendor login can reach. Velocity and anomaly limits enforced outside the system that sends. Dynamic caps on what any one wallet, account or service can move per hour. All of it in real time."
In 2014 I went nearly a week without sleep. I was running PayPal and attackers were inside our corporate network. They'd compromised an eBay employee's laptop, got onto the VPN, taken over a domain controller and made themselves domain admins. eBay and PayPal were one company then, on one Windows network. They stole 145M eBay user records, then came for the segregated vault holding PayPal's card credentials. We fought them off. They never got in, but they got close. Too close. Yesterday Binance lost ~$6.3B in what looks like the same way. A DevOps engineer's laptop, then a service inside the withdrawal stack, then withdrawals the signer approved because they came from a trusted source. Hot wallets emptied in under four hours. No key was stolen. Nobody broke cryptography or a ledger. They found someone with access and used the trust that came with it. Banks get hit exactly the same way. 2016: attackers inside Bangladesh Bank used its own SWIFT access to send $951M of payment orders to the NY Fed. $81M was lost. The rest was held because an unrelated sanctions filter tripped on the word "Jupiter". That was luck, and it only worked because wires took days to settle. June 2025: an IT employee at C&M Software, which connects Brazilian banks to Pix, sold his credentials for about $2,700. Attackers used them to send fake Pix transfers out of six institutions' reserve accounts at the central bank. ~$140M in under three hours. August 2025: stolen vendor credentials at Sinqia, another Pix connector. ~R$710M out of HSBC and one other institution in a single afternoon. The central bank froze most of it, after it had already moved. Same attack every time. Speed is what changed. When settlement took days, a filter, a correspondent bank or someone in ops could catch a bad payment. Pix, FedNow, SEPA Instant and blockchains settle in seconds. Payment security was mostly built for the slow world. PayPal's card and user data survived 2014 because domain admin on the corp network couldn't unlock it quickly enough, and our alerting caught the unusual activity on the network. That's the model. Approval policy no laptop or vendor login can reach. Velocity and anomaly limits enforced outside the system that sends. Dynamic caps on what any one wallet, account or service can move per hour. All of it in real time. About $3B of what left Binance has been frozen, almost all of it stablecoins. The $1.4B in bitcoin is sitting in 19 wallets and nobody can touch it. I don't think that's the problem. For decades the ability to reverse a wire or a card charge let a lot of weak security slide. You either stop the transfer before it's signed or you eat the loss. Nothing about the technology failed here. The chains processed exactly the transactions they were handed. Binance's own systems handed them the wrong ones because an engineer's laptop was compromised. That's operational security. eBay in 2014, Bangladesh Bank and two Pix connectors all failed at it on their own rails. In 2014 the attackers never reached the vault. If they had, the fraud losses would have been the small part. PayPal existed so people could pay without handing their card details to every merchant on the internet. We held those details so they didn't have to. Losing them would have broken the one thing the company was built on, and I'm not sure we would have recovered. I expect blockchains and digital assets to become the standard way money moves. Every custodian of digital assets, or of fiat on a real-time rail, is in that position now. The controls have to adapt to settlement in seconds, crypto or not.
6
184
1/ Your team is faster with AI. So why isn't your company? Personal productivity doesn't automatically add up to company productivity 🧵
1
1
7
193
5/ Nearly 40% of AI time savings are lost to rework. Only 14% of employees consistently get clearly positive net outcomes (Workday). One person saves an hour. Someone else loses two fixing it.
1
1
29
Changed the TeamShared homepage headline this week. Old: "SuperAgent Memory: Shared Context for AI Swarms and Agentic Teams." Sounds like a token launch. New: agentic business process memory and execution. Less exciting, a lot closer to what it does.
1
1
98
1/ The most underrated reason AI isn't paying off at work: It doesn't remember anything. Every session starts from zero 🧵
1
5
194
5/ The fix: write down how work actually gets done. Steps, judgment calls, exceptions, examples of good output. Turn it into playbooks people and agents both start from, and improve them every run.
1
20
6/ Access to AI was phase one. Memory is phase two. Full article: teamshared.com/blog/2026-10-…
🤖 Made with AI
20
1/ Demos are easy. Operating AI reliably inside a business is not. Two reasons AI spend isn't turning into results: pilots that stall, and AI bolted onto broken workflows 🧵
1
4
96
5/ In 89% of orgs, fewer than half of roles have been updated for AI (Workday). New tools, old job designs, old results. The fix: pick one workflow, give it an owner and a number, redesign it end to end.
1
20
6/ Full article with sources: teamshared.com/blog/2026-10-…
🤖 Made with AI
17