Abstract: The present technology pertain to verifying user identity using a proof of satisfaction such as a token, including a non-fungible token. The present technology includes receiving, by a smart contract on a distributed ledger, a request to engage in a transaction, where the smart contract requires an originator of the transaction to prove that it satisfies a requirement that is verifiable by an authority in order to conduct the transaction, and where the requirement is that the originator of the transaction proves that it is not a bot. The smart contract receives a pointer to a proof of satisfaction of the requirement. The proof of satisfaction is verified by following the pointer. The method also includes conducting the transaction after verifying that the requirement has been satisfied.

Abstract: The present technology can allow a user to use the OpenID Connect protocol to login to an account that has an anonymous user account ID. More specifically, the present technology can programmatically combine information received from an OpenID provider during the OpenID Connect protocol with a random value to yield a unique anonymous user account ID. The present technology also makes use of the ability within the OpenID Connect protocol to embed a chosen nonce into the token signed by the OpenID provider. This allows for embedding hashes of cryptographic keys, like signature verification keys, into ID tokens received from the OpenID provider that authenticates the user. Subsequently, the user can sign messages that can be verified using the verification key bound to the ID token from the OpenID provider.

Abstract: The present technology can allow a user to use the OpenID Connect protocol to login to an account that has an anonymous user account ID. More specifically, the present technology can programmatically combine information received from an OpenID provider during the OpenID Connect protocol with a random value to yield a unique anonymous user account ID. The present technology also makes use of the ability within the OpenID Connect protocol to embed a chosen nonce into the token signed by the OpenID provider. This allows for embedding hashes of cryptographic keys, like signature verification keys, into ID tokens received from the OpenID provider that authenticates the user. Subsequently, the user can sign messages that can be verified using the verification key bound to the ID token from the OpenID provider.