Golem GitHub Digest #10: Improvements from community feedback

This article was first published on null

What’s in store for this Digest?

Golem GitHub Digest #10: Improvements from community feedback

Since the previous GitHub Digest (#9) the whole Golem team has been in Energizer Bunny Mode on every front. The GNT -> GLM migration was initiated and we made our migration audit public, along with making the contracts repo (gnt2) open. This is particularly important for Yagna and New Golem since it requires the new GLM token for a feature just now available in the form of the Alpha 3, among other features.

Shortly after, the Golem Online Hackathon was launched and we offered the knowledge base, our version of a  one-stop-shop for hackers in our GitHub Hackathons repository. If you’re looking for a team to build on Golem with then that’s the place to go! You can also find details of other participants, projects, bounties, etc. in the Gitcoin page.

To go alongside the Hackathon (focused on requestors), we also initiated provider bounties offering GLM to those who provide on Golem. You can track that and more in the GitHub issue.

Before we dive into the GitHub we also need to highlight the Golem Test Harness (Goth), Hackathon 101 and Q&A session. You can find more about that in this blog.

So, what’s in the Golem GitHub?

The amazing feedback during the Alpha 3 release, hackathon and bounties has provided us with valuable feedback and letting us come across strange behaviours such as requestors with errors such as: Failed to create allocation error, Invoices get stuck in "RECEIVED" status, Allocations are not always released.

Other issues we came in contact with were long computations frequently failing on providers. The fixes to improve on this have already been created in the YaJSapi repo. While there is no patch release yet, developers can still utilize the branch that fixes it ...

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

Comments (No)

Leave a Reply