Currently block_timestamp is calculated by splitting the 256 bit value into 4x64 bit values and treating them as goldilocks field elements. This creates aliasing (the same encoded value can map to different 256 bit values, because the goldilocks field is less than 64 bits).
We could instead hash the 256 bit value somehow into a 4 goldilocks field elements, so that only one preimage exists (considering the hash strenght). At any point the original 256 bit value could be provided as witness to recover the original value.
Currently block_timestamp is calculated by splitting the 256 bit value into 4x64 bit values and treating them as goldilocks field elements. This creates aliasing (the same encoded value can map to different 256 bit values, because the goldilocks field is less than 64 bits).
We could instead hash the 256 bit value somehow into a 4 goldilocks field elements, so that only one preimage exists (considering the hash strenght). At any point the original 256 bit value could be provided as witness to recover the original value.