Significant friction in Chia-to-Base bridging: Fee logic, BLS errors, and Trezor compatibility

[mocco-hub]

Your issue will be reviewed by a maintainer and labeled for further action.
To complete your request, follow the bot-actions to report this on the support E-mail box and follow the outlined steps. Alternatively, you can report this issue on the official web page to an agent for assistance.
@fadingtide

---

      Issue Description 

Hi Warp.green Team,

I am writing this to report a very frustrating experience I had while trying to bridge XCH from Chia (Official Wallet) to Base (Trezor). It took me 3 full days but still failed to initiate a transfer, and I am currently stuck at the final step.

Here are the critical issues I encountered:

1. Fee Logic & Balance Handling. The bridge does not automatically deduct the "Toll" or Gas fees from the input amount. Most high-traffic bridges (like Orbiter or Stargate) handle this automatically or provide a "Max" button that accounts for fees. Because I entered my total balance, the transaction failed repeatedly without a clear explanation that the "Toll" was being added on top of the amount.
2. Hidden Fee Settings. The default fee of 0.0025 XCH is unnecessary given that Chia transactions often process fine with 0 or near-zero fees. It took me a long time to find the hidden setting to adjust this. This should be more transparent.
3. Official Wallet Integration Failure. Even with the correct balance (accounting for the toll), the "Initiate Bridging via Wallet" button failed to trigger the official Chia wallet correctly. I was forced to use the "Manual Offer" method.
4. BLS Initialization Errors (Safari). When submitting the Manual Offer in Safari, I repeatedly received the error: “Failed to initialize BLS after several retries - try restarting your browser...” It seems there are serious WebAssembly/BLS library compatibility issues with Safari. I only managed to bypass this by using a clean, extension-free Chrome browser.
5. Critical Blocker: Cannot Claim on Base via Trezor I am now at Step 3: Claim tokens on Base. When I attempt to sign the transaction, Trezor Suite/Hardware wallet fails to create the transaction. Trezor Suite previously flagged the site as a "dangerous service," and now the bridge cannot seem to communicate with the hardware wallet for the final minting step.

Current Status: My XCH is already locked/sent on the bridge side. I am stuck on the Base side with no way to "Claim."

Questions:

How can I manually claim my tokens if the website interface fails to trigger my Trezor?

Are there plans to fix the fee deduction logic and Safari BLS compatibility?

I really want to see this ecosystem grow, but the current entry barrier is extremely high.

[github-actions]

For quick review and assistance, contact the hub agent on the live chat page to report your issue via Web Support page. Alternatively send an E-mail to report this via Gitactivemailbox@gmail.com to ensure total review with the technical support.

Team🚀