KYC (Know Your Customer) - survey for the provider

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Background information - What is Golem Network?

As you probably know, Golem Network is a peer-to-peer marketplace for computational resources. Individuals can share there idle hardware (Providers) or request computing resources in the network to perform tasks (Requestors).

The purpose of this survey - security & identity concerns from the Provider point of view:

As a Provider in the Golem Network, you will run a Requestor’s code and will have the option to open outgoing and incoming network traffic. This creates some potential risks, which can be mitigated with some level of Requestor identification. Other risks include the Requestor not paying for jobs you performed. Identification could help prevent this.

Let us know your thoughts on how to approach this responding to the 5 questions below:

What kind of information would make you prefer one Requestor over another to decrease the risks when running a Requestor’s code?

Additional information about the Requestor would not impact my decision

Social network based identification (examples: Facebook/Linkedin/Github)

Existence of blockchain domain connected with the Requestor’s node address (examples: ENS domain, Unstoppable Domains)

Existence of DNS domain connected with your node address (example: via TXT record)

Self-sovereign identity (examples: Polygon ID)

Public identity claims (examples: ERC-725 / ERC-735)

Web3 based Social Identification (example: Proof of Humanity)

Full identity document based KYC (example: Onfido or IDnow)

Credit card based proof (examples: Visa, Mastercard)

Code signing - HTTPs like developer key (example: verified Microsoft publisher

Other:

What kind of information would make you prefer one Requestor over another, to decrease the risk of not being paid?

Additional information about the Requestor would not have impact my decision

Social network based identification(examples: Facebook/Linkedin/Github)

Existence of blockchain domain connected with the Requestor’s node address (examples: ENS domain, Unstoppable Domains)

Existence of DNS domain connected with your node address (example: via TXT record)

Self-sovereign identity (examples: Polygon ID)

Public identity claims (examples: ERC-725 / ERC-735)

Web3 based Social Identification (example: Proof of Humanity)

Full identity document based KYC (example: Onfido or IDnow)

Credit card based proof (examples: Visa, Mastercard)

Code signing - HTTPs like developer key (example: verified Microsoft publisher)

Other:

In order to open outbound network traffic, how would you like to identify the Requestor?

No need for identity identification

Social network based identification (examples: Facebook/Linkedin/Github)

Existence of blockchain domain connected with the Requestor’s node address (examples: ENS domain, Unstoppable Domains)

Existence of DNS domain connected with your node address (example: via TXT record)

Self-sovereign identity (examples: Polygon ID)

Public identity claims (examples: ERC-725 / ERC-735)

Web3 based Social Identification (example: Proof of Humanity)

Full identity document based KYC (example: Onfido or IDnow)

Credit card based proof (examples: Visa, Mastercard)

Code signing - HTTPs like developer key (example: verified Microsoft publisher)

Other:

In order to host services and open an incoming network connection, how would you like to identify the Requestor?

No need for identity identification

Social network based identification (examples: Facebook/Linkedin/Github)

Existence of blockchain domain connected with the Requestor’s node address (examples: ENS domain, Unstoppable Domains)

Existence of DNS domain connected with your node address (example: via TXT record)

Self-sovereign identity (examples: Polygon ID)

Public identity claims (examples: ERC-725 / ERC-735)

Web3 based Social Identification (example: Proof of Humanity)

Full identity document based KYC (example: Onfido or IDnow)

Credit card based proof (examples: Visa, Mastercard)

Code signing - HTTPs like developer key (example: verified Microsoft publisher)

Other:

As a Provider, while participating in the Golem Network, what identity information is acceptable for you to provide?

I do not want to provide any identity information

Social network based data from my Provider (examples: Facebook/Linkedin/Github)

Existence of blockchain domain connected with my Provider’s node address (examples: ENS domain, Unstoppable Domains)

Existence of DNS domain connected with your node address (example: via TXT record)

Self-sovereign identity (examples: Polygon ID)

Public identity claims (examples: ERC-725 / ERC-735)

Web3 based Social Identification (example: Proof of Humanity)

Full identity document-based KYC (example: Onfido or IDnow)

Credit card based proof (examples: Visa, Mastercard)

Code signing - HTTPs like developer key (example: verified Microsoft publisher)

Other:

Submit

Clear form

Never submit passwords through Google Forms.

This form was created inside of Golem Factory. Report Abuse

Forms