celestiaorg
feat: accommodate custom functionality
Access to certain celestia-node services, such as header.Store, is needed by custom data availability light clients. Ideally, developers of custom data availability light clients shouldn't have to fork this repo when they need to add additional services to a celestia-node.
One way to do this is to make the cli more portable, along with implementing some sort of Plugin interface so that custom celestia-nodes can easily be created.
should we close this?
We have groomed and decided to leave it open to post-mainnet phase
going to close this to keep our issues backlog smaller and actionable. We can create/groom as a discussion/roadmap plan as demand arrives now folks are integrating. Also, some customization work was done along these lines (but not designed as a totally 'plugin' system) in https://github.com/celestiaorg/celestia-node/pull/2950 that satisfied an example demand for this
