-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Implement node client discovery #165
Labels
P1
repo/akash-api
repo/node
Akash node repo issues
repo/provider
Akash provider-services repo issues
Comments
troian
added a commit
to akash-network/akash-api
that referenced
this issue
Dec 16, 2023
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Dec 16, 2023
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
10 tasks
troian
added
repo/node
Akash node repo issues
repo/provider
Akash provider-services repo issues
repo/akash-api
P1
and removed
awaiting-triage
labels
Dec 16, 2023
troian
added a commit
to akash-network/akash-api
that referenced
this issue
Jan 8, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/akash-api
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/akash-api
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/node
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/provider
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/provider
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
troian
added a commit
to akash-network/provider
that referenced
this issue
Jan 9, 2024
refs akash-network/support#165 Signed-off-by: Artur Troian <troian.ap@gmail.com>
github-project-automation
bot
moved this from In Progress (prioritized)
to Released (in Prod)
in Core Product and Engineering Roadmap
Jan 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P1
repo/akash-api
repo/node
Akash node repo issues
repo/provider
Akash provider-services repo issues
Is your feature request related to a problem? Please describe.
With updates/additions to proto API it becomes a little hard to track which version of proto should be used by the particular client on the mainnet.
This feature aims to solve it by introducing client discovery.
Describe the solution you'd like
n/a
Describe alternatives you've considered
n/a
Search
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: