Files
dasman a500b3d9f1 event_graph: expanding the graph to have multiple DAGs
basically the one dag we had before is now at least one (arbitrarily 5 max) are addressed by their genesis event hash, managed in DAGStore and are sorted chronologically.
creating a new EventGraph instance means creating the configured number of dags deterministically
and open those trees in DB, created if not existing.
prune now drops the oldest tree and adds a new one to the considered trees.
each dag is paired with its unreferenced tips and are updated accordingly.
fetching an event searches through all dags and fetch the wanted one.
in protocol, requesting tips are done by sending the dag_name of which the unreferenced tips are requested (probably breaks comp, still WIP)
2024-12-24 03:32:48 +03:00
..
2024-06-12 02:27:06 +03:00
2024-06-12 02:27:06 +03:00
2022-04-02 13:26:02 +02:00
2023-05-31 14:36:36 +00:00
2023-05-31 14:36:36 +00:00