ScriptPubKeythat represents an m-of-n multisig. This means that in order to spend the coins, m number of private keys will be needed to sign the spending transaction out of the n number of different public keys provided.
scriptPubkeyhas the following form:
<sigsRequired> <pubkeys…> <pubKeysCount> OP_CHECKMULTISIG
Transaction.Sign, which does not work for multisig.
TransactionBuilderfor signing the transaction.
scriptPubKeyreceived a coin in a transaction called
Cointhey received from the transaction:
TransactionBuilder, they create an unsigned transaction.
Sidenote: there is an inherent difficulty which arises from this situation. You need to send the newly created, unsigned multi-sig transaction to every signer and after their signed it, you also need to collect the partially signed transactions from them and combine them into one, so that you can publish that on the network. This problem is partially solved by the BIP-0174, because it at least standardizes the data format, but you still need to implement your own way to distribute the data between the signing parties. NBitcoin doesn't have an implementation for BIP-0174 or for the off-chain data distribution yet.
scriptPubKeyas easily and concisely as a regular Bitcoin Address?