Martin Horák

@JimBuck619 Trezor support is only one piece of the puzzle. The bigger question is how Secure Element integration, multisig compatibility, and Monero’s privacy model will be handled. Curious what use case you’re optimizing for?

@adam67104 respond to your dm

@adam67104 check your dm

@silvertopsolar Hey, TRX support is only the first step. Native Tronscan integration depends on Trezor’s signing and wallet-connect infrastructure. There are already secure workarounds if you need TRON access today, happy to point you in the right direction

@highplanes1 Hey, ElectrumSPV has limited hardware wallet support, so the issue is likely compatibility rather than your Trezor itself. What exact version of ElectrumSPV and firmware are you running? I’ve helped troubleshoot this before, there are a couple of checks that usually pinpoint the problem quickly.

@highplanes1 Hey, ElectrumSPV has limited hardware wallet support, so the issue is likely compatibility rather than your Trezor itself. What exact version of ElectrumSPV and firmware are you running? I’ve helped troubleshoot this before, there are a couple of checks that usually pinpoint the problem quickly.

@MathieuSarfati Bonjour. Avant de pouvoir vous aider à débloquer un portefeuille, il est important de vérifier son type, la plateforme utilisée et le problème d'accès rencontré. Si le solde est légitime, je peux vous aider à évaluer la situation et à identifier les options de récupération les plus sûres. Quel portefeuille utilisez-vous et quel message d'erreur ou restriction s'affiche ?

@P19806 Te sigo, sígueme de vuelta para que pueda contactarte directamente por mensaje directo.

@9FFSCB Pues dígame los pasos a seguir ¡ En safepall se ha hecho directamente (bep20 a eth)

@P19806 Si los tokens están en su Ledger, primero debemos verificar la dirección de la billetera, la red y si tiene acceso completo al dispositivo y a la frase de recuperación. Envíeme los detalles de los tokens y la dirección de la billetera, y le guiaré a través de los pasos a seguir de la manera más segura.

@roneyjanuario Hey, If your ledger shows 0 consumption while credits vanished, that’s usually not a wallet sync issue, it’s an accounting mismatch between allocation and settlement layers. I can help trace where the discrepancy originated if you can export the transaction history

@Richard54557517 If you want, send me the exact error message Coinbase gives when the transfer is rejected, and I can tell you what’s actually blocking it. Send a DM

@Richard54557517 Hey, What you’re describing isn’t normal. Coinbase can and does place additional restrictions on withdrawals to self-custody wallets when their risk systems flag a transaction, but there are usually ways to identify and resolve the specific trigger. I’ve helped users move funds from Coinbase to external wallets after repeated verification failures. Before trying again, I’d want to check whether it’s a withdrawal hold, account restriction, wallet-address risk flag, or a security review issue.

@0fbzorp Hey, Yeah. I can point you to a few Base analytics tools that break down wallet activity, PnL, token performance, smart money flows, and on-chain metrics. Drop the wallet address and I’ll tell you which metrics actually matter and how to read them

@zuhdiimohamad Hey, Maybe. If the tokens were sent to a scammer-controlled address, recovery is usually very difficult. But if you can share the transaction hash and the fake Ledger site you used, I can help trace where the funds went and check whether there’s any realistic recovery path before writing it off

@UsefulUpdatesJ Hey, If you sent WETH to a USDC deposit contract address, recovery depends on whether the receiving contract can recognize or access the token. What chain was it on, and do you have the transaction hash? I may be able to help you determine if recovery is possible

@bryancwatkins Hey, 72-hour holds after verification usually point to a risk-flag or compliance trigger on the transfer, not the ID check itself. What type of transfer was it, and did support mention the specific reason code? That detail usually tells you what’s actually happening

@f82james Hey, That’s because “instant transfer” and “instant withdrawal” aren’t the same thing. Coinbase lets you buy USDC instantly, but if you funded it with a bank transfer, they’ll still place a hold before you can move it off-platform. The real question is what payment method was used, there are a few ways around the wait depending on how the deposit was made.

@CornellOusleySr Hey, That’s a major red flag. When a bank clears your account but Coinbase flags it for suspicious activity, the issue is usually deeper than the transaction itself. I’ve seen this before, happy to help you pinpoint what’s actually triggering the hold

@RyukiNumb Hey, This usually points to a compliance, security, or account verification restriction, not a random error. Coinbase rarely limits withdrawals without a trigger. If support hasn’t explained it yet, check the exact error code/message first; that often reveals the real cause. Feel free to DM the details and I’ll help you decode it

@Hoghead1961 I understand your frustration. A wallet being connected only by USB and not actively in use should not lead to unexpected asset movement. If you can share the exact wallet model, firmware version, and what you mean by “MTed,” I’d be happy to help analyze what happened and determine whether it was a device issue, a security compromise, or something else. The details matter

@AlexRealCrypto This sounds like a duplicate submission issue between Ledger signing and wallet broadcasting. Have you checked whether it’s actually two separate tx hashes on-chain or just the wallet rebroadcasting the same signed transaction? I’ve traced this exact behavior before, happy to help pinpoint where it’s happening