update_state_cold_storage now uses ec_points_format from BulkData for tx parsing.
parse_txs still uses the default ec points format.
The open question is whether we need to keep backward compatibility or not. I think it probably isn't worth it because even if clients failed to sync state with the cold storage they still can continue with the usual sync. And the only period when it would be useful is the period when we've already updated the ui but haven't updated the cold storage.
In this PR the following was done:
BulkDatawas extended withec_points_formatupdate_state_cold_storagenow usesec_points_formatfromBulkDatafor tx parsing.parse_txsstill uses the default ec points format.The open question is whether we need to keep backward compatibility or not. I think it probably isn't worth it because even if clients failed to sync state with the cold storage they still can continue with the usual sync. And the only period when it would be useful is the period when we've already updated the ui but haven't updated the cold storage.
The reason why it could be useful is described at https://github.com/zkBob/zkbob-pool-storage/issues/2.