IDEAS home Printed from https://ideas.repec.org/a/gam/jmathe/v10y2022i14p2422-d860342.html
   My bibliography  Save this article

Achieving Security in Proof-of-Proof Protocol with Non-Zero Synchronization Time

Author

Listed:
  • Lyudmila Kovalchuk

    (Physical Technical Institute, NTUU “Igor Sikorsky Kyiv Polytechnical Institute”, 03056 Kiev, Ukraine)

  • Volodymyr Kostanda

    (Adoriasoft, 61166 Kharkiv, Ukraine)

  • Oleksandr Marukhnenko

    (Faculty of Computer Engineering and Control, Kharkiv National University of Radioelectronics, 61166 Kharkiv, Ukraine)

  • Oleksii Pozhylenkov

    (Department of Mathematics, Physics and IT, Odesa Mechnikov University, 65000 Odesa, Ukraine)

Abstract

Among the most significant problems that almost any blockchain faces are the problems of increasing its throughput (i.e., the number of transactions per unit of time) and the problem of a long waiting time before block confirmation. Thus, for example, in the most common BTC blockchain, according to various estimates, throughput is from 3 to 7 tps (transactions per second), and the average block confirmation time (block is considered confirmed if it has at least 6 blocks over it) is 1 h. At the same time, it is impossible to solve these problems directly by increasing the block size or increasing block generation intensity because this leads to essentially a decrease in the security of the blockchain in the first turn against double spend and splitting attacks. Such problems lead to the inconvenience of the practical use of cryptocurrencies to pay for goods and services. Proposed a few years ago, the PoP consensus protocol potentially helps to solve the problem of increasing blockchain throughput, although it was originally intended to ensure the stability of “young” blockchains, with “small” PoW, through the use of a secure blockchain, such as BTC. A blockchain that has provable security is called the security-provided blockchain (SPB), and one that uses SPB to achieve its security is called the security-inherited blockchain. In this paper, we give explicit formulas which describe how the number of confirmation blocks in the security-inherited blockchain, which is sufficient to achieve a given security level of this blockchain to a double spend attack, depends on the parameters of both blockchains. It is essential that we use a realistic model to obtain the results, taking into account the synchronization times of both blockchains. Such a model is much closer to the real situation, but at the same time, it leads to significant analytical difficulties in obtaining results. The obtained formulas are convenient for numerical calculations, the numerous examples of which are also given in this work.

Suggested Citation

  • Lyudmila Kovalchuk & Volodymyr Kostanda & Oleksandr Marukhnenko & Oleksii Pozhylenkov, 2022. "Achieving Security in Proof-of-Proof Protocol with Non-Zero Synchronization Time," Mathematics, MDPI, vol. 10(14), pages 1-14, July.
  • Handle: RePEc:gam:jmathe:v:10:y:2022:i:14:p:2422-:d:860342
    as

    Download full text from publisher

    File URL: https://www.mdpi.com/2227-7390/10/14/2422/pdf
    Download Restriction: no

    File URL: https://www.mdpi.com/2227-7390/10/14/2422/
    Download Restriction: no
    ---><---

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:gam:jmathe:v:10:y:2022:i:14:p:2422-:d:860342. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: MDPI Indexing Manager (email available below). General contact details of provider: https://www.mdpi.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.