Martin Horák

Software & Crypto Engineer | Blockchain Security Specialist Focused on smart contracts, wallet infrastructure, and decentralized systems.

[Martin Horák @9FFSCB]

@weed1673 That usually happens when the order isn’t passing the exchange’s execution checks, most commonly liquidity mismatch, slippage too tight, or the route failing on the DEX aggregator.

If it’s repeatedly canceling, I’d want to see the exact swap route and error code, there are a couple of subtle fixes depending on whether it’s a liquidity pool issue or a wallet/nonce rejection.

[Martin Horák @9FFSCB]

@AndreiI27470074 Hey, That usually isn’t “funds locked” it’s almost always a Ledger app / ZEC derivation path or shielded-pool compatibility issue, especially after recent Zcash wallet changes.

Don’t try random swaps yet; you could make it worse. If you want, I can quickly help you isolate whether it’s Ledger Live, a network upgrade mismatch, or a transparent vs shielded address issue

[Martin Horák @9FFSCB]

@zacksCrypto101 Hey, MGUSD isn’t just a “drop-in token” on most platforms, it only goes live once liquidity routing, contract verification, and compliance checks are cleared.

Right now, there’s no confirmed deployment window I can safely quote. If you’re tracking it for trading or integration, I can walk you through what stage it’s actually at and what signals to watch before it hits the platform

[Martin Horák @9FFSCB]

@facap_ Hey, That usually points to a liquidity/transfer restriction issue or a taxed/paused contract state not just “market timing”.

What chain and contract are you on? If you share the CA, I can quickly tell you whether it’s a liquidity lock, trading toggle, or a honeypot-style restriction.

[Martin Horák @9FFSCB]

@Oregantweet Are you aiming for full protocol-level signing support on Flare, or just dApp compatibility through an abstraction layer?

[Martin Horák @9FFSCB]

@Oregantweet Hey, That request sits at the intersection of wallet signing architecture and chain support.

For Flare Network, adding support for Tangem Wallet isn’t just “enable it” it depends whether you want native key derivation support, or a WalletConnect-style integration layer

[Martin Horák @9FFSCB]

@ramenS001 Happy to help you map out the exact fix path if you want to go deeper into how to get it whitelisted/integrated properly

[Martin Horák @9FFSCB]

@ramenS001 Right now that’s not a wallet-side issue, it’s a token standard / integration gap on the Supra side or lack of native support in Tangem’s firmware/token registry.

If you’re trying to self-custody SUPRA in Tangem, you’ll need proper contract-level support. Otherwise the wallet won’t expose deposit/receive functionality safely.

[Martin Horák @9FFSCB]

@TimeIsMoneyHQ I just sent you a message, check your DM

[Martin Horák @9FFSCB]

@Fork_BTC Nếu bạn chia sẻ txid và loại địa chỉ, tôi có thể nhanh chóng cho bạn biết vấn đề là gì. Hãy theo dõi lại và gửi tin nhắn trực tiếp cho tôi.

[Martin Horák @9FFSCB]

@Fork_BTC Zcash hoàn toàn không sử dụng SegWit, nên đó là một sự hiểu lầm.

Nếu ZEC của bạn không hiển thị trong Trezor Suite, thường là do sự không khớp loại địa chỉ (trong suốt so với được bảo vệ) hoặc ví không đồng bộ đúng tài khoản/đường dẫn nguồn gốc, chứ không phải do chính mạng lưới

[Martin Horák @9FFSCB]

@BatscheBatsche Hey, That sounds like a failing display or hardware issue rather than a software one. Before doing anything else, can you tell me the wallet model and whether the screen is still responsive? I can help you determine if your funds are at risk and the safest recovery option.

[Martin Horák @9FFSCB]

@TimeIsMoneyHQ That error usually means the DAG→INK bridge service is temporarily disabled on the backend, not a wallet issue. Before trying random fixes, can you tell me which bridge URL you’re using and whether the transaction hash is being generated at all? That’ll help narrow down whether it’s a bridge outage or a routing/liquidity problem

[Martin Horák @9FFSCB]

@Atexascashx8 Hey, Sounds like a sync or backend issue. Which wallet version are you running, and are you seeing an error when broadcasting transactions? I know a workaround

[Martin Horák @9FFSCB]

@BaconExpat Nice. Before you stake, make sure you’re choosing the right validator setup and reward structure. Most people skip that part and leave yield on the table. Happy to walk you through it

[Martin Horák @9FFSCB]

@saunarob Yes, Blackhole can be accessed through Coinbase Wallet, but support depends on the network and connection method you’re using. What exactly are you trying to connect to, staking, swapping, or the Blackhole dApp? I can help you check the correct setup.

[Martin Horák @9FFSCB]

@TedGrizzlyDavis Hey, If you still have your recovery phrase, your funds are usually safe. The real issue is identifying why you can’t access the wallet. What error are you seeing? I can help you troubleshoot it before you risk making things worse

[Martin Horák @9FFSCB]

@fleety_99 That’s useful, but the real question is how those transfers are being classified and routed. Different exchanges and wallets trigger different risk models at the bank level. I’ve spent a lot of time analyzing the crypto compliance and payment rails side of this, there are a few details that usually explain why one person’s transactions pass while another’s get flagged

[Martin Horák @9FFSCB]

@Mecca36015511 A master reset wipes the device, so the only way back in is with the original recovery phrase. Also, a genuine Ledger device will never ask for your seed phrase during a normal connection process. Before entering anything, can you show me exactly where that prompt appears? It could be a phishing interface

[Martin Horák @9FFSCB]

@Quest_Crypto680 Some staking options on Ledger are legitimate, but the real question isn’t the wallet, it’s who actually controls the funds and where the yield comes from. In some cases you keep custody; in others you’re taking validator, smart contract, or counterparty risk. I never recommend parking a large principal until I’ve reviewed the exact staking product. Which coin are you looking at? I can show you the actual risks in 2 minutes.