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
{{ message }}
Repository navigation
Create ADR describing interacting with DALC implementations #142
We will expand the approach to keep the DALC behind a grpc server. One of the main reasons for this is that we can’t have two libp2p hosts in the same process, and ideally not even on the same machine. Also, optimint cannot import celestia-node, because celestia-node requires dependencies for celestia-core and celestia-app, while optimint must only import tendermint. In the future, this aspect might change as the requirements for what exactly can and can’t go in each repo are still in flux.
Short Term
completely removing any dependencies on celestia-app
progress with the grpc mocked DALC PR
Nothing changes for celestia-node
Medium Term
write a DALC grpc adapter for celestia-node once celestia-node has DAS functionality. The current plan is to keep this code in a separate repo. It might end up being a good idea to include it in celestia-app or celestia-node, but that is tbd
Long Term
edit Unless we figure out a way to safely use libp2p hosts and create a DAS client that doesn't import celestia-core in the same process/machine, we will continue to delegate all data availability processes to this DALC server/middleware
Activity
tzdybal commentedon Oct 21, 2021
Call summary (by @evan-forbes):
We will expand the approach to keep the DALC behind a grpc server. One of the main reasons for this is that we can’t have two libp2p hosts in the same process, and ideally not even on the same machine. Also, optimint cannot import celestia-node, because celestia-node requires dependencies for celestia-core and celestia-app, while optimint must only import tendermint. In the future, this aspect might change as the requirements for what exactly can and can’t go in each repo are still in flux.
Short Term
Medium Term
Long Term
liamsi commentedon Oct 22, 2021
Q: Wouldn't that just mean having a different identity key and using a different port? How would that not be safe?
evan-forbes commentedon Oct 22, 2021
cc @Wondertan
Good question, I think there was mention of some global vars that libp2p relies on.
edit: added the condition that DAS client would also have to not import celestia-node as to avoid importing celestia-core
Manav-Aggarwal commentedon Jun 27, 2024
Refer to https://rollkit.github.io/rollkit/specs/da.html