History Services, Evaluation and Points

[cmadh]

Copied from TG-Chat (cmadh):

still confused by what exactly "partial" means and how IGs define "hyperion-full"

there's nodeos with:

• blocks.log
• state_history.log
• traces.log (SHIP --trace-history)

and then there's hyperion:
I see many things missing in this draft as there are quite a few configurations that
a.) can have high impact on the expenses a Guild has
b.) be highly valuable for users and developers

I'm speaking about things like:

"features": {
...
"streaming": {
...
"traces": ?, // from what I know only works when traces_log is enabled in nodeos.
"deltas": ? // feature that can be crucial for applications while it could reduce get_table_rows-calls if reliable and commonly available
...
},
}

"indexer": {
...
"fetch_traces": ?, // again, from my understanding only works if traces.log is enabled
...
"max_inline": 20 // if set to something low reduces the overall processing-time and reduces storage, has an impact on expenses, can cause "false transparency"
...
},

Also, the features mentioned in this image are not covering many of the topics we had in discussions in the past like

• "hyperion points ONLY if you have "full history" (still unclear if that means state_history or state_history + traces) -> because without state-history no full hyperion possible" (not having "full history" while having a fully indexed hyperion has in the past led to less points while every time I asked for clarification the answer hasn't been answered.)

[cmadh]

In addition, there are questions regarding offering public trace-endpoints ( v1/trace_api/get_block ).