You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JSON API against running lotus fullnode is good for staying up with a current node.
when doing historic processing, it will likely be faster and probably path of least resistance to have a snapshot of a lotus repo, but not take the overhead associated with a lotus process and going through a json API.
It would be nice to be able to directly run the badger and library code for accessing an on-disk repo to directly provide the lens API rather than indirecting it through a lotus API.
The text was updated successfully, but these errors were encountered:
The JSON API against running lotus fullnode is good for staying up with a current node.
when doing historic processing, it will likely be faster and probably path of least resistance to have a snapshot of a lotus repo, but not take the overhead associated with a lotus process and going through a json API.
It would be nice to be able to directly run the badger and library code for accessing an on-disk repo to directly provide the lens API rather than indirecting it through a lotus API.
The text was updated successfully, but these errors were encountered: