azat (@howeeveerr) header
azat (@howeeveerr) profile picture

co-founder @trueholdxyz

London, UK
Joined October 2021
Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)Photo by azat (@howeeveerr)
We compared read-only API keys on 20 exchanges, from each exchange’s own docs. All 20 offer a key that can see your account and can’t touch it. Some expire if you don’t bind an IP, some never expire, two require an IP from day one. Sources: truehold.xyz/blog/read-only-…
44
In Web3Auth's design, a Google or Apple login wallet has its key split, and one part sits on Web3Auth's nodes until you sign in. Web3Auth paused that service at 21:13 UTC yesterday. If an app gave you a wallet at Google sign-in, ask who holds that part. nitter.gq/keplrwallet/status/211…
We have received reports of unauthorized transactions on some Keplr accounts created with Google or Apple login. We flagged this to the @Web3Auth team and have been working with them on the investigation since. Based on our initial assessment: if you created your Keplr wallet with a recovery phrase or a hardware wallet, you are NOT affected. If you created your Keplr account with Google or Apple login, your account may be affected. While we investigate: – Do not send new funds to that account. – Do not re-import or recreate it anywhere. – Google/Apple login is paused for now. – Trust updates only from this account. Ignore DMs or links offering “recovery”. We will share verified details and next steps here as soon as we have them.
33
Chainalysis's Nov 4 update also said logins were down, so customers couldn't yet reset the password it asked them to reset. If that password is also on an exchange account, change it there first. nitter.gq/WuBlockchain/status/21…
Chainalysis: Names, Usernames, Password Hashes, and Valid Tokens of All Users Were Exposed; Some Plaintext Passwords Also Leaked Blockchain analytics firm Chainalysis disclosed in an updated security incident notice that the names, usernames, password hashes, and valid authentication tokens of all users had been exposed to the attacker, and that some customers’ plaintext passwords were also leaked through a separate attack method. After detecting abnormal activity, the company suspended KYT transaction monitoring, address screening, and login services, and required all users to reset their passwords and rotate API keys where necessary. Previously, on October 30, Chainalysis first disclosed that it had been breached by a hacker using offensive AI agent technology; at that time it only confirmed that certain customer identity information had been accessed and said it had found no evidence that passwords or session tokens had been leaked.
9
Sui did this in May 2025: validators froze $162M taken from Cetus, then 90.9% voted for an upgrade that moved it to a recovery multisig. On Polygon the freeze is already in place. The fork would move POL out of an address without its key. nitter.gq/WuBlockchain/status/21…
Polygon Labs Member Proposes Hard Fork to Recover Approximately 70.49 Million POL Stolen from Polymarket and Binance A member of the Polygon Labs Validator Support Team has published a Polygon Improvement Proposal (PIP) suggesting a hard fork on the Polygon PoS mainnet to recover approximately 70.49 million POL stolen in two recent hacks involving Polymarket and Binance, valued at about $6.5 million based on October 29 prices. Of the total, Polymarket accounts for approximately 23.86 million POL, while Binance accounts for approximately 46.63 million POL. The related funds are currently restricted from transfer by block-producing nodes. The proposal aims to move the POL balances from the attackers’ addresses to recovery addresses designated and verified by the two institutions through a hard fork, without changing the total token supply. The proposal will be submitted for discussion at the Polygon Protocol Governance Call on November 5. If approved, client development and testnet rehearsals are expected to be completed in approximately two weeks.
27