Collecting surveys with secure identities via a blockchain

1. A computer-implemented method for collecting surveys with a secure identity, the method comprising:

posting, from a requesting system to a blockchain, a request (i) pertaining to a survey and (ii) targeted to an attribute of a user;

determining, via the blockchain, that a user profile includes an attribute that matches with the attribute of the request;

transmitting, via the blockchain and in response to determining that the user profile includes the attribute that matches with the attribute of the request, the request to a device associated with the user profile;

receiving, from the device associated with the user profile, a response to the request;

generating, to the blockchain, a commitment based on the response to the request; and

transmitting, from the blockchain to the requesting system, the commitment.

2. The method of claim 1 , wherein determining that the user profile includes the attribute that matches with the attribute of the request comprises performing, between the device associated with the user profile and the requesting system, a zero-knowledge (ZK) proof.

3. The method of claim 2 , wherein the ZK proof is a zero-knowledge succinct non-interactive argument of knowledge (ZKSNARK).

4. The method of claim 1 , wherein the request is targeted to a plurality of attributes of the user, and wherein determining that the user profile includes the attribute that matches with the attribute of the request comprises determining that the user profile includes a plurality of attributes that match with the plurality of attributes of the request.

5. The method of claim 1 , further comprising:

determining that the response is properly completed; and

holding the response in a smart contract associated with the blockchain.

6. The method of claim 5 , wherein the request includes an amount of tokens to be held in escrow, the method further comprising:

paying, in response to determining that the response is properly completed, the amount of tokens to a user associated with the user profile.

7. The method of claim 5 , further comprising:

transmitting, in response to determining that the response is properly completed, the properly completed response held within the smart contract to the requesting system.

8. The method of claim 1 , further comprising:

receiving additional user profile information; and

paying, in response to receiving the additional user profile information, an amount of tokens to a user associated with the user profile.

9. The method of claim 1 , further comprising:

adding, to the blockchain, results of the matching of the attribute between the user profile and the request.

10. The method of claim 1 , wherein posting the request comprises adding a transaction to the blockchain in sequence with other data broadcasted during a contemporary time window.

11. The method of claim 10 , wherein adding the transaction to the blockchain in sequence with other data broadcasted during the contemporary time window comprises adding the transaction to a new block or to an existing block of the blockchain.

12. The method of claim 1 , wherein the blockchain is a tamper-resistant ledger comprising a chronological ordering of a plurality of blocks.

13. The method of claim 1 , wherein the commitment is generated using an elliptic curve scalar multiplication.

14. A system comprising one or more processors and storage media storing instructions which, when executed by the one or more processors, cause:

posting, from a requesting system to a blockchain, a request (i) pertaining to a survey and (ii) targeted to an attribute of a user;

determining, via the blockchain, that a user profile includes an attribute that matches with the attribute of the request;

transmitting, via the blockchain and in response to determining that the user profile includes the attribute that matches with the attribute of the request, the request to a device associated with the user profile;

receiving, from the device associated with the user profile, a response to the request;

generating, to the blockchain, a commitment based on the response to the request; and

transmitting, from the blockchain to the requesting system, the commitment.

15. The system of claim 14 , wherein the instructions when executed cause determining that the user profile includes the attribute that matches with the attribute of the request by performing, between the device associated with the user profile and the requesting system, a zero-knowledge (ZK) proof.

16. The system of claim 15 , wherein the ZK proof is a zero-knowledge succinct non-interactive argument of knowledge (ZKSNARK).

17. The system of claim 14 , wherein the request is targeted to a plurality of attributes of the user, and wherein the instructions when executed cause determining that the user profile includes the attribute that matches with the attribute of the request by determining that the user profile includes a plurality of attributes that match with the plurality of attributes of the request.

18. The system of claim 14 , wherein the storage media stores further instructions which when executed cause:

determining that the response is properly completed; and

holding the response in a smart contract associated with the blockchain.

19. The system of claim 17 , wherein the request includes an amount of tokens to be held in escrow, and the storage media stores further instructions which when executed cause paying, in response to determining that the response is properly completed, the amount of tokens to a user associated with the user profile.

20. The system of claim 14 , wherein the storage media stores further instructions which when executed cause:

receiving additional user profile information; and

paying, in response to receiving the additional user profile information, an amount of tokens to a user associated with the user profile.

21. The system of claim 14 , wherein the storage media stores further instructions which when executed cause adding, to the blockchain, results of the matching the attribute between the user profile and the request.