Method for determining a cost to allow a blockchain-based admission to a protected entity

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

identifying, in a blockchain network, a conversion transaction identifying a conversion of a 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 access tokens, wherein the conversion value is determined based on at least one access parameter; and

converting, 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, wherein

a client spends the second sum of the second-type access tokens to access the protected entity, the determined conversion value is the access cost to the protected entity, the function of the protected entity being unrelated to operation of the blockchain network.

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

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

4. The method of claim 1 , wherein the least one access parameter weights a risk of false positive and false negative of denying access of a legitimate client.

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

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

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

7. The method of claim 5 , 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 identification (ID), a number of available first-type access tokens, an identification of a source granting the first-type access tokens, and the protected entity.

8. The method of claim 7 , wherein the conversion transaction does not include information identifying the client or a user of the client.

9. The method of claim 1 , wherein the conversion transaction is realized at least one of: a written contract on the blockchain network on an off-chain Oracle on the blockchain network.

10. The method of claim 1 , further comprising:

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

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

12. A conversion system for providing a 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 conversion system to:

identify, in a blockchain network, a conversion transaction identifying a conversion of a 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 access tokens into the second-type access tokens, wherein the conversion value is determined based on at least one access parameter; and

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, wherein

a client is required to spend the second sum of the second-type of access tokens to access the protected entity, the determined conversion value is the access cost to the protected entity, the function of the protected entity being unrelated to operation of the blockchain network.

13. The conversion system of claim 12 , wherein the first-type access tokens and the second-type access tokens are different types.

14. The exchange system of claim 12 , wherein of the first-type access token and the second-type access token are cryptocurrency tokens having different cryptographic identities.

15. The conversion system of claim 12 , wherein the least one access parameter weights a risk of false positive and false negative of denying access of a legitimate client.

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

17. The conversion system of claim 12 , wherein the conversion system is further configured to:

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

18. The conversion system 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 identification (ID), a number of available first-type access tokens, an identification of a source granting the first-type access tokens, and the protected entity.

19. The conversion system of claim 17 , wherein the conversion transaction does not include information identifying the client or a user of the client.

20. The conversion system of claim 17 , wherein the conversion transaction is realized at least one of: a written contract on the blockchain network on an off-chain Oracle on the blockchain network.

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

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