The best I can figure out is that you heard of this fancy new thing (Merkle airdrop) that would shift the cost of distributing tokens onto the recipients and you decided to do it despite having no clue how to implement it safely.
Merkle airdrop is not only about cutting the costs of an airdrop. Please read the information we have provided.
Currently we have implemented an option to create new wallet right within the system, as well as an options to sign transactions with Metamask plugin, so your claims that "we have no clue how to implement it safely" have no more ground.
I have read a lot of that information and it's quite interesting, thank you.
However I couldn't find any justification for requiring private keys in any of those articles. Even your solution of having a wallet "within the system" does not sound that much safer. I'm guessing you're doing this because you think your customers wouldn't be able to figure out how to sign the transactions using their own wallets. That still seems to fall under "no clue how to implement it safely".
Anyway, not to derail this thread any further - I'd still recommend for LoyceV to not rush with any revisions just yet.