Coinomi send tx stuck

[willy]

The apps mentioned use their own methods to create transactions, which are not necessarily idenditcal with the routines used inside the official Nu/Nud builds.

If those methods are outdated (in this case: include a fee that’s too low), their transactions will be rejected by the official client.

[MatthewLM]

I could release an update with the correct fee (0.02nbt right?), but then if it goes back down to 0.01nbt, it will be too high. I can look into dynamic fees but that will no doubt involve significant development work. The question is, will this be resolved by returning the fee to 0.01nbt, or should I update it?

[willy]

I can look into dynamic fees but that will no doubt involve significant development work

Dynamic is the way to go here, I suppose.
Can nubitsj/nudroid discover the price itself or does it need an external feed?
I can offer integrating a tx-feed on anton… which of course can be changed inside the wallet by the user if wanted.

[MatthewLM]

It would make most sense to calculate fees from examining the fee votes in the blockchain which can be done via nubitsj. This would have to wait for a future update though. For now I can change the hardcoded fee, though it makes no sense to do so if the plan is to return to a 0.01nbt fee.

[willy]

but then if it goes back down to 0.01nbt, it will be too high.

Maybe that 1 cent has to work for the interim period… Question is: What happens if the TX fee keeps rising further?

[mhps]

It would make most sense to calculate fees from examining the fee votes in the blockchain

If the fee is continuously changing every block (e.g. a moving average) then the valid fee has to be within a tolerance range (e.g. 0.00214586 +/- 0.00000100 ) or the fee paid at GUI inputing time or broadcasting time might be outdated by the time the tx is processed by a node. I don’t remember there is a tolerance parameter defined.

[Nagalim]

t would make most sense to calculate fees from examining the fee votes in the blockchain which can be done via nubitsj

You can’t just use the getinfo RPC command? That’s what I did in my nuauction code.

[MatthewLM]

I could provide the information via a server, but it would be better to have the app calculate the fee itself. It would have to follow the same algorithm as the main client.

[Nagalim]

Got an email from CTO of coinomi, they’re gonna release a hot-fix soon.

[cryptog]

So. Should we revert to 0.01 or leave it as it is at 0.02?

[Nagalim]

I’m still voting 0.05 nbt and 10 NSR. I’m still not convinced this could have been done in a better way.

[cryptog]

So the solution for any party using nubits is to automatically adjust…

[Nagalim]

Nu 2.0 which contained the code was a mandatory update. People were given time and notice. We can give them more time and more notice, but how much is enough? How do we know when we’re ‘allowed’ to raise the fees?

[cryptog]

I agree. If they do not, this is because they do not care enough. What abouy nudroid?

[Nagalim]

If we want to use this as a warning shot so everyone running a hot NBT wallet has a few days to realize there’s an issue then switching back down so Txns go through and wallets aren’t all messed up and stuff, we can do that. We are most likely in the process of doing that anyway with the datafeeds switched over.

[cryptog]

the datafeeds switched over.

what do u mean?

[Nagalim]

you and cybnate are both voting 0.01 on the datafeed right?

[cryptog]

I have reverted to 0.01 from 0.02. But I am not sure if it is meaningful.

[zoro]

yes, no good to go back and forth. we made a choice, now we should support that choice.

[erasmospunk]

Hi all, I pushed a quick fix for the Coinomi wallet to fix the fee issue. If you have any stuck transactions fresh the wallet, you would need to resend the transaction (if it is still stuck in the mempool, send us a message).

Eventually we will add dynamic and user configurable fees to avoid those kind of issues.

Sorry for the stress this caused you.