chainweaver does not prevent error on cross-chain k: account creation resulting in single account protocol violation

[trendzetter]

Scenario:

1. select transfer coins
2. fill out a cross chain transfer to an non-existing k: account. choose keys-any

actual result:

the transfer fails on continuation and cannot continue. the account cannot be created as k: account standard because it requires keys-all for account creation and the receiver guard has keys-any. error single account protocol.

expected result:

the rules of the k account creation are checked if the account does not exist. The transfer cannot be confirmed if the entered data does not conform the rules of k account creation

[jmininger]

Note. This requires that the default has been overridden. You should not have to specify a keyset when sending to k-accounts. The correct one will be chosen for you.

[trendzetter]

I know but some people seem to play with these options when they don't know what they are doing. I think when we are talking about manually writing contract calls users should know what they are doing and do their own checks.
But for the wizard the options are limited and the result preferable never be invalid. users could be warned if they choose an option in the wizard that will not work at all.