A very reasonable future path for this software

[faddat]

Note: I haven't reviewed the latest information from the charter. I'm writing assuming that the idea is for Juno to proceed as a general purpose smart contract platform.

Juno

Juno should work to make itself a predictable and stable smart contract platform. Each of the new modules introduced by Juno needs to be examined regarding:

• level of technical debt
• economic safety
• technical safety
• suitability

If they're all found to be needed, then Juno needs to begin to actually discuss these modules and the unique advantages that they provide. Currently, there's no public story surrounding these modules, and if that is the case, why do they exist? The more custom code Juno has the more work it takes ot maintain the chain.

This issue follows the thesis that contract authors are attracted to stable deploy targets, allowing them to focus entirely on the contract code that they're deploying.

The fee share module should be removed because it encourages overpricing for contracts and can be used to make attacks cheaper. Unless it is being actively used to benefit the chain, this risk outweighs its benefit.

Clock - contracts can execute blockly

Does anyone use it? This is a very attractive feature, so if no one does, we should try to learn why.

Drip - allow airdrops to juno stakers

Drip is awesome! That said I haven't heard of projects using it, so this is another case where if it isn't being used, why not?

Fee Pay - pay contract fees on behalf of users

Again, a very interesting feature allowing users to fund contract costs on behalf of others. The wallet limit is a sensible way of rate limiting.

Technical narrative

The code in this repository dramatically exceeds the narrative about Juno to the wider world. Im quite sure that there are few developers who are aware of the extensive expanded feature set available to developers on Juno.