Corey

To reproduce: - Create a transaction for 5000 sats. - Tap "Continue". In a high fee environment the fee should get set to "Custom" at a lower sat per vByte....

This is intentional, expected behavior that's been discussed on multiple occasions and prevents users from losing sats. I would, in earnest, consider it unethical to remove that check. Even attempting...

I would disagree. It's a vital check and should not be removed. Again, even if we removed this check in Bitkit most services and Electrum servers will still refuse to...

@JeanlChristophe & @BitcoinErrorLog, I think the only safe way to expose a high-fee bypass to the user in Bitkit would be to have them intentionally trigger the Send flow from...

Can you please check and relay what your fee estimates are in Settings?

Thanks! That looks about right. I'm going to look into how we pass these fees off to LDK to ensure we're doing it correctly. It is possible that LDK determines...

@Jasonvdb, think we could be overpaying due to [this](https://github.com/synonymdev/bitkit/blob/11bff79a5b8fb57dd4d89e0083ad40c91fbfc48e/src/utils/lightning/index.ts#L221C1-L221C5) setting? If I remember correctly, don't we have that one configured quite a bit higher to ensure it doesn't cause a...

This should be resolved as of the latest commits. Will close shortly unless others are still reporting this as an issue.

Replace `nodejs-mobile-react-native` functions with Rust functions via UniFFI using the following: - [Android](https://forgen.tech/en/blog/post/building-an-android-app-with-rust-using-uniffi) - [iOS](https://forgen.tech/en/blog/post/building-an-ios-app-with-rust-using-uniffi)