Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consolidate Core Accessor Clients Under TxClient #4273

Open
vgonkivs opened this issue Jan 27, 2025 · 0 comments
Open

Consolidate Core Accessor Clients Under TxClient #4273

vgonkivs opened this issue Jan 27, 2025 · 0 comments
Labels
refactor optional label for items that are related to implementation work and do not change functionality WS: Maintenance 🔧 includes bugs, refactors, flakes, and tech debt etc

Comments

@vgonkivs
Copy link
Member

Currently, celestia-node maintains three clients in the core accessor. Since we already have a TxClient that proxies transaction-related requests, I propose moving these clients inside the TxClient to streamline the structure.
@evan-forbes evan-forbes added refactor optional label for items that are related to implementation work and do not change functionality WS: Maintenance 🔧 includes bugs, refactors, flakes, and tech debt etc and removed needs:triage external labels Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
refactor optional label for items that are related to implementation work and do not change functionality WS: Maintenance 🔧 includes bugs, refactors, flakes, and tech debt etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vgonkivs @evan-forbes