Specification of Datum - Githubissues

neume-network / strategies

Indexing strategies for the neume network.

GNU General Public License v3.0

11 stars 7 forks source link

Closed TimDaub closed 1 year ago

TimDaub commented 2 years ago

Fixes #301
[ ] implement ids for all strategies
[ ] answer question: Can we go from a user defined identity to a fastly indexed flat file?
[ ] answer question: How could we reference one data point in the json fields of anther one to e.g. get rid of music-os-accumulator and instead resolve e.g. zora-get-tokenmetadatauri by following a universal Datum.id?

TimDaub commented 1 year ago

Been thinking a bit more about this and I'm starting to imagine that we should have two types of indexes:

a URI that can address an external resource as e.g. an eth_call, which I've described here and maps to all worker messages: https://github.com/neume-network/schema/issues/53
A hash and pointer to a data dir file that defines an offset within the file itself for fast access and joins.