Ledger’s (@Ledger) signature reporting only hits wallets built on its Ethereum or Solana kit.
Lace, Yoroi, and Eternl sign Cardano with a separate library, so your ADA signatures there aren’t reported this way.
Keeps your metadata yours and not someone else’s.
Follow up: I found something even more absurd ⚠️
Since context-module 2.7.0, Ledger's SDK sends a SECOND report on every signature, to /v2/blind-signing-events, now with the function selector too.
It's on by default, and unlike v1, the SDK gives no option to replace or disable it. So any wallet that turned off the v1 report starts sending again after a routine update.
Their signer kit changelog says it plainly: "Require context-module 2.7.0 (sign reporter enabled)"
https://t.co/qGGBH5umaF
https://t.co/JxO0AUt0hx
Alongside @ambire, @Rabby_io also caught the v1 report from my post below 👏 They replaced Ledger's v1 reporter with a local callback that sends nothing:
https://t.co/hNMwpgVfPN
But they're still on 2.1.0, which has no v2 reporter yet. The day they update, v2 goes out anyway unless they catch it. So heads up, fellow wallet devs: the builder has no setter for the v2 reporter, so you need to gate `signReport` on the built module yourself.
Ambire is safe because we're not on 2.7.0. Since Ledger gives no setting for the v2 reporter, our next SDK update overrides it in code, so it follows the same opt-in privacy toggle we already use for v1 (off by default).
@Ledger, is this a test to see if we're paying attention?
I guess at this point we should review every SDK update line by line.
Across (@AcrossProtocol) lost control of its domain.
Its registrar believed a stranger's story, and that person could disrupt your life. If you have a product or service that runs through a company that has a support desk, you can also be affected by this.
The Across domain is currently down while we secure it against an attack from earlier today.
At ~18:45 UTC, a social engineering attack on @Namecheap (our domain registrar) gave a bad actor control of the Across domain.
Within 15 minutes of this attack, we were alerted and immediately worked to shut the site down. SEAL911 marked across.(to) as a phishing site with major wallets, and Cloudflare worked with us to mark the domain as at risk, and later pulled the site’s DNS records.
At the time of this post, Across.(to) is fully down, and the phishing site is no longer available.
In the brief period before Cloudflare fully blocked the malware site, some users who visited across.(to) may have been affected. No third-party integrations or API users were affected. Users who believe they were affected should DM us with transaction details and revoke attacker permissions (see next tweet for details).
Despite our best efforts, @Namecheap has been unresponsive, and we have not been able to properly secure the domain to bring Across’s services back up. Across’s frontend and API will remain down until we can properly secure them. We will always put user safety first.
Across’s domain was fully locked down with best-in-class security practices; this unauthorized takeover should not have been possible. We will be investigating this deeply and will provide a post-mortem on how this domain takeover was possible once we have more information.
Logging in with Google isn’t holding your keys.
A flaw at Web3Auth (@Web3Auth) exposed keys behind some Keplr (@keplrwallet) social login wallets. Seed phrases and hardware wallets were fine.
Ada holders: no seed means someone else’s setup may hold part of your key.
🚨 Social login wallets exposed
A flaw at @Web3Auth exposed the private keys behind some @keplrwallet Google and Apple login wallets.
How the login works, the rescue, the numbers, and what it means for Cardano 👇
https://t.co/jEKiJfTdpg
Not financial advice.
Paraguay’s Ueno Bank shut overnight.
About 2.9 million customers’ savings frozen.
When your money sits on someone else’s books, they control access.
That’s why Ada holders keep their own keys.