Those are always from one sided view coming from Elastic.
but there are many issues that are going to be addressed in future releases, there is a public roadmap for Golem...
Well, the list was prepared by Elastic but it can be used as a starting point for further research.
On another note, I really wonder how Golem team is going to address verification of the output for rendering jobs. Reputation system isn't something that can be fully trusted. The main problem is that in order to verify the final image (or frame), it needs to be fully rendered by requester, or some other worker. Any partial results will simply not work in this case, and additional full renders will be huge overhead for the system.
[EDIT: Golem actually says "Such reputation systems are vulnerable to numerous attacks. There is the famous sybil attack, where the attacker creates a large number of identities and fakes those scores via a large influence on the network. There is also the re-entry attack, where the attacker starts fresh with a “neutral” reputation by abandoning the old identity.
So far, we are aware of no system resilient to all attacks. Reputation systems in decentralized applications remain an open problem. Golem’s reputation system too is still a subject of research, and we plan to cooperate with the best teams in the field to come up with the best solutions."
https://blog.golemproject.net/the-challenges-ahead-933f040cba95]
