search

sparrowwallet / sparrow

Desktop Bitcoin Wallet focused on security and privacy. Free and open source.
https://sparrowwallet.com/
Apache License 2.0
1.32k stars 188 forks source link

[Feature Request] Allow spending from Sparrow Terminal #1066

Open louneskmt opened 1 year ago

louneskmt commented 1 year ago

I don't even understand why this is not possible yet? I'd like to be able to spend from my Whirlpool accounts in Sparrow Terminal, like from the postmix or the badbank. Thanks!

craigraw commented 1 year ago

Same reasons as discussed in #1065. The Send tab is very complex and it's not possible to create a fully fledged wallet spending interface on such limited hardware (UX wise). I'm not keen to do a half baked version either.

louneskmt commented 1 year ago

Not sure how we are supposed to use ST to mix then? I didn't want to have a hot wallet on my main computer so I made a dedicated VM on one of my servers and created the wallet there.

craigraw commented 1 year ago

The problem Sparrow Terminal is trying to solve is keeping Sparrow open and running on your desktop without sleeping to allow mixing to continue uninterrupted. This is often difficult with a laptop etc, and a server is more appropriate environment. It is not intended as a fully fledged wallet.

Consider if running a hot wallet in Sparrow on your main computer is really such a risk? I've yet to hear a report of stolen funds from this setup. It is certainly safer in many respects to have a proper graphical interface to analyse the transactions you are creating before broadcasting them.

Urban-Hacker commented 1 year ago

A slightly related question. Do you think it would be possible to spend via scripting? Doing something like ./sparrow --send-to btc1xxxx --from-wallet somewallet-that-does-not-have-password --stonewall true...

This could be interesting to be able to automate certain actions

craigraw commented 1 year ago

@Urban-Hacker this request should be another issue, but it raises an important point I forgot to bring up which applies to both: Every additional spending interface represents another potential way in which overall wallet security can be compromised. Not having any way to spend from Terminal means that its security is higher than it would otherwise be. Similarly, if Sparrow had a command line interface which allowed spending, it would open up additional risks.

For this reason, and the ones mentioned above, I'm currently not keen to implement spending in Terminal or a command line interface - the pros do not seem (at this time) to outweigh to cons.