Optimize chainassets db

[g1nt0ki]

I think one column per chain is suboptimal, what if we we instead have timestamp, chain & value as three columns, or just timestamp & value (single json with all the data)

Other thing is, can split into daily and hourly tables? we dont need hourly data from the start of time right? I am thinking of adding a script that will backup/archive old hourly data and then retain only past 2-3 months, need to do something similar for tvl, bridge and other databases. wdyt?