# Unusual Version Number in Blocks

I've noticed recently that some blocks contain version numbers that are not the traditional 0x10000000 or 0x20000000.

For example, this block, has a version number of 0x3FFFE000 instead of 0x20000000 like the previous block has.

From my understanding this will not affect the actual hash digest, since it will produce a valid hash regardless of what the version field is.

A quick search on the forum did not return any results, but I am going to take a slight guess that this has something to do with miner voting to show what the consensus is for a future change? If this is the case, does it really make sense due to mining pools being a majority of hash power anyways? (Instead of miners votes individually)

If my prediction is correct, is there some list that defines which proposal coordinates to a given version number?

Thanks