Thanks for the answer Ishmael. However, that is not exactly the answer that I was looking for. I guess that my question was not deep enough and not properly asked. I'll rephrase:
In a common ScriptPubKey to pay a single recipient, we use the bitcoin address (hash of the public key):
scriptPubKey: OP_HASH160 <scriptHash> OP_EQUAL
However, in a multisig (what I guess that createMultiSigOutputScript creates), the Script requires the public keys:
script: OP_m <pubKey1> ... OP_n OP_CHECKMULTISIG
Since I guess that there is no way to do a multisig with bitcoin addresses instead of public keys, then my question is: why was this created like that?,
instead of being more consistent and using addresses like in the scriptPubKey?
Kind regards,
V