Blockchain-based admission processes for protected entities

1. A method for blockchain-based access to a protected entity, the protected entity being an entity to be protected from malicious threats, comprising:

granting access tokens of a first-type to a client;

identifying, in a blockchain network, 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, the function of the protected entity being unrelated to operation of the blockchain network.

2. The method of claim 1 , further comprising:

validating the client based on at least a predefined condition; and

granting the first-type access tokens, upon 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 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 on the blockchain network.

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 , wherein the conversion transaction is realized as at least one of: a smart contract on the blockchain network, and an off-chain Oracle on the blockchain network.

13. The method of claim 1 , further comprising:

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

14. 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 .

15. An access system for blockchain-based access to a protected entity, the protected entity being an entity to be protected from malicious threats, comprising:

a processing circuitry; and

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

grant access tokens of a first-type to a client;

identify, in a blockchain network, 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 access tokens into a second sum of the second-type 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, the function of the protected entity being unrelated to operation of the blockchain network.

16. The system of claim 15 , wherein the system is further configured to:

validate the client based on at least a predefined condition; and

grant the first-type access tokens, upon validation of the client.

17. The system of claim 15 , wherein the first-type access tokens and the second-type access tokens are different types.

18. The system of claim 15 , wherein the first-type access tokens and the second-type access tokens are cryptocurrency tokens having different cryptographic identities.

19. The system of claim 15 , wherein the least one access parameter weights a risk of false positive of granting admission to an illegitimate client and of false negative of denying admission of a legitimate client.

20. The system of claim 15 , wherein the at least one access parameter is related to any one of: the client, the protected entity, and at least one global indication.

21. The system of claim 15 , wherein the system is further configured to:

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

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

23. The system of claim 15 , wherein the system is further configured to:

conditionally grant the client access to the protected entity; and

revoke the conditionally granted access, when a transaction holding the sum of the second-type of access tokens is not identified on the blockchain network.

24. The system of claim 15 , 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.

25. The system of claim 24 , wherein the conversion transaction does not include information identifying at least one of: the client, and a user of the client.

26. The system of claim 15 , wherein the conversion transaction is realized as at least one of: a smart contract on the blockchain network, and an off-chain Oracle on the blockchain network.

27. The system of claim 15 , wherein the system is further configured to:

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