We used to save the configuration protocol for each epoch in the database, but this is incorrect because every time we changed the configuration we got deserialization errors and had to re-index all configurations in a new way. I found a place in the nearcore library where the configuration protocol is processed and applied this logic on the side of the read-RPC service.
We used to save the configuration protocol for each epoch in the database, but this is incorrect because every time we changed the configuration we got deserialization errors and had to re-index all configurations in a new way. I found a place in the
nearcorelibrary where the configuration protocol is processed and applied this logic on the side of the read-RPC service.