Author

Topic: Multisig for multiple receiver addresses and different coins/tokens (Read 102 times)

legendary
Activity: 3444
Merit: 10558
Q1.
this question isn't clear. you mean something like this transaction:
https://www.blockchain.com/btc/tx/cce09841f35cf8f3a0f1f194746837a2d4dec15e7db469ba52d82c3d9deb4632
there are different "senders" each having a different address (a different key) which they all are creating a single transaction.
if this is what you had in mind then it has nothing to do with multisig. it is a feature that existed for a long time, where you can spend multiple transaction outputs in one transaction and sign each of them with their respective private keys since they already are going to have a separate signature field inside the final tx.

Q2.
as far as i know, it is possible. because the way that bitcoin is using multisig is very primitive and easy to implement. basically you concatenate multiple public keys and then sign the tx multiple times and then concatenate those signatures together too. so as long as each of those altcoins support some sort of scripting language where you can tell the interpreter to "check_multisig" then they should be able to do it no matter what signature schemes they are using.
however, when we move to Schnorr and start using collective signatures when you just have 1 sig and 1 pubkey they won't be able to do it unless they are using Schnorr or any other DSA algo that allows safe signature aggregation.
jr. member
Activity: 35
Merit: 16
Just would like to ask two questions.

Question 1
Is it possible to implement multisig to send different bitcoin amounts on multiple bitcoin receiver addresses at once in a single transaction?

E.g. 5 people create a transaction (actually 5 transactions in 1) to send different bitcoin amounts from a hardware wallet address to 5 different addresses (each person has its own address) within a single multisig.

Question 2
Is it possible to implement multisig for every currency (e.g. neo, ripple, monero, ....) or it works just for bitcoin?
Jump to: