Here is the problem I'm trying to solve with this idea: Lets say you create an address, publish the address on your blog, and tell all your readers to donate $0.05 to that address if they like your blog. Lets assume you receive 10,000 donations this way. This all adds up to $500. The problem is that because of the way the bitcoin payment protocol works, a large chunk of that money will go to fees. If one person sent you a single donation of $500, you would be able to spend most of the $500, but since you got this coin by many smaller UTXO's, your wallet has to use a higher tx fee when spending this coin.
The technical reason for this is that you have to explicitly list each UTXO individually when making bitcoin transactions. There is no way to say "all the utxos". This post describes a way to achieve this. I'm not yet a bitcoin master, so there are parts of this proposal that I have not yet figured out entirely, but I'm sure other people who know more could help out. **OP_CHECKWILDCARDSIGVERIFY** First, I propose a new opcode. This opcode works exactly the same as OP_CHECKSIGVERIFY, except it only evaluates true if the signature is a "wildcard signature". What is a wildcard signature you ask? This is the part that I have not yet 100% figured out yet. It is basically a signature that was created in such a way that expresses the private key owners intent to make this input a *wildcard input* ** wildcard inputs ** A wildcard input is defined as a input to a transaction that has been signed with OP_CHECKWILDCARDSIGVERIFY. The difference between a wildcard input and a regular input is that the regular input respects the "value" or "amount" field, while the wildcard input ignores that value, and instead uses the value of *all inputs* with a matching locking script. ** coalescing transaction" A bitcoin transaction that _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
