The Telos work proposal #25 was opened with the target of implementing portable snapshots for Chronicle, so that Chronicle data can be easily moved between servers of different OS versions.
As of August 22nd, I added a new feature to Chronicle that allows starting it from a nodeos portable snapshot. So, there's no need to re-scan the whole history in order to get up to date Chronicle data. Now it's enough to point it to a node that just started from a snapshot. This eliminates the need for portable snapshots in Chronicle, so the initial purpose of the WP is obsoleted.
The work proposal asks for 50000 TLOS, which is approximately USD 2500 in current prices.
I propose to re-purpose the WP#25 and set the following deliverables:
-
Implement a new event type for authorization updates. Currently if one needs to get permissions and authorization information from Chronicle, they need to scan
newaccount,updateauthandlinkauthactions on the system contract. Authorization updates are also available as table deltas within the state history, so this change will allow getting the full information about account permissions if a node starts from a portable snapshot, within an hour, instead of scanning the whole history which takes a significant time. -
Update LightAPI to use the authorization updates. This will allow spining up a new instance of LightAPI quickly without the need of re-scanning the whole history.
-
Add REX balances to LightAPI.
As of today, hosting of LightAPI for Telos costs nothing to the Telos community. It is used by Bloks.io and is free to use by other applications and wallets. Also Chronicle is used by some projects of Telos community members.
There are also deeper details on Chronicle and its place in the big picture of things in my recent article.
Yours truly
cc32d9