sparrow
sparrow copied to clipboard
sparrowwallet
[FEATURE] add support for construct tx with a sighash different than SIGHASH_ALL with a larger output than the input.
would be very powerful, if can be possible to construct transactions , with the other sighash types different than SIGHASH_ALL, like these ones: https://raghavsood.com/blog/2018/06/10/bitcoin-signature-types-sighash https://bcoin.io/guides/crowdfund-tx.html https://learn.saylor.org/mod/book/view.php?id=36341&chapterid=18919 Thanks
This PR, could be a very desirable and valuable implementation of signatures that enable a more versatile type of transaction for Bitcoin, and Sparrow is the ideal candidate to do it!
I think it's a great implementation for current code.
Cheer up and continue with the great work you are achieving!
It could be interesting in exchanges between peers without trust in 3rd parties
It is already possible to create PSBTs (and transactions) with different sighash types - from what I understand this issue is actually about creating transactions that would usually not be possible within a wallet (for example, creating an output that is larger than the funds available in the wallet).
I would like to understand the desired use case better. Supporting the crowdfunding use case is more than just allowing the creation of a transaction with such a large output - there must also be support for a funder to load the transaction in a wallet and add inputs to it, before passing it on to the next funder to add more inputs. This process doesn't seem very practical or private to me (over say a standard BIP47 type crowdfunding approach), but possibly I am missing something.
It is already possible to create PSBTs (and transactions) with different sighash types - from what I understand this issue is actually about creating transactions that would usually not be possible within a wallet (for example, creating an output that is larger than the funds available in the wallet).
I would like to understand the desired use case better. Supporting the crowdfunding use case is more than just allowing the creation of a transaction with such a large output - there must also be support for a funder to load the transaction in a wallet and add inputs to it, before passing it on to the next funder to add more inputs. This process doesn't seem very practical or private to me (over say a standard BIP47 type crowdfunding approach), but possibly I am missing something.
Thanks for your interest. Indeed, the point is to be able to create transactions with larger outputs. One of the possibilities, and part of what I am working on is to fund a 2-2 multi-signature wallet between two users who do not know or trust each other. These funds would serve as a deposit of collateral and payment on which they could make exchanges in the real world. Currently it is not possible with any wallet to create a transaction like this: alice sends 1 btc to [msig alice&bob 2-2] only if bob sends 1 btc too to [msig alice&bob 2-2]
( if you don't build the transaction in raw).
For other things a standard BIP47 crowdfunding tx isn't really a true crowdfunding is it more like a donation, the concept of crowdfunding is more like "funders fund if the project reach the funding goal", this way possibilitate a way to create p2p crowdfunding projects only if the tx reach the goal, in a more decentralized way.
Any possibility to decentralize p2p exchanges without trust might worth a try. Interesting proposal
