This article was first published on null
What’s in store for this Digest?
This week we’ll be going over our latest GitHub activity focusing on Pull Requests in Yagna and its related repositories. We’ve mentioned before that we’ve been working on Yagna for over a year! And to show this in an entertaining way, I created a video displaying the contributions to all our public Yagna repositories visualized from their inception!
In the previous Golem GitHub Digest (#2) we went deeper into the milestones and specific repositories related to The Next Milestone (internally dubbed as YAGNA). This week, we’ll be covering significant Issues and Pull Requests.
So, what’s new in the Golem GitHub?
Today we’re going into a number of Pull Requests which are additions (and removal) of code into the master branches of our repositories.
In the current version of Golem some of you might know that there are ways to limit the resources for a node running as a provider on the network. Similarly, this will exist with New Golem. The developers worked on a pull request (#428) to add in such functionality to the provider agent where the node runner can limit hardware resources, introducing 3 new command-line arguments for limiting max CPU cores, RAM, storage plus corresponding environment variables.
The GNT Driver is a significant part of what will handle payments from requestor to the provider in New Golem. Work on the GNT Driver API (#415) was merged, distinguishing between mainnet and testnet (Rinkeby).
For the new marketplace to work, it requires rules by which the requestor and provider nodes follow. In Pull Requests #410, #417 and #418 our marketplace sub-team has added functionality to the decentralized marketplace of creating an agreement, confirming such agreements, and countering proposals on both the requestor and provider side. Together these ...
To keep reading, please go to the original article at: