i was also with dynamic block but i've heard there are some problems, first of all is if an attacker is abusing the network by flooding it and increase the dynamic block momentarily, this will lead to some sort of centralization toward strong node
the other thing is to follow the monero project with its dynamic block, but it will change a bit the fundamental economy of bitcoin, making it inflate for a small amount like monero did
there are many ways to have a dynamic protocol
put short nodes FIRST have to accept a certain size for the network to happily accept without much/any orphan drama
next pools need to be rest assured that if pools made blocks bigger then current consensus it wont cause much/any orphan drama.
it is not as simple /silly as pools make bigger blocks if the mempool is overfilled due to an abuser flooding it..
firstly node need to flag their acceptance they can cope with Xmb.. then pools flag their intent to make anything upto xmb to give a prompt for the laggers to adjust to xmb or be left unsynced when pools deem it safe to move forward.
then when it meets a certain safe majority level pools dip their toe in the water.
EG imagine majority nodes flagged 2mb was ok.. pools then flagged a majority ok to make 2mb base blocks..
at a certain point pools 'test the water' by making a 1.001mb block to see the orphan risk, then the next block maybe 1.002mb and so on safely incrementing up, naturally with demand until whenever blocks get to be 2mb full due to demand.
its not going to be a 2 mb or a 1gigabyt by mindnight thing. nodes and pools will do it safely.
after all.. did pools and nodes jump from 0mb to 1mb overnight in 2009-2015.. nope.
after all.. did pools and nodes jump from 0.5mb to 1mb overnight in 2013-2015(after the sipa caused db fork event).. nope
it was natural and safe and orphan mitigating low risk movements.