Cryptographic systems and methods for providing services to authenticated users

1. A method, comprising:

receiving, at a broker processor and from a prover processor, a user request, a user token, and a user cryptographic zero-knowledge proof associated with a user characteristic;

receiving, at the broker processor, from a service processor, and based on the user request and the user token being received at the service processor from the prover processor, a requirements specification and the user token;

generating, via the broker processor, a broker cryptographic zero-knowledge proof based on the requirements specification and the user cryptographic zero-knowledge proof; and

transmitting, via the broker processor and to the service processor, the broker cryptographic zero-knowledge proof to cause the service processor to fulfill the user request.

2. The method of claim 1 , wherein the user token is associated with a user for at least one of a pre-defined time period or a pre-defined number of uses.

3. The method of claim 1 , wherein the user request includes a request associated with a uniform resource locator (URL).

4. The method of claim 1 , wherein the user cryptographic zero-knowledge proof is based on (1) a user profile organized according to a schema and (2) an indication of data within the user profile to be verified.

5. The method of claim 4 , wherein the requirements specification includes the indication of the data.

6. The method of claim 4 , wherein:

the indication of the data includes an indication of public data; and

the indication of the public data is associated with a signed hash tree root generated by a trusted third party (TTP).

7. The method of claim 1 , wherein the user cryptographic zero-knowledge proof is the broker cryptographic zero-knowledge proof.

8. The method of claim 1 , wherein the user cryptographic zero-knowledge proof is different from the broker cryptographic zero-knowledge proof.

9. An apparatus, comprising:

a processor; and

a memory operably coupled to the processor, the memory storing instructions to cause the processor to:

receive, from a prover processor, a user request, a user token, and a user cryptographic zero-knowledge proof associated with a user characteristic;

receive, from a service processor and based on the user request and the user token being received at the service processor from the prover processor, a requirements specification and the user token;

generate a broker cryptographic zero-knowledge proof based on the requirements specification and the user cryptographic zero-knowledge proof; and

transmit, to the service processor, the broker cryptographic zero-knowledge proof to cause the service processor to fulfill the user request.

10. The apparatus of claim 9 , wherein the user token is associated with a user for at least one of a pre-defined time period or a pre-defined number of uses.

11. The apparatus of claim 9 , wherein the user request includes a request associated with a uniform resource locator (URL).

12. The apparatus of claim 9 , wherein the user cryptographic zero-knowledge proof is based on (1) a user profile organized according to a schema and (2) an indication of data within the user profile to be verified.

13. The apparatus of claim 12 , wherein the requirements specification includes the indication of the data.

14. The apparatus of claim 12 , wherein:

the indication of the data includes an indication of public data; and

the indication of the public data is associated with a signed hash tree root generated by a trusted third party (TTP).

15. The apparatus of claim 9 , wherein the user cryptographic zero-knowledge proof is the broker cryptographic zero-knowledge proof.

16. The apparatus of claim 9 , wherein the user cryptographic zero-knowledge proof is different from the broker cryptographic zero-knowledge proof.

17. A non-transitory, processor-readable medium storing instructions that, when executed by a processor, cause the processor to:

receive, from a prover processor, a user request, a user token, and a user cryptographic zero-knowledge proof associated with a user characteristic;

receive, from a service processor and based on the user request and the user token being received at the service processor from the prover processor, a requirements specification and the user token;

generate a broker cryptographic zero-knowledge proof based on the requirements specification and the user cryptographic zero-knowledge proof, and

transmit, to the service processor, the broker cryptographic zero-knowledge proof to cause the service processor to fulfill the user request.

18. The non-transitory, processor-readable medium of claim 17 , wherein the user token is associated with a user for at least one of a pre-defined time period or a pre-defined number of uses.

19. The non-transitory, processor-readable medium of claim 17 , wherein the user request includes a request associated with a uniform resource locator (URL).

20. The non-transitory, processor-readable medium of claim 17 , wherein the user cryptographic zero-knowledge proof is based on (1) a user profile organized according to a schema and (2) an indication of data within the user profile to be verified.

21. The non-transitory, processor-readable medium of claim 20 , wherein the requirements specification includes the indication of the data.

22. The non-transitory, processor-readable medium of claim 20 , wherein:

the indication of the data includes an indication of public data; and

the indication of the public data is associated with a signed hash tree root generated by a trusted third party (TTP).

23. The non-transitory, processor-readable medium of claim 17 , wherein the user cryptographic zero-knowledge proof is the broker cryptographic zero-knowledge proof.

24. The non-transitory, processor-readable medium of claim 17 , wherein the user cryptographic zero-knowledge proof is different from the broker cryptographic zero-knowledge proof.