The Co-founder of the Golem Project offered a Q&A session to a lucky user to answer some questions regarding the development, features and possible relations with DApps.

Recently, the acting CEO and CTO of Golem, shared a series of thoughts and explanations through a brief interview with one of the users of the network. In addition to talking about important points such as usability and the Golem token (GNT), Janiuk expressed the reasons behind the choice of the Intel SGX route, resulting in Graphene (the LibraryOS they have been building in a collaboration with Intel, ITL, Chia-Che Tsai and Don Porter).

Are Golem service providers limiting to Intel chips? What are PJ’s thoughts on SGX?

Janiuk assured that embracing this technology does not necessarily mean that service providers in the Golem network are limited to Intel CPUs.

JK said:

“The discovery protocol mentioned in answer to question no 2 allows adding new types of resources. This applies to all classes of Trusted Execution Environments (TEEs), including Intel Software Guard Extensions (Intel SGX).”


Janiuk also took advantage of the question to explain that Graphene was chosen because of its natural potential in terms of features and recognizability. In his statement, he specified that they will take the necessary measures to reach sophisticated solutions that allow the optimal development of the Golem network.

Enterprise partnerships situation

JK explained that currently the project efforts are focused solely and exclusively on optimizing the project and not on establishing business partnerships, at least until it is really necessary.

“We are an active participant in the Graphene Consortium , where Intel is one of the official contributors. For now, it seems that Golem is the leading force behind the direction and the development of the platform.”

Collaborations with DApp developers

The Golem team has been tirelessly seeking to boost network use cases, as well as interviews with users to analyze the usability of the platform. At the same time, JK explained that for now, the goal is to present Golem to developers as a successful option. In this way, the GNT community would grow and integrations would not be necessary.

“Once the Task API is released, we expect external integrations with Golem being born. This API will most probably also allow users to make the best use out of the Graphene features.”

JK’s thoughts on the velocity argument and token value

According to Janiuk, having a utility token is vital, in fact, GNT is designed to be an example of utility and not an arbitrary one.

“If the sole purpose of the token on a platform is to be the medium of exchange, then favoring this token over any other, with similar characteristics (eg, average transaction time, transaction fees denominated in USD, and so on) is not necessary from the platform usability perspective.”

Although many users believe that reinventing the project or adding another token, reason why it would be unnecessary to fork the project, as this would not be more beneficial for the network or platform from a usability point of view. In this case, Janiuk says it is better to improve the existing token.

Assuming that a fork occurs in all projects that implement their ERC-20 token as a medium of exchange. Each project would replace its original token with ETH, thus giving a better user experience since it would only have to use a token for future transactions.

What's your reaction?
Happy0
Lol0
Wow0
Wtf0
Sad0
Angry0
Rip0
Leave a Comment