1/ We are sharing additional details regarding our investigation into unauthorized access to GitHub's internal repositories.
Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.
+++ also from my understanding no audit flagged the DVN config. SigmaPrime, Code4rena, Bailsec, MixBytes all reviewed the solidity but the required DVN count lives in the EndpointV2 ULN config, not the source tree. out of scope by default.
this is the structural gap: risk assessors like Chaos Labs and LlamaRisk onboard collateral based on audit coverage and TVL depth. auditors scope "the .sol files at commit X" and assume the multisig configures runtime parameters securely post-deployment.
nobody owns the layer in between.
IMO crypto needs a PCI-equivalent for runtime posture. (not literal PCI, but a compliance surface that forces protocols to prove their deployed config matches their threat model)
code audits ≠ operational security like every every nine-figure bridge loss in the last two years (Multichain, Nomad, Ronin, now Kelp) was a config or key failure, not a contract bug.
@0xTib3rius the privacy policy there on the appstore and the 4-pin is a whole another level of marketing as "bitcoin like privacy"
well he didn't lie anyway bitcoin ain't that private anyway @monero is.
@durov@durov its funny that you think you're doing good and you're anti-censorship and with privacy and so on meanwhile your app is still not e2e by default and you keep shitting on @signalapp with claims and so on.
like do like them lol.
you're not an angel either
its weird someone would say that to #Spain which leads in several key European metrics as of 2025-2026, most notably boasting the highest life expectancy in Europe. It is currently recognized as the fastest-growing major economy
I believe @spain is going on the right direction regardless of what the post is saying.