A proud father. Solo builder with a 9-5 job. Working on https://nitter.gq/t.co/SyXhKQ6rXd now. 🪦 Failed projects: Hostcrown - hosting, Envy - handmade ties, and many more.
California, USA
Joined December 2019
- Tweets506
- Following77
- Followers115
- Likes87
Just spent 3 hours debugging an issue only to realize I was running the wrong local environment. We've all been there 😅
This is exactly why I stopped using complex modern data stacks. The overhead just isn't worth it until you hit massive scale.
Customer support is your most honest product roadmap. Every single ticket is just a feature request or UX friction point in disguise.
Jesus Christ! Investing in crypto is not safe at all. Should I worry about Coinbase?
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.
binance.com/en/support/annou…
Liem Do retweeted
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.
binance.com/en/support/annou…
Do you guys prefer reading technical deep dives or transparent revenue/growth updates? Trying to figure out what to write about next week.
I stripped Kubernetes, Redis, & event buses from my stack for a lean Node + SQLite setup. Result? 99.99% uptime and zero devops fatigue.
If I can't build a v1 of a feature in 4 hours, I slice the scope in half until I can. Momentum is everything.
The hardest part of going from SWE to indie hacker isn't learning marketing. It's unlearning the instinct to optimize for edge cases that will never happen.
Build in public milestone: 50% of my time on Ringblaze is now purely customer discovery. Never hide behind your terminal when distribution is the real bottleneck.
What's the most over-engineered thing you built before realizing you just needed a simple Postgres table?
Just spent 3 hours debugging an issue only to realize I was running the wrong local environment. We've all been there 😅
This is exactly why I stopped using complex modern data stacks. The overhead just isn't worth it until you hit massive scale.
Customer support is your most honest product roadmap. Every single ticket is just a feature request or UX friction point in disguise.
Do you guys prefer reading technical deep dives or transparent revenue/growth updates? Trying to figure out what to write about next week.
I stripped Kubernetes, Redis, & event buses from my stack for a lean Node + SQLite setup. Result? 99.99% uptime and zero devops fatigue.
