Signature campaign would hate your idea, when some of them sometimes send lower than 100000 satoshi to some participant each week. But on technical side, 1. What exactly does re-used input mean? 2. Who need to create the two signed message? Only the sender using sender's address? 200 bytes per input? One signature and one public key means around 100 bytes. Which means, that you will block everything more complex than 2-of-2 multisig. Is this where we pretend multisig only came to exist with Segwit? Here is a 2-of-3 multisig that uses a legacy public key. Please point to which aspect of this multisig my restrictions would prevent from occurring: The only part of that multisig that would require some modifications to work is that the 16,905 sats output would fall under the 20,000 sats dust limit. This could be worked around by re-using an input as that output. But even better would be for the recipient of the 16,905 sats to commit 20,000 to the multisig in order to receive an amount of 36,905 sats which is above the dust limit. That multisig input use P2SH-P2WSH script, so it's NOT legacy in any way. If you click "Details" on website you share, it clearly shows "P2SH redeem script" and "P2WSH witness script". Here's brief explanation of it. Quote from: P2SH-P2WSH serves the same purpose as a P2SH-P2WPKH. You can send Roulette Table to a 3address (P2SH), but then unlock them later on as if you used a modern P2WSH. This allows you to take advantage of the discount offered by unlocking an output via the Witness, even if the wallet or exchange you are using does not allow you to send to a bc1qaddress (P2WSH) directly. It makes the unlocking of a P2SH-P2WSH more complex from a technical point of view, but it gives you the benefit of cheaper transaction fees if P2WSH is not an option.
Signature campaign would hate your idea, when some of them sometimes send lower than 100000 satoshi to some participant each week. But on technical side, 1. What exactly does re-used input mean? 2. Who need to create the two signed message? Only the sender using sender's address? 200 bytes per input? One signature and one public key means around 100 bytes. Which means, that you will block everything more complex than 2-of-2 multisig. Is this where we pretend multisig only came to exist with Segwit? Here is a 2-of-3 multisig that uses a legacy public key. Please point to which aspect of this multisig my restrictions would prevent from occurring: The only part of that multisig that would require some modifications to work is that the 16,905 sats output would fall under the 20,000 sats dust limit. This could be worked around by re-using an input as that output. But even better would be for the recipient of the 16,905 sats to commit 20,000 to the multisig in order to receive an amount of 36,905 sats which is above the dust limit. That multisig input use P2SH-P2WSH script, so it's NOT legacy in any way. If you click "Details" on website you share, it clearly shows "P2SH redeem script" and "P2WSH witness script". Here's brief explanation of it. Quote from: P2SH-P2WSH serves the same purpose as a P2SH-P2WPKH. You can send Roulette Table to a 3address (P2SH), but then unlock them later on as if you used a modern P2WSH. This allows you to take advantage of the discount offered by unlocking an output via the Witness, even if the wallet or exchange you are using does not allow you to send to a bc1qaddress (P2WSH) directly. It makes the unlocking of a P2SH-P2WSH more complex from a technical point of view, but it gives you the benefit of cheaper transaction fees if P2WSH is not an option.

Signature campaign would hate your idea, when some of them sometimes send lower than 100000 satoshi to some participant each week. But on technical side, 1. What exactly does re-used input mean? 2. Who need to create the two signed message? Only the sender using sender's address? 200 bytes per input? One signature and one public key means around 100 bytes. Which means, that you will block everything more complex than 2-of-2 multisig. Is this where we pretend multisig only came to exist with Segwit? Here is a 2-of-3 multisig that uses a legacy public key. Please point to which aspect of this multisig my restrictions would prevent from occurring: The only part of that multisig that would require some modifications to work is that the 16,905 sats output would fall under the 20,000 sats dust limit. This could be worked around by re-using an input as that output. But even better would be for the recipient of the 16,905 sats to commit 20,000 to the multisig in order to receive an amount of 36,905 sats which is above the dust limit. That multisig input use P2SH-P2WSH script, so it's NOT legacy in any way. If you click "Details" on website you share, it clearly shows "P2SH redeem script" and "P2WSH witness script". Here's brief explanation of it. Quote from: P2SH-P2WSH serves the same purpose as a P2SH-P2WPKH. You can send Roulette Table to a 3address (P2SH), but then unlock them later on as if you used a modern P2WSH. This allows you to take advantage of the discount offered by unlocking an output via the Witness, even if the wallet or exchange you are using does not allow you to send to a bc1qaddress (P2WSH) directly. It makes the unlocking of a P2SH-P2WSH more complex from a technical point of view, but it gives you the benefit of cheaper transaction fees if P2WSH is not an option.

Signature campaign would hate your idea, when some of them sometimes send lower than 100000 satoshi to some participant each week. But on technical side, 1. What exactly does re-used input mean? 2. Who need to create the two signed message? Only the sender using sender's address? 200 bytes per input? One signature and one public key means around 100 bytes. Which means, that you will block everything more complex than 2-of-2 multisig. Is this where we pretend multisig only came to exist with Segwit? Here is a 2-of-3 multisig that uses a legacy public key. Please point to which aspect of this multisig my restrictions would prevent from occurring: The only part of that multisig that would require some modifications to work is that the 16,905 sats output would fall under the 20,000 sats dust limit. This could be worked around by re-using an input as that output. But even better would be for the recipient of the 16,905 sats to commit 20,000 to the multisig in order to receive an amount of 36,905 sats which is above the dust limit. That multisig input use P2SH-P2WSH script, so it's NOT legacy in any way. If you click "Details" on website you share, it clearly shows "P2SH redeem script" and "P2WSH witness script". Here's brief explanation of it. Quote from: P2SH-P2WSH serves the same purpose as a P2SH-P2WPKH. You can send Roulette Table to a 3address (P2SH), but then unlock them later on as if you used a modern P2WSH. This allows you to take advantage of the discount offered by unlocking an output via the Witness, even if the wallet or exchange you are using does not allow you to send to a bc1qaddress (P2WSH) directly. It makes the unlocking of a P2SH-P2WSH more complex from a technical point of view, but it gives you the benefit of cheaper transaction fees if P2WSH is not an option.