As mentioned in 0xMiden/node#1140 (comment), we should have a limit in place for account updates per block.
Notably, we already have ACCOUNT_UPDATE_MAX_SIZE which is $2^{18}$ currently (and will likely change again with #1465), but it is only enforced on a transaction level. So with that limit set to 64 KiB, we essentially have a block limit of ACCOUNT_UPDATE_MAX_SIZE * MAX_ACCOUNTS_PER_BLOCK = 4 GiB, which is way too much.
The limit for this issue can either be per block globally or per account in a block. The former would allow a block to include a single large account update and many smaller ones, while the latter wouldn't but might be fairer overall.
Given that we already have ACCOUNT_UPDATE_MAX_SIZE, maybe a per block maximum might be the most flexible option.
As mentioned in 0xMiden/node#1140 (comment), we should have a limit in place for account updates per block.
Notably, we already have$2^{18}$ currently (and will likely change again with #1465), but it is only enforced on a transaction level. So with that limit set to 64 KiB, we essentially have a block limit of
ACCOUNT_UPDATE_MAX_SIZEwhich isACCOUNT_UPDATE_MAX_SIZE * MAX_ACCOUNTS_PER_BLOCK= 4 GiB, which is way too much.The limit for this issue can either be per block globally or per account in a block. The former would allow a block to include a single large account update and many smaller ones, while the latter wouldn't but might be fairer overall.
Given that we already have
ACCOUNT_UPDATE_MAX_SIZE, maybe a per block maximum might be the most flexible option.