Payment to script address
Opened this issue · 2 comments
Currently, the script does not at all support script address.
Following a recent change, it has become possible to support such addresses.
Now we are faced with the discussion of whether we should support them.
Often times when airdropping to users, we base our amounts from snapshots of the chain. This will regularly include trading script addresses.
In this case, we do NOT want to drop to those addresses, as the tokens will simply be locked up forever.
However, there may be edge cases where we do want to support script addresses, for example, someone may have a proxy validator, or multisign validator of some sort.
To remedy this, I propose we add a flag for --allow-validator. By default, any script addresses will be rejected. With this flag enabled however, we'll allow script addresses to be recipients of tokens.
Open to discussion about this.
This sounds like a good idea, the only question I have is how this interacts with --use-pub-key-hashes, when we see a hash in the beneficiary file, how do we know if it is a script or pubkey hash?
By the name, we should assume its always a pub key hash. Lets avoid script support with that flag