Announcing ZKsync Managed Services from Matter Labs.
Dedicated, production‑grade ZK Stack chains, plus RPC, block explorer, indexers, and event delivery.
Operated 24/7 by the team behind the protocol.
Blog: https://t.co/FUEUthxfSH
Website: https://t.co/gj6FeWL1fJ
The morning after posting this photo in Tokyo, a stranger awaited me in the lobby of my hotel
I went for breakfast and while passing through the lobby, someone on the sofa there turned around and said "Hello Pieter 🤝 "
I was like WTF 😳
It turns out he was an indie hacker living in Japan (not Japanese, but Western), who'd been waiting all morning to meet me
He figured out which hotel I was staying at just from the photo below
I had a chat with him and he was nice, he had a regular job in Japan and wanted to build his own business too, all friendly and nice and fine
But still it did make me remember that rule to never post photos in a place until you've left! Because you may get instantly d0xed and visited by people
I guess obvious in 2025
Especially in a time where AI can find where any photo is taken in literally seconds, even up to the floor number you stay in a hotel, I stayed at floor 37 and it correctly guessed the range (33-38)
Beware!
https://t.co/YtRm2V1bWT
At this point I've audited a couple *hundred* Smart Contracts.
Along the way, I've picked up a number of things that more often than not... lead to Critical bugs/vulnerabilities.
So I decided to compile them all and share them with you.
→ 17 Common attack vectors I always try out on a new codebase (+ 5 Bonus):
- Frontrunning/backrunning
- Using very small amounts as inputs (e.g. 1 wei)
- Passing zero as an input
- Using contracts that cannot accept ether
- Gas griefing with external calls
- Weird ERC20 tokens (fees, 777, return values, etc...)
- Price manipulation
- Blacklisted ERC20 addresses
- Potential overflow/underflow
- Block re-orgs
- Reentrancy (721, inter-function, inter-contract, inter-system (read-only))
- Sybil attacks on incentives/tokenomics
- Flash loans (even flash mints e.g. Dai)
- Accepting any data from an arbitrary address (Malicious bytes)
- Inflating internal accounting by sending tokens to the system
- Forced precision loss when precision really matters (min balance checks etc...)
- Addresses that might be empty at one point, yet house contract code at another
5 Bonuses:
- Reverting (external calls I can make revert, inputs I can use to cause a revert)
- Unexpected addresses (provide a `receiver` address pointing to another contract in the system)
- Selector clashing
- Signatures (replay, malleability, recover to 0 address etc...)
- Hash collision (encodePacked)
I like hardware wallets even less now.
- If they are open sourced: cool
- closed sourced: nope nope nope
- can send your private key out: What in the Vitalik fuck are you doing
Old joke about agnostic technologists building artificial super intelligence to find out if there’s a God.
They finally finish & ask the question.
AI replies: “There is now, mfs!!”
Today our team launched the official @LensProtocol SDK 🚀🎁
It reduces the amount of code by >=95% & includes authentication, persistence, & type safety.
A huge boost to DX & is especially helpful for new devs & early stage projects.
https://t.co/JJT6UtY7kz
before after
For the chance to win a Ledger Stax, all your have to do is:
- Make sure you’re following us @Ledger
- Retweet this post
- Leave a comment telling us what you're going to name your Ledger Stax on the side screen!
T&C here:
https://t.co/DJQ9YTT6Ui
A software developer is facing up to 6 years in prison on money laundering charges for simply writing code.
Code which is a neutral tool meant to protect privacy. Code which he hasn't made any money from.
Release Alexey immediately.
#FreePertsev
We’d like to remind you that #litecoin is one of our favorite #crypto as it’s our belief that one day it might just be mainstream enough to make every ordinary purchase with #litecoin Until that day just realize that we still believe in it. #LitecoinFam