加密货币付款现在更简单、更划算：

• 优惠 10%：用加密货币付款，所有套餐和积分包均享 10% 优惠。向专属地址充值 USDT 或 USDC，积分多送 10%。
• 直接购买套餐：选择套餐（按月或按年）或积分包，可用 BTC、ETH、USDT、USDC、SOL 等 150 多种币付款，无需银行卡。
• 金额一目了然：付款前会显示实际要支付的金额。
• 加密货币付款页面现已支持 7 种语言。

Three problems people told us about. All three are fixed. Here is what was wrong, and what changed.

Restyling a video could fail with a wall of raw text. If you sent a clip to be restyled and something was wrong with it, you got a server error with the upstream service's raw response pasted into it — in English, as machine output. Two things were hiding behind that: the clip was longer than the model accepts, or the model declined the wording of your instruction. Both are things you can fix in a few seconds, and neither was being said plainly.

The length limit (2-10 seconds) is now checked when you pick the file, before anything is spent, and the clip is refused with its own length shown. When the model declines an instruction, you are told that in one sentence, with a suggestion to reword it or pick another model. And when a job fails after credits were taken, the credits come back — that path existed but did not actually return them, which we have corrected.

Training a character from your own photos would not start. If you picked roughly ten photos or more and pressed Start Training, it failed the instant you pressed it — "Failed to fetch", nothing in the log, every single time. Your photos were being sent at full camera size, so the request went over our upload limit and was turned away before it ever reached us. That is why there was nothing to investigate on our side.

Photos are now resized before they are sent — long edge 1024, which is the size the training uses anyway, so nothing that matters for a likeness is lost. Twenty photos go through. Your previews still show the originals. If a set is still too large, you are now told how large it is and what to do, instead of a silent failure.

A subscriber reported this on September 16 with 17 photos. Fixed on the 17th, and training has run normally since.

A crypto invoice could arrive for more than the price on the page. Reported from India in late August: the page showed ¥1,960, the invoice came for about $65. The regional discount was being applied to what you saw, but not to what you were billed. That was our mistake, not a currency quirk.

The invoice is now built from exactly the same regional price the page shows, and the response records which region and rate were used, so a gap like that cannot pass unnoticed again. If you backed out of that invoice without paying, the one you get now will match the page.

While we are here: you do not need crypto for the dedicated pages. Someone asked this and it is a fair question, because the crypto option is prominent. Any regular plan from Basic upward, bought by card, already includes access. Crypto is there for people who would rather pay that way, not as a requirement.