Simon

There will be no WW3. They've abandoned numbered releases and switched to a live service model with seasonal events.

Boris' argument for why Bitcoin is a ponzi: i) one of his friends once invested in it and the price went down ii) Satoshi is Japanese (?) iii) there's no one to talk to if, and I quote: "they decrypt the crypto" iv) Pokemon cards are better because kids notice them $200,000

I see some weird things but this takes the biscuit. A vulnerability in the Companies House website, that let anyone view the private dashboard of any one of the five million registered companies, see directors' personal details. And modify them.

@IterIntellectus Academia should return to what it is meant for: professional researchers, engineers, scholars. Not as a dumping ground for everybody who just wants a degree to get a basic job.

I built this as a side for personal use. But, it turned out to be so much more and so much better than I ever hoped, I am releasing it as a product for everyone. It's called Situation Deck (SitDeck) and it's a free OSINT dashboard with 180+ live data sources. It puts the entire world and almost everything happening in it on one screen. Here's what it is, why it exists, and why/how I'm giving it away for free.

The first two known exploits against live ZK circuits just happened, and they weren't subtle underconstrained bugs. They were Groth16 verifiers deployed without completing the trusted setup ceremony. One was white-hat rescued for ~$1.5M, the other drained for 5 ETH. 🧵

In December I was quoted $4000 for a batch of eMMC chips. I didn't want to commit because I wasn't yet sure if they are large enough (128GB; it would be better to have 256GB). Today's quote is $32000. I can't afford that for my project. ¯\_(ツ)_/¯

Alright, so when any EOA is delegated to any contract, the EOA essentially behaves like that contract. So what I did is just create a contract that has both receive() as well as fallback() function, so when anyone sends native gas token to the EOA which is behaving like a smart contract due to the EIP-7702 delegation, it triggers the receive() function, which immediately calls an internal function called _forwardNative(). This function checks the msg.sender, if it's not my address, it calls another internal function that reverts the whole transaction, essentially makes your tx fail and your gas token bounces back to you. And if it sees my address as msg.sender, it forwards the gas token right back to me. Now this is a very simple contract, yet very dangerous as well. After the Pectra upgrade, hackers don't monitor for gas token transfers using RPCs anymore. Instead, they design their malicious contract in such a way that whenever you send a gas coin to your compromised wallet, it triggers the receive(), which essentially calls another function that sweeps your gas token directly to the hacker's wallet. And here's the nastiest part, as your wallet is already compromised, means the hacker has your private key, when you try to undelegate the smart contract by setting the delegation to zero address, they re-delegate again to their malicious contract almost immediately using your own private key. They keep the delegation alive to ensure the native coin sweeping runs all the time. It becomes a constant tug of war that you almost always lose. And the irony is u are your own problem here. Every time you send gas tokens to your compromised wallet trying to save it, your own transaction triggers the receive() function, which calls the sweep function that sends your funds straight to the hacker. You are literally funding your own robbery. The hacker doesn't need to run a bot watching for incoming transfers anymore, you are doing the work for them. Your transaction is the trigger, your gas token is the payload, and the contract your wallet delegated to is the weapon. All the hacker did was set the trap.

And yet someone decided to use the energy for mining Bitcoin

Why is everyone so sad no one has to potentially work anymore

What it's like using the internet in the UK right now

Psyops protection inbuilt

@sumsub A bit tone deaf to publish an article on other company incidents when Sumsub just disclosed a threat actor had access to sensitive data that went undetected for 1.5 yrs.

It seems the Bank of England is unwilling to budge on the £20k stablecoin holding limit for individual users, which significantly restricts many use cases. Apparently, BoE staff understand this, but it may be that the restriction is coming from the very top, perhaps Andrew Bailey? Whether this is true or not, its a true limit to innovation and for the UK to lead on stablecoins denominated in its own currency. I sincerely hope this does not make it into the final draft, as it would severely undermine the potential stablecoins can provide and reduces the competitiveness of the UK regime globally. At worst, this could mean that the US or the EU becomes a more favourable region for growing sterling stablecoins, pushing them further outside the reach of the UK oversight.

API sellers want to replace @stripe with permissionless, pay-per-request payments using x402 and USDC. But x402 requires buyers to sign every API call or manage private keys in their code. Developers just want to connect a wallet, set a spending limit, and make API calls, the same way they'd use any API key today, but funded by their wallet instead of a credit card. There's no turnkey way to let a buyer authorize once in a browser and have x402 payments execute automatically on every call after that.

You have to be able to post memes when times are bad. You have to be able to post memes when times are good. You have to be laughing at situations. You have to find the humor in the worst times and the best times. That's the ascended path.

THIS IS NOT A DRILL: The Dutch authorities, without a warrant, just seized one of our VPN servers saying they'll give it back after they "fully analyze it". Windscribe uses RAM disk servers so the only thing the authorities will find is a stock Ubuntu install. The bigger worry is the unredacted Epstein files we had on there...

Attacking the P vs. NP problem with ruliology ... the beginnings of empirical theoretical computer science writings.stephenwolfram.com/2026/01/p-vs-n…

We’re partnering with the UK's Department for Science, Innovation and Technology to build an AI assistant for GOV.UK. It will offer tailored advice to help British people navigate government services. Read more about our partnership: anthropic.com/news/gov-UK-pa…