KYC (Know Your Customer) - survey for the requestor

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 Requestor point of view:

As a Requestor in the Golem Network, your private data files will be uploaded to Providers’ machines. Your code will also run on untrusted hardware, which creates another potential risk. Both can be mitigated with some level of Provider identification.

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

What kind of information about a Provider would increase your trust level? *

I do not need any information about my Provider

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:

Required

As a Requestor, 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