Im looking for a developer community feedback for Ethereum Distribution System project: a generalized, semver enabled fully-on chain distribution system (generalized factory)
Please reach back in thread or leave comments in discussion tab on github! 
TLDR, hypotesis I want to validate:
Hypotesis 1
The current landscape of smart contract distribution on the Ethereum network is fragmented and inefficient.
Mostly, projects generate numerous deployment artifacts that cannot be optimized in database(?) because of built metadata affects code hashes.
This practice results in a increase in blockchain size for node operators, far beyond what is necessary.
This likely is much below what storage / tx takes, however, contrary to tx data, bytecode is not something nodes can prune, meaning in the long run it may become more actual?
I am not familiar with how execution clients store contract bytecode, but I doubt they split metadata objects in separate table, and even if, the smart contract devs are not incentivised to re-use heavily and likely anyway produce overhead number of artefacts
Hypotesis 2
Newer ecosystems such as Sui claim competitive advantage over Ethereum, for example, for being able to pass objects between contracts.
From my understanding, the EVM is eventually right concept because it allows to build similar abstraction model on top, as it is just a computer architecture.
With stateless Distributions proposed in EDS, it is possible to write software that will enable functionality similar as Sui proposes on inside evm. ( e.g,: Two applications distributed trough same distribution / distributor do not need for user explicit approvals as they are by design distributed together. )
Hypotesis 3
Distributions that are stateless chunks of code, in principle could be used to provision execution layer migration scripts for the whole protocol.
EIP 7702 discussion is exemplary for this, it’s a breaking change for many security assertions.
It could be presented as “Ethereum 3.0”, a network within a network, where upon fork day, Beacon chain promises to migrate all of infrastructure that community added and then do user states (assets) migration ad-hoc whenever users reach out to designated migration contract.
Open questions
How dumb am I 
any of these hypothesises can hold their truth?
Can bytecode size on Ethereum become a problem in foreseeable future?
I’ve encapsulated proposal to enshrine use of bytecode hashes in ERC7744 however If this proves to be very helpful, perhaps it’s worth to move in EIPs?
If EDS proves to have positive perception, this implies that there will be extensive use of proxies instead of new deployments, perhaps an EIP needed to bake native proxy support for this (even if not, proxies are very popular) ?