@ObiAutosNG@cz_binance@alexdolbun Weeks only show how the market feels. The chips shipping for the next couple of years were planned under Jensen anyway. The real test is what the next CEO decides, and that takes years to show.
Jensen co-founded Nvidia and ran it for 33 years. Gone 4 days into a board investigation.
He owns 3.5%. One share, one vote. Nothing to fight a board with.
Elon holds 82% of SpaceX votes. No board can push him out.
The scandal was the trigger. The cap table left no way back.
We'll find out in a few years if losing him was a mistake.
@ExactEscrow When a buyer asks if the wiring email is really from your office, what do you send them so they can check it against the version you issued?
Been doing outreach myself for a few weeks.
Some prospects read my questions as digging into their business. I'm only trying to check they have the problem before suggesting anything.
How do you ask "how do you handle this today?" without making people uncomfortable?
Getting your email hacked should not cost you or your organization money.
One changed account number on one real-looking invoice is all it takes.
So take the document out of the email.
Evidence Rooms. First room free.
Send secure today.
https://t.co/2e90zvqyBC
Meet the animated me. A founder learning to make videos, mistakes included.
Made with AI tools: Krea and Seedance. Edited in Final Cut Pro.
New video every week.
Binance lost ~$6.3B (about $3B since frozen) and says it found no evidence any private keys leaked.
That's the part people should be scared of.
Per Binance, a compromised DevOps engineer's laptop gave the attacker access to a service container that was allowed to submit withdrawals to the hot wallet signer. They've since found additional points of breach.
The signer did exactly what it was built to do. It signed.
On Ethereum it signed an EIP-7702 delegation that turned Binance 14 into a sweeper contract. On the other chains it signed plain transfers. Same pipeline, ~10 chains, minutes.
Laptops get popped every day. Good security assumes that will happen.
The real failure is that "attacker controls internal services" turned straight into "billions get signed" with nothing independent in between.
What should have been there:
The signer parses what it signs. No blind hashes.
Hot wallets only sign transfers to whitelisted addresses. Never a 7702 delegation.
Hard amount and rate limits the requesting service can't change.
Large moves need approval from a separate system and separate people.
Any one of these turns a $6.3B loss into a much smaller one.
And here's the uncomfortable bit. A compromised laptop with EDR installed and MFA on still shows green on every compliance dashboard.
Passing audits means your controls exist. It doesn't mean anything stops a bad signature at the moment it matters.
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.
https://t.co/ywB2mKFy0p
Introducing the Invoance MCP server
Signed records, straight from your AI assistant
~ what you sent, and to whom
~ the file, by its fingerprint
~ what the model said, and which model
Let your agents keep the receipts.
https://t.co/tIEPubZ5jB
People kept asking for our logo, so I spent a couple of hours fixing that.
Right-click the Invoance logo and it's yours. Copy it as SVG straight to your clipboard, grab the full brand kit, or open the guidelines.
No downloading files one by one. No screenshots.
https://t.co/Ed8Iceg8eD
@TitleTechNY@aussieflya@CertifID When a buyer calls in for the last 4 digits, how does your team confirm it's really the buyer on the line and not someone who's been sitting in their inbox for weeks?
@davidaeberle Agreed, and I'd add one thing: the audit trail has to be one the bank can check without trusting the agent's vendor. If the log sits in a database the agent can write to, it's a story, not evidence.