-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lower fixed minimum sendable amount in Leather #5739
Labels
area:bitcoin
enhancement
enhancement-p2
Critical functionality needed by few users, with no clear alternatives
Comments
314159265359879
added
enhancement-p2
Critical functionality needed by few users, with no clear alternatives
enhancement
area:bitcoin
labels
Aug 7, 2024
@kyranjamie wdyt of the above proposal? |
kyranjamie
added a commit
that referenced
this issue
Aug 12, 2024
Thanks for the proposal @314159265359879. Why 515 specifically? Per advice here, perhaps |
Ignore my 515, that was a mistake 546 is excellent. PR, looks good. |
kyranjamie
added a commit
that referenced
this issue
Aug 15, 2024
kyranjamie
pushed a commit
that referenced
this issue
Aug 26, 2024
## [6.46.0](v6.45.2...v6.46.0) (2024-08-26) ### Features * change balance load logic, closes leather-io/issues[#227](#227) ([faf71fb](faf71fb)) ### Bug Fixes * add default true to show settings to make sure it shows for locked screens, closes [#5777](#5777) ([96b2990](96b2990)) * do not capitalise add network ([5258d7e](5258d7e)) * empty space in settings dropdown ([d33df6f](d33df6f)) * failing ledger test ([67799fe](67799fe)) * fix formatting of add network ui, closes leather-io/issues[#5735](#5735) ([8a76b5f](8a76b5f)) * fix issues with alignment of page headers ([ea76352](ea76352)) * **ledger:** support stx_signMessage, closes [#5756](#5756) ([92a99ed](92a99ed)) * make headers more composable, prevent logo hover, closes leather-io/issues[#4597](#4597) ([3f2e359](3f2e359)) * minimum bitcoin spend, closes [#5739](#5739) ([34405f6](34405f6)) * prevent illegal constructor error ([a774b66](a774b66)) * remove blockstream from tests and add network form ([86af370](86af370)) * remove card from retrieve taproot ui ([27ca424](27ca424)) * **sentry:** sample performance units, closes leather-io/issues[#249](#249) ([3b6a5d8](3b6a5d8)) * tool to clear submitted tx state ([1e6f63d](1e6f63d)) * update ui library and deprecate footer ([0f5cfa2](0f5cfa2)) * validate dom nesting console error ([fe21fa8](fe21fa8)) ### Internal * differentiate action popup and popup, improve responsiveness and refactor footers, ref [#5260](#5260) ([2cae2a2](2cae2a2)) * hide lock option if wallet already locked ([b43cf8b](b43cf8b)) * post-release merge back ([686a823](686a823)) * remove back button on unlock screen and remove fragment ([9bc13ab](9bc13ab)) * update monorepo dependancies ([427f82f](427f82f)) * update prettier ([9e7d404](9e7d404)) * update tanstack libraries ([1486f5c](1486f5c))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:bitcoin
enhancement
enhancement-p2
Critical functionality needed by few users, with no clear alternatives
Currently the wallet has a hard set limit of 6000 sats when sending bitcoin. In most cases this is helpful because it prevents users from accidentally sending small amounts that are likely to become uneconomical to use after sending.
It turns out sometimes users want to send a small amount even if the resulting UTXO is likely to be uneconomical afterwards. For example to meet whitelist/mint conditions for an ordinal inscription series.
I suggest lowering to 515 sats.
Another option would be to show a notice when a user tries to send less then 6000 sats but then let the user proceed after clicking they understand the risk. So we do not prevent sending small amounts but we do caution the user when they try it. Much like we do when we detect abnormally high fees.
The text was updated successfully, but these errors were encountered: