4 - if a user logs into moneybutton, handcash, or twetch wallet the existing api calls for the respective wallet should be enough to interact with sCrypt smart contracts. I suggest laying out all the requirements for each type of sCrypt contract then sharing the requirements with all teams developing wallets. The teams developing wallets can inform sCrypt what types of contracts are currently possible with their wallet. If a developer has a specific sCrypt contract they want to implement they can easily see what wallet that is currently possible with.
4 - if a user logs into moneybutton, handcash, or twetch wallet the existing api calls for the respective wallet should be enough to interact with sCrypt smart contracts. I suggest laying out all the requirements for each type of sCrypt contract then sharing the requirements with all teams developing wallets. The teams developing wallets can inform sCrypt what types of contracts are currently possible with their wallet. If a developer has a specific sCrypt contract they want to implement they can easily see what wallet that is currently possible with.