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
For the Golem Stats Page we are expected to deliver a breakdown of yagna versions used by providers on the network. We need to establish the version of yagna that the specific provider operates. Right now to establish this we need to extract the information from the metrics pushed by providers to yastats. That's really inconvenient.
What we would need?
It would be awesome if the yagna version would be advertised in the offer itself, so that when we utilize the passive market scan, we can obtain this information via this path.
Acceptance Criteria
When running a passive market scan we can see the yagna version property (however you will name it) that will present the values like v0.16.0 for "stable", and pre-rel-v0.16.1-rc4 for pre-releases.
The text was updated successfully, but these errors were encountered:
I would prefer to avoid users matching on that while creating applications, as they should refer to capabilities / payment protocol version / maybe runtime version. I think putting this under debug (like subnet) would be appropriate.
Why?
For the Golem Stats Page we are expected to deliver a breakdown of yagna versions used by providers on the network. We need to establish the version of yagna that the specific provider operates. Right now to establish this we need to extract the information from the metrics pushed by providers to yastats. That's really inconvenient.
What we would need?
It would be awesome if the yagna version would be advertised in the offer itself, so that when we utilize the passive market scan, we can obtain this information via this path.
Acceptance Criteria
v0.16.0
for "stable", andpre-rel-v0.16.1-rc4
for pre-releases.The text was updated successfully, but these errors were encountered: