CrushBtc

I really can't take this anymore. That second confirmation step Yijie mentioned—how prominent is it? Has anyone ever made a cross-platform transfer? I'm genuinely curious what this second confirmation step looks like. I think this is a design issue: BN promotes UID transfers, and users are used to them. Even when transferring between different platforms, people will default to using a UID, right? But if UIDs collide across platforms, that's clearly a design issue. All I can say is that this isn't solely the user's fault.

This is basically a speedrun to getting your account burned, guys—check it out. Just be sure to use an alt account; OpenAI likes to settle old scores. But this idea is seriously brilliant.

Additional research: Are the credit cards linked to the banned accounts in any of these BIN ranges: 544015, 546400, 543502, 543799, or 512998? I suspect the virtual cards all use these BINs, and that the BINs ran into trouble, causing the accounts to be temporarily suspended. However, it looks like some people have had their accounts unblocked. Link:

No worries, Chinese people have their own way of doing things 🫡

Additional note: The account mentioned above is still active, and there’s also a 48team that’s still active, so the risk-control model is likely the problem.

Vote on why ChatGPT accounts are getting banned—let’s figure out what’s really going on together.

There was no email notification for this round of account bans. After logging in, all I saw was that the accounts didn’t exist. The reason is still a mystery: I have two Pro100 accounts, and my IP changes frequently. One is in a non-US region and one is in the US region, and I used both with sub2. One claimed the API quota and used about half of it on sub2. So my take is that this was another false positive from the risk-control model. If you’ve been banned, don’t panic—just appeal and wait for compensation.

Appeal portal:

Breaking: OpenAI may be banning accounts en masse. Plus, Pro 100, and Pro 200 accounts seem to be affected across all regions. The reason for the bans is still unclear, but it probably has nothing to do with reverse proxies. Check if your account is still active.

Anyone who has claimed this credit before should use it with caution. I’ve seen a lot of people on L site whose GPT accounts were banned. Generally speaking, OpenAI’s API platform has very strict risk controls. If you get banned, your account will be banned too. Codex, on the other hand, is very stable when accessed through a reverse proxy. If you’re connecting it to an external agent framework, definitely don’t use the API credits.

One more thing: when things are quiet, share some genuinely useful, substantive content—make sure it provides value.

I finally worked up the courage to do KYC. Obviously, I was afraid of getting flagged by risk control (and I’m still shaking). I went ahead and linked Stripe too. But I’m still short by so many impressions. Even just coasting gets me 1/5 of the way there, so I only need to put in 5x the effort, go from posting once a week back to posting daily, and I can get paid too. I should’ve qualified a long time ago, technically. I wonder if the numbers from before will still count when I qualify again.

When are Double 11 and Black Friday coming? I really want to pick up a top-tier server with a great network route.

I looked into it—it’s a bandwidth issue. The 128GB laptop only gets a little over 600, but the Studio is different; it gets 1,200. Keep it up, guys! I’ll try to upgrade to a 512GB Studio next year.

I deployed QWEN 3.8 27B 8-bit MLX locally on an M5 Max. Here are the results from the Pelican test: it took 12 minutes and 27 seconds to complete the task.

Inference setup:
Inference engine: Splash 1.4.1
Acceleration: DFlash 2 speculative decoding
KV cache: BF16, unquantized
Recurrent state: FP32
Thinking level: xhigh

Overall quality is pretty good. The only issue is that generation is too slow at 30 t/s.

The protocol payments are finally stable (supports direct opens and upgrades).

I’ve been looking for one-off orders to test all this time. Before, everything was handled through browser automation, which was very inefficient. Now that the protocol is working, we can handle more orders.

Going forward, we’ll primarily use the protocol, with browser automation as a fallback.

If you’re interested, guys, check out the link and show some support.

More services will be integrated down the road. We’re working hard on it.

I put together a quick recap of last night's incident. You can see the full timeline and a diagram tracing the hacker's fund flows here: Signing off to get some rest.

I’m going to wash up and call it a night. So far, it’s close to 6 billion, with some of it frozen. That’s just a drop in the bucket for BN, so it doesn’t seem like a big problem.

Tonight is the hardest to keep it together.

These are all EVM wallets. In addition, the following are suspected hacker addresses:

SOL bc1q0mtc2f5agpkvlq6hhahmfr3hlr55kyfjhl2mnm
BTC TG5iBMQPrDzJJAUM8GMVBf1hRaJ1wvzsGi
TORN AffzFDKZbyMiU11zmVBoAqD25ugpr7xoWWyRyGigBEaU

The total amount of funds potentially stolen exceeds $5 billion, and the theft is ongoing.

Shit, this foreigner's account balance is down.