I’m reporting a reproducible signing failure affecting Ledger hardware wallets when withdrawing assets from Kinetic.market on the Flare network (chainId 14). This is not an RPC or UI issue — the signing request does reach the Ledger, I blind‑sign it, and MetaMask fails immediately afterward. The signed transaction never reaches the network.
Summary of the Issue
When initiating a withdrawal from Kinetic.market using MetaMask with a Ledger hardware wallet:
- MetaMask constructs the transaction normally
- Ledger does receive the signing request
- I blind‑sign the transaction on the Ledger
- MetaMask immediately throws an error
- The signed transaction is never broadcast
- No transaction hash is produced
This indicates the failure occurs after Ledger signs, during MetaMask’s serialization or submission of the signed payload.
Environment Details
Ledger Firmware: 1.5.1
Ledger Ethereum App: 1.21.2
MetaMask Version: 13.30.0
Network: Flare Mainnet (chainId 14)
RPC: https://flare-api.flare.network/ext/C/rpc
DApp: https://kinetic.market/
What I’ve Verified
Flare RPC configuration is correct
Chain ID is correct (14)
Flare network is properly added in MetaMask
Ledger signs transactions normally on other EVM chains
The issue only occurs on Flare → Kinetic withdrawal
Kinetic support was unable to resolve this
I was muted for some unknown reason in the Flare Discord before reaching engineering support.
Why This Appears to Be a Serialization or Encoding Issue
Because the Ledger does receive and sign the transaction, the failure is not a transport issue, chainId mismatch, Ledger parsing rejection, or a MetaMask → Ledger communication failure
Instead, the failure likely occurs in one of these layers:
MetaMask cannot serialize the signed transaction
(common with large calldata or non‑standard fields)
The signed payload is malformed or incomplete
(MetaMask hardware signing bug)
The RPC rejects the signed transaction format
(Flare’s Coreth-based engine may expect a different envelope)
This behavior is consistent with complex contract calls on EVM chains where MetaMask’s hardware signing path is not fully compatible.
Request
Please escalate this to the Flare Labs engineering team or the maintainers responsible for:
MetaMask → Ledger signing compatibility
Transaction serialization on chainId 14
RPC acceptance of signed payloads
Kinetic contract call formatting for hardware wallets
I can provide logs, MetaMask errors, or the raw transaction data if needed.
This issue prevents Ledger users from withdrawing assets supplied to Kinetic on Flare and appears to be a chain‑level signing/serialization incompatibility.
Thank you.
I’m reporting a reproducible signing failure affecting Ledger hardware wallets when withdrawing assets from Kinetic.market on the Flare network (chainId 14). This is not an RPC or UI issue — the signing request does reach the Ledger, I blind‑sign it, and MetaMask fails immediately afterward. The signed transaction never reaches the network.
Summary of the Issue
When initiating a withdrawal from Kinetic.market using MetaMask with a Ledger hardware wallet:
This indicates the failure occurs after Ledger signs, during MetaMask’s serialization or submission of the signed payload.
Environment Details
Ledger Firmware: 1.5.1
Ledger Ethereum App: 1.21.2
MetaMask Version: 13.30.0
Network: Flare Mainnet (chainId 14)
RPC: https://flare-api.flare.network/ext/C/rpc
DApp: https://kinetic.market/
What I’ve Verified
Flare RPC configuration is correct
Chain ID is correct (14)
Flare network is properly added in MetaMask
Ledger signs transactions normally on other EVM chains
The issue only occurs on Flare → Kinetic withdrawal
Kinetic support was unable to resolve this
I was muted for some unknown reason in the Flare Discord before reaching engineering support.
Why This Appears to Be a Serialization or Encoding Issue
Because the Ledger does receive and sign the transaction, the failure is not a transport issue, chainId mismatch, Ledger parsing rejection, or a MetaMask → Ledger communication failure
Instead, the failure likely occurs in one of these layers:
MetaMask cannot serialize the signed transaction
(common with large calldata or non‑standard fields)
The signed payload is malformed or incomplete
(MetaMask hardware signing bug)
The RPC rejects the signed transaction format
(Flare’s Coreth-based engine may expect a different envelope)
This behavior is consistent with complex contract calls on EVM chains where MetaMask’s hardware signing path is not fully compatible.
Request
Please escalate this to the Flare Labs engineering team or the maintainers responsible for:
MetaMask → Ledger signing compatibility
Transaction serialization on chainId 14
RPC acceptance of signed payloads
Kinetic contract call formatting for hardware wallets
I can provide logs, MetaMask errors, or the raw transaction data if needed.
This issue prevents Ledger users from withdrawing assets supplied to Kinetic on Flare and appears to be a chain‑level signing/serialization incompatibility.
Thank you.