Ponder

Fun `trace_` API problem:

Write a function that accepts a single trace object and returns a uint256 representing its execution index within the transaction.

The index doesn't need to be absolutely accurate, but when used as a sort key, it must accurately order _any_ subset of traces within one transaction.

This remains unsolved. I think it's impossible - if anyone wants to learn more about traces and double check my work, would gladly chat

Created a gist with examples + more context

https://gist.github.com/0xOlias/596f21266023bc79adcff3f4d2c113b7

TL;DR - our requirements are weird, but if we solve this it will save Ponder users lots of time and money (on their RPC bill 🙃)

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

Just to confirm: you know that postgres can sort (correctly) on array fields such as traceAddress?

If I'm not mistaken, that's what we did (when we were on postgres)

Oh wow, I did not expect it to work out of the box on the traceAddress format.

We'll have to find a way to make this work in SQLite, which (afaict) does not support array column types. New thread to pull on though - thanks!

Double check that storing as a TEXT and sorting it won't work for you. I think it might produce the same ordering

I think that will break if any elements exceed 9, eg these will not order properly:
[0,1,9]
[0,1,11]

Thanks again, have more to play with now!