Golem GitHub Digest #9: AMD provider support, network metrics and improved proposal handling

This article was first published on null

What’s in store for this Digest?

Golem GitHub Digest #9: AMD provider support, network metrics and improved proposal handling

Since our previous GitHub Digest (#8) the Golem team has been heads down working towards the next Alpha release and gathering feedback from the Alpha II release and Provider Sneak Peek. Something that’s been particularly helpful has been the community’s involvement in providing us with logs for any issues they’ve encountered so that we can address them in the upcoming release.

So, what’s in the Golem GitHub?

To start off with we want to highlight the new Ya-runtime-vm pre-release (v0.2.2). What’s exciting about this release is that it includes support for providers using AMD processors! Up until this release, only Intel CPUs were supported as providers on the network. You can try run it yourself with:

curl -sSf https://join.golem.network/as-provider | YA_INSTALLER_VM=0.2.2 bash -

As for Yagna, there’s also been pre-release (v0.4.1) which includes the implementation of pushing of metrics from yagna daemon to a statistics page. This will help us provide a statistics page to share with the community containing lots of information about the network such as 24hour earnings, network CPU usage, accepted+paid invoices, signed agreements and negotiations, active offers, etc. If you’re interested in the code and to see where this information will be sent you can check out this Pull Request

Although not yet part of the binary releases, the ZkSync payment driver is more or less ready pending final review and checks. A huge amount of work from our whole team went into making this possible, from the research of the R&D team and then into the development and integration (a large amount of which is contained in this PR) so we’re very proud to soon have this functionality available to Golem users.

An important ...

To keep reading, please go to the original article at:

Comments (No)

Leave a Reply