Blockchain-based admission processes for protected entities

1. A method for controlling access to a protected entity by a client, comprising:

receiving a redirected request of the client to access the protected entity that was denied by the protected entity, the redirected request including a public key of the client and designating the protected entity to be accessed, the protected entity being an entity to be protected from malicious threats;

granting, in response to the received redirected request, access tokens of a first type to the client, using the public key of the client;

identifying a conversion transaction identifying a request to convert the first type of access tokens with access tokens of a second type, wherein the transaction designates at least the protected entity;

determining a conversion value for converting the first type of access tokens into the second type of access tokens, wherein the conversion value is determined based on at least one access parameter;

converting, based on the determined conversion value, a first sum of the first type of access tokens into a second sum of the second type of access tokens; and

granting the client access to the protected entity when the sum of the second type of access tokens is received as a payment from the protected entity.

2. The method of claim 1 , wherein granting the client access to the protected entity further comprises:

validating the client based on at least a predefined condition, wherein the first-type access tokens are granted only upon successful validation of the client.

3. The method of claim 1 , wherein the first-type access tokens and the second-type access tokens are different types.

4. The method of claim 3 , wherein the first-type access tokens and the second-type access tokens are cryptocurrency tokens having different cryptographic identities.

5. The method of claim 1 , wherein the least one access parameter weights a risk of false positive of granting access to an illegitimate client and of false negative of denying access of a legitimate client.

6. The method of claim 1 , wherein the at least one access parameter is related to any one of: the client, the protected entity, and at least one global indication.

7. The method of claim 1 , wherein determining the conversion value further comprises:

dynamically changing the conversion value based on at least one access parameter.

8. The method of claim 7 , wherein the conversion value is dynamically changed based on any one of: per transaction, per access request from the client, and per session.

9. The method of claim 1 , further comprising:

conditionally granting the client access to the protected entity; and

revoking the conditionally granted access, when a transaction holding the sum of the second type of access tokens is not identified.

10. The method of claim 1 , wherein the conversion transaction includes transaction data, a transaction hash value, and a previous transaction hash value, wherein the transaction data includes a unique transaction identifier (ID), a number of available first-type access tokens, an identification of a source granting the first-type access tokens, and an identifier of the protected entity.

11. The method of claim 10 , wherein the conversion transaction does not include information identifying at least one of: the client and a user of the client.

12. The method of claim 1 , further comprising:

logging at least the identified conversion transaction and the determined conversion value.

13. A non-transitory computer readable medium having stored thereon instructions for causing one or more processing units to execute the method according to claim 1 .

14. An access system for controlling access to a protected entity by a client, comprising:

a processing circuitry; and

a memory, the memory containing instructions that when, executed by the processing circuitry, configure the access system to:

receive a redirected request of the client to access the protected entity that was denied by the protected entity, the redirected request including a public key of the client and designating the protected entity to be accessed, the protected entity being an entity to be protected from malicious threats;

grant, in response to the received redirected request, access tokens of a first type to the client, using the public key of the client;

identify a conversion transaction identifying a conversion of the first type of access tokens with access tokens of a second type, wherein the transaction designates at least the protected entity;

determine a conversion value for converting the first type of access tokens into the second type of access tokens, wherein the conversion value is determined based on at least one access parameter;

convert, based on the determined conversion value, a first sum of the first type of access tokens into a second sum of the second type of access tokens; and

grant the client access to the protected entity when the sum of the second type of access tokens is received as a payment from the protected entity.

15. The system of claim 14 , wherein the access system is further configured to provide its public key to the client.