IDUSDT
Everest / Tether USD
crypto Composite

Send the total to your hardware wallet in a single transaction, then forward them in smaller transactions from there. That way you only have to do the ID verification once.

I did a deep dive into the headers of both emails (the fake "Entropy Bug" alert and the follow-up "Phishing Warning"), comparing them to an authentic BitBox newsletter from two months ago. Here is the technical breakdown:
**The Technical Evidence from the Headers**
All three emails—the phishing attempt, the warning, and the older official newsletter—originated from the **exact same legitimate Brevo (Sendinblue) marketing account** used by BitBox:
* **Sending Infrastructure:** All emails were routed through the same Brevo IPs (`77.32.149.25` / `77.32.149.26`via `shared-p100-i2...brevo.net`).
* **Client Account ID (**`X-Mailin-Client`**):** Identical across all three emails (`4943728`).
* **DKIM Signatures:** All three passed cryptographic verification (`dkim=pass (header.d=bitbox.swiss)`). They were signed using BitBox’s official domain keys.
**What Actually Happened**
1. **Third-Party Email Service Compromise:** The BitBox hardware was **not** hacked. Instead, attackers gained unauthorized access to BitBox’s marketing/newsletter service account (Brevo/Sendinblue).
2. **The Phishing Blast (Mail 1, Campaign 435):** The attackers leveraged this compromised marketing account to send out the fake "Entropy Bug" panic email with the phishing link to the entire mailing list.
3. **The Official Countermeasure (Mail 2, Campaign 436):** The BitBox team quickly detected the breach, regained control of their Brevo account, and sent out an authentic warning to all subscribers roughly 45 minutes later using the same email campaign tool.

It is Coinbase to Hardware Wallet. I won’t say the name here but it rhymes with Brezor. Haha. I called customer support and they are insisting on a 72 hour waiting period despite me successfully completing the ID verification. My Coinbase debit card is also declining due to this hold on my account. My kids each have hardware wallets. This is an ~~easy~~ way for me to send them cash.

No, I have used Coinbase for about 10 years. I verified my ID when I opened my account send allowance to my children’s hardware wallets.

Is this your first transaction with Coinbase? I had to go through ID verification when I started depositing dollars and Bitcoin into Coinbase. But after that I have been able to freely send out any Bitcoin that I have in my wallet.

Despite uploading my ID and taking a 20 second selfie video, the transfer is held up by Coinbase! I have three more wallets to send allowances too, what the heck is going on??

Hi u/Corey_In_Texas,
Thanks for sharing your ticket ID, we'll escalate this to the appropriate team.
— Binance.US Support

Yes 100%. Not financial advice: I feel DCA is the way to go. There are people documenting and sharing this on reddit that has proven it's the best long term strategy for most.
Lump sum can work great or burn you depending on how the market swings.
I've read about exchanges from the start, so you can imagine my skepticism to use any that aren't established. That being said, I was suggested to use Coinbase and I've been with them for about a decade now. Sure I've had issues, but they're relatively minor (have to re-upload ID and other small things) but never make issues.
I've moved crazy amounts of money (for me) and never had an issue. I've read a lot of complaints about them, but they haven't failed me once.
I also have their black Amex credit card and get 4% BTC back on the first $10k monthly spend, after that I get 2% BTC back unlimited.
And being a coinbase one member, I get I think 3.5% back in USDC or BTC for holding USDC which pays for the monthly fee. And they also give you discounts for being a member to tax management and filing applications. This is the most useful part!

The Liquid exploiter and Blockstream have been communicating through messages embedded in Bitcoin transactions, with parts of the exchange encrypted so outside observers couldn’t read them.

On **September 8**, the exploiter announced a change in how they would communicate:
>All messages will be in plaintext.
**Transaction ID:**
`1d690f3b96b878067f3a445b74dfb8fab4201c0455d88ac98cc14a927e7858d7`
On **September 9**, a subsequent plaintext message made the dispute public. Two excerpts:
>
And later:
>Anyway we are going to publish the privatekey to decrypt our conversations afterwards.
The message demanded payment from Blockstream’s own funds and warned that refusing would leave holders facing a 15% loss. That is the sender’s demand and warning—not evidence of an agreed bounty or an independently established outcome for holders.
**Transaction ID:**
`f7055f6c8dd00f404e48c12483ae740180f658db206733505bb27b015e579588`
What makes this interesting is the distinction between a public transaction and a readable conversation. The exchanges were already visible on Bitcoin, but the encrypted content wasn’t. Now the exploiter is making their demands readable to everyone and saying they will release the material needed to decrypt the earlier exchanges. Blockstream, meanwhile, reportedly continued replying with encrypted messages.

Ticket ID: 131695710
User ID: 613889428
Issue Description:
The customer support agent is unresponsive. 
Binance.us is holding more than $5,000.00 USD and I cannot access ANY of my money despite completing the KYC process to the highest levels.
Account is still restricted for KYC review despite having completed Advanced Verification, submission of bank statements and completing the questionnaire.

Fair questions — the screenshot only shows the headline numbers.
“Qualified” means the model’s originally published TouchRate estimate was at least 70%. So the filter is based on the estimate attached to the forecast not on whether it later turned out right.
Each published range has a defined 30, 60 or 90-minute validity window. A hit means the market reached that range within its window.
The hit rate is hits divided by hits plus misses with each completed range counting once. Pending, invalid and cancelled records are excluded.
We show the overall rate alongside the qualified rate plus evaluated range counts and results by horizon.
Your point about showing the qualified sample size alongside its percentage is fair too.
The individual forecast view is probably the most useful part to explore: you can look up a forecast ID and compare its published ranges with what the market actually did afterwards.
That doesn’t turn a hit rate into a trading return, but it gives you something concrete to examine beyond a headline percentage.
I’d be interested to hear what you think of that level of detail.

Hello there,

We checked your case ID and found that our chat support team has already given you the necessary information through chat. Please understand that we’re unable to ask for or disclose personal information on social media. If you have additional questions about your case, please contact us through chat. Thank you for your understanding. \^BT

1 As it is our mission and commitment to provide better and reliable services for all Bitfinex users, we require our users to update and/or provide Know-Your-Customer information from time to time in order to maintain the level of integrity and compliance required by international anti-money laundering as well as counter terrorist financing policies.

Accordingly, please provide us with the following details:
* Reasons for transfers from and to your Bitfinex account;
* A clear and detailed explanation your account activity and objectives.
* A detailed explanation of the sources of all funds deposited to Bitfinex
* A proof of source of funds confirming how the deposited funds were originally acquired.
* A detailed description of the destination you are sending your funds to from your Bitfinex account
* Have you ever opened and used any other account(s) on Bitfinex? If so please provide the user name(s) and email address(es) of any account ever opened. explain why you operated more than one account, if you have.
In addition to answering these questions, we will need you to provide us with both of the following documents **1. a scan of your current government-issued ID** and **2. a photo of you holding your photo ID.** Also, please make reference to Bitfinex in a note with the date the photo was taken and your signature displayed in this last picture. Make sure the image uploaded includes your full face and that all ID details are clearly readable in an image that is **at least 6 megapixels resolution** taken under correct light conditions. The images need to be in JPG format and need to be the original images generated by the camera used

2 We would like to understand how did you initially invest in cryptocurrency? Please clarify which exchange you used, which cryptocurrencies you bought, in which year, which trading methods you used. Please provide supporting documents (e.g. credit card/bank statements showing the purchase of funds, exchange funds history, email confirmations, etc.)
We would also like to understand how did you initially source your funds to invest in cryptocurrency. Please clarify whether the funds were sourced from salary, business income, inheritance, sale of assets, savings etc. along with supporting documentation.
3 You mentioned that the funds invested into cryptocurrencies were derived from your salaried income. We request you to provide us with supporting documents in the form of an employment contract and pay slips. 
Additionally, you stated that you had accounts on Coinbase and kraken. Please provide us with supporting documents such as screenshots of the dashboard and transactions history page and/or email confirmations of account creation and transactions alerts.
He tenido que rastrar el correo y algunas capturas antiguas y excels para ver si puedo recuperar mi cuenta y mis Euros...tremendo cacheo se estan montando los amigos...

Hello there,

Upon reviewing your case ID, it seems our chat support team has already provided the required information in the chat. For security reasons, we cannot request or share any personal information over social media. If you have any other concerns about your case, please ask via chat. Thank you for your understanding. \^BT

Hello there,
Can you please share your Case ID so we can check? \^BT

Sounds like the wallet recovery worked, but the Seeker ID may need a separate recovery path. I’d avoid entering the seed phrase anywhere outside the official Seeker/Solana Mobile flow and contact official support if the ID is still tied to the old device.

Oof, that's a frustrating loop. The Seed Vault restores the wallet keys but the Seeker ID is actually a separate on-chain identity tied to the previous device's hardware, so restoring just the wallet won't bring the ID back.

You'll need to go through the Seeker ID recovery flow specifically. There should be an option during setup to recover an existing ID, usually using the seed phrase from the ID itself (which might be different from your wallet seed). If you didn't back up a separate ID seed phrase, you might be stuck unless the old device can be wiped remotely.

**Hi everyone,**
I’m having trouble recovering/accessing my previous **Seeker ID** after switching to a new Seeker phone.
Here’s what happened:
1. I previously had a Seeker phone, which I unfortunately had to return.
2. Before returning it, I saved the **seed phrase for the wallet that was created on that Seeker**.
3. I now have a new Seeker phone.
4. I used the **Seed Vault** on the new device to restore the wallet using the seed phrase from my previous Seeker.
5. The wallet was successfully restored, but when I try to use it, I get the following message:
>
So, it looks like the wallet itself has been successfully recovered, but the **Seeker ID is still associated with my previous device**.
My question is: **How can I recover or log back into my existing Seeker ID on my new Seeker phone?**
Is there a way to transfer/recover the Seeker ID using the wallet or seed phrase, or do I need to unlink the ID from the previous device somehow?
Any help would be greatly appreciated!

This article doesn’t prove what you’re claiming. It’s about Microsoft’s GDID, a persistent identifier associated with a particular Windows installation, and investigators correlated that with IP history, account records, and other evidence to identify the suspect.
That is not the same as “every device has a device ID that any government agency can track you with.”
If I visit a government website from an iPhone over a properly working VPN, the site does not automatically receive some universal device ID that uniquely identifies me. There are other ways a device or person can potentially be fingerprinted or identified, but that’s a very different claim.

Send the total to your hardware wallet in a single transaction, then forward them in smaller transactions from there. That way you only have to do the ID verification once.