Smart Contract's bytecode is gossiped every time balance or storage is updated.

[morph-dev]

Currently, we will try to gossip Smart Contract's code even if it is not modified.
If contract's balance or storage was updated, entire AccountState (and leaf in the account trie) will be updated as well.

The following code would then gossip bytecode as well:

trin/portal-bridge/src/bridge/state.rs

Lines 180 to 191 in 3fc0ed8

	if account.code_hash != keccak256([]) {
	// gossip contract bytecode
	let code = state.database.code_by_hash_ref(account.code_hash)?;
	self.gossip_contract_bytecode(
	address_hash,
	&account_proof,
	block_tuple.header.header.hash(),
	account.code_hash,
	code,
	)
	.await?;
	}

I'm not sure if there is easy way for this to be fixed.

[KolbyML]

I don't think this is a milestone for devcon 2024

[KolbyML]

Just in case someone wanted to work on this, #1337 this PR should be merged first as it would invalidate the work from this PR.

I think in the grand scheme of things there is a lot that should be done before this issue though

[morph-dev]

I don't think this is a milestone for devcon 2024

While I think it's not critical for the devcon and there are other important issue, I think we should have this if we want to gossip head blocks (because there will be a lot of contracts that are touched at every block).

100% there is just a lot to do before we reach that, lot being relative