Cannot send XSN from Trezor Device about block-explorer HOT 6 OPEN

Might it be, that you tried to send a bigger ammount of XSN?
If so try the new transaction ammount "Very high" and have a look if it helps.

from block-explorer.

Indeed, there is a issue that when dealing with lots of UTXOs, the fee amount may not be enough, right now its computed in a naive way instead of estimating how much is required.

The common way to solve this for now, is to send smaller amounts, or choose the highest fee.

from block-explorer.

Seems to be very specific the OS. Works without a hitch on an Arch distro. KUbuntu (latest build) is where this issue persisted. Could be a weird configuration or something else related to Trezor - I don't want this to be too much of a time sink or worry.

from block-explorer.

I don't know if you are hitting a different issue, in this case, we detected that the fees are being hardcoded instead of taking them as the wallet does (we take 1000 satoshis instead of 1000 satoshis/kb), when the transaction gets big enough, the network rejects it due the fee being not enough.

This will be fixed.

from block-explorer.

I experienced the same issue just now. Trying to send 10, 30 and 50 xsn from my trezor to another address. With a fee of 100satoshis
All three the transactions failed without error message or transaction ID
I was able to send all three of the amounts when selecting 500 satoshis.

@AlexITC what do you mean with "when the transaction gets big enough"
I don't view 10xsn as a large transaction? Or are you talking about transactions per minute on the network?

[edit]
I noticed that the actual transaction fee shown on xsnexplorer.io is 0.000005
And I just now realized that we are talking XSN satoshis. Not BTC satoshis. Makes sense

from block-explorer.

"when the transaction gets big enough"

The amount is irrelevant but the number of outputs required for the transaction is what get us the need for a higher fee, ideally, the integration should compute the fee automatically like xsn-qt does but we haven't fixed that.

from block-explorer.