Pinned Tweet
people in a community i ran were convinced i wasn't a real person. a bot, or a company account with staff taking shifts.
you can't moderate your way out of that one. i went on the livestream and said hello.
that fixed it. nothing else had.
1
6
600
the loudest person in a community is almost never the one you want handling something.
the one you do want rarely puts their hand up. but every time i asked, they said yes straight away.
the bottleneck was never willingness. it was noticing.
3
315
"this might kill everyone" is now something you can say about your own product on a tuesday and still have a normal wednesday.
3
364
steam tells you at checkout that you're buying a license, not a game. it's in the cart, right before you pay.
it took a california law to get that sentence written down. the arrangement never changed. it just got printed.
1
4
597
52% of game developers now say generative AI is making their industry worse. two years ago it was 18%.
the support that's left is concentrated in executives, not in the people actually shipping.
that gap isn't a games story.
3
423
fogo's chain is back up and 237m of the stolen tokens are gone for good.
on how the foundation was compromised: "we'll share further information as the investigation continues."
that isn't a date. they just spent three days learning what fills that gap.
1
3
524
certik puts august at around $215m in confirmed losses. $41.5m of that was phishing.
that part isn't a contract problem. it lands on whoever runs the discord.
the exploit gets a postmortem. the phishing wave gets a pinned message nobody reads.
there's a fake foundation account running a compensation vote for a chain that can't produce blocks.
fogo has been halted since saturday and the halt notice is still the last word from the project.
silence during a halt isn't neutral. somebody fills it.
1
8
623
update: cronos is back online. validators rolled the chain back to before the exploit.
that answers today. it also hands every user on that chain a new question: who can rewind this, and what has to happen before they do it again.
the postmortem is the easy part.
cronos is halted. crypto.com says its app and exchange are running normally. people are mixing those two up.
everything on the chain is frozen right now, including positions that never went near tectonic.
no restart time has been given yet.
1
8
993
cronos is halted. crypto.com says its app and exchange are running normally. people are mixing those two up.
everything on the chain is frozen right now, including positions that never went near tectonic.
no restart time has been given yet.
cosmos labs isn't naming the bug, the chains, or a restart time. correct call, it protects everyone still unpatched.
it also leaves every community manager on a cosmos evm chain announcing an incident they can't describe.
hardest post in this job and nobody trains you for it.
the version that works: state the fact, state the boundary, state the next update time.
"we've halted. we can't share the vulnerability yet because other chains are still patching. next update 09:00 UTC whether or not we have news."
the third line is the one people skip and it's the only one that buys you quiet.
1
184
The coldcard hackers are sitting on a pile of bitcoin they can't move.
so people started messaging them on-chain. one offered to launder it for 7%.
cold outreach has reached the point where you're pitching your services, inside a bitcoin transaction, to somebody who is definitely never going to reply.
1
8
790
coldcard users did nothing wrong. no phishing link, no seed typed into a fake site, no device out of anyone's hands.
the flaw arrived in a dependency migration in march 2021. five years later, over 1,000 BTC left those wallets in 41 minutes.
i've argued for self-custody for six years and i'm not walking it back. but "not your keys, not your coins" was always half a sentence. the other half is that you inherited a build config you never saw.
own your keys. owning them isn't the same as understanding them.
2
9
910
the strongest argument against me: this is the case for custodians and it just made itself. a regulated custodian carries insurance and a legal counterparty. a hardware wallet carries a firmware release from 2021 and your hope.
my answer is that custody moves the failure, it doesn't remove it. the people who lost funds on an exchange got this same lecture in reverse. pick the failure you can actually inspect.
98
the affected set, from Coinkite's own advisory:
Mk2 and Mk3 on firmware 4.0.1 through 4.1.9. Mk4 and Mk5 before standard 5.6.0 or Edge 6.6.0X. Q before 1.5.0Q or Edge 6.6.0QX.
updating firmware does not repair a seed that already exists. if yours was generated on affected firmware you need a new one and the funds moved across.
seeds built with 50+ private dice rolls are not considered at risk from this alone.
blog.coinkite.com/coldcard-m…
1
204


