@Article{hajdu20using,
  author       = {Hajdu, {\'A}kos and Ivaki, Naghmeh and Kocsis, Imre and Klenik, Attila and G{\"o}nczy, L{\'a}szl{\'o} and Laranjeiro, Nuno and Madeira, Henrique and Pataricza, Andr{\'a}s},
  date         = {2020},
  journaltitle = {IEEE Access},
  title        = {Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts},
  pages        = {190760--190783},
  volume       = {8},
  comment      = {* implemented and evaluated for Hyperledger Fabric
* do code modification

  * based on abstract syntax tree, tool: Solc

* execute fault-free and faulty variants of Smart Contracts
* additionally formally verify fault-free and faulty variants of Smart
  Contracts

  * Smart Contracts code must be annotated with specification
    (invariants etc.)
  * formal verification fails, if unexpected error occurs

    * e.g., assert statements failing, overflows
    * *not* including errors caused by guards

      * e.g., ``require`` statements

* fault model

  * overflow
  * insufficient randomness
  * missing/wrong

    * faulty variable initialization (incl. their absence)
    * conditional statements
    * ``require`` statements
    * API usage (e.g., call ``SafeMath``)
    * ans so on (\# fault model is interesting: not too small and well
      structured)

* workload generated
* evaluation using 15 algorithms

  * 5 algorithms of common algorithms

    * each with two additional version

      * one with protection mechanisms removed
      * one with more protection mechanisms added

  * large set of results (fault types X algorithms X how detected X …)
  * evaluate effectiveness of error detection

* reflect on threats to validity of their findings \#wow
* \# overall a comprehensive, detailed work},
  file         = {:hajdu20using - Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts.pdf:PDF},
  groups       = {fault injection},
  publisher    = {IEEE},
  timestamp    = {2021-01-20},
}

{"_id":"WFhnmAF2gFDD9XiEs","bibbaseid":"hajdu-ivaki-kocsis-klenik-gnczy-laranjeiro-madeira-pataricza-usingfaultinjectiontoassessblockchainsystemsinpresenceoffaultysmartcontracts","author_short":["Hajdu, Á.","Ivaki, N.","Kocsis, I.","Klenik, A.","Gönczy, L.","Laranjeiro, N.","Madeira, H.","Pataricza, A."],"bibdata":{"bibtype":"article","type":"article","author":[{"propositions":[],"lastnames":["Hajdu"],"firstnames":["Ákos"],"suffixes":[]},{"propositions":[],"lastnames":["Ivaki"],"firstnames":["Naghmeh"],"suffixes":[]},{"propositions":[],"lastnames":["Kocsis"],"firstnames":["Imre"],"suffixes":[]},{"propositions":[],"lastnames":["Klenik"],"firstnames":["Attila"],"suffixes":[]},{"propositions":[],"lastnames":["Gönczy"],"firstnames":["László"],"suffixes":[]},{"propositions":[],"lastnames":["Laranjeiro"],"firstnames":["Nuno"],"suffixes":[]},{"propositions":[],"lastnames":["Madeira"],"firstnames":["Henrique"],"suffixes":[]},{"propositions":[],"lastnames":["Pataricza"],"firstnames":["András"],"suffixes":[]}],"date":"2020","journaltitle":"IEEE Access","title":"Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts","pages":"190760–190783","volume":"8","comment":"* implemented and evaluated for Hyperledger Fabric * do code modification * based on abstract syntax tree, tool: Solc * execute fault-free and faulty variants of Smart Contracts * additionally formally verify fault-free and faulty variants of Smart Contracts * Smart Contracts code must be annotated with specification (invariants etc.) * formal verification fails, if unexpected error occurs * e.g., assert statements failing, overflows * *not* including errors caused by guards * e.g., ``require`` statements * fault model * overflow * insufficient randomness * missing/wrong * faulty variable initialization (incl. their absence) * conditional statements * ``require`` statements * API usage (e.g., call ``SafeMath``) * ans so on (# fault model is interesting: not too small and well structured) * workload generated * evaluation using 15 algorithms * 5 algorithms of common algorithms * each with two additional version * one with protection mechanisms removed * one with more protection mechanisms added * large set of results (fault types X algorithms X how detected X …) * evaluate effectiveness of error detection * reflect on threats to validity of their findings #wow * # overall a comprehensive, detailed work","file":":hajdu20using - Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts.pdf:PDF","groups":"fault injection","publisher":"IEEE","timestamp":"2021-01-20","bibtex":"@Article{hajdu20using,\n author = {Hajdu, {\\'A}kos and Ivaki, Naghmeh and Kocsis, Imre and Klenik, Attila and G{\\\"o}nczy, L{\\'a}szl{\\'o} and Laranjeiro, Nuno and Madeira, Henrique and Pataricza, Andr{\\'a}s},\n date = {2020},\n journaltitle = {IEEE Access},\n title = {Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts},\n pages = {190760--190783},\n volume = {8},\n comment = {* implemented and evaluated for Hyperledger Fabric\n* do code modification\n\n * based on abstract syntax tree, tool: Solc\n\n* execute fault-free and faulty variants of Smart Contracts\n* additionally formally verify fault-free and faulty variants of Smart\n Contracts\n\n * Smart Contracts code must be annotated with specification\n (invariants etc.)\n * formal verification fails, if unexpected error occurs\n\n * e.g., assert statements failing, overflows\n * *not* including errors caused by guards\n\n * e.g., ``require`` statements\n\n* fault model\n\n * overflow\n * insufficient randomness\n * missing/wrong\n\n * faulty variable initialization (incl. their absence)\n * conditional statements\n * ``require`` statements\n * API usage (e.g., call ``SafeMath``)\n * ans so on (\\# fault model is interesting: not too small and well\n structured)\n\n* workload generated\n* evaluation using 15 algorithms\n\n * 5 algorithms of common algorithms\n\n * each with two additional version\n\n * one with protection mechanisms removed\n * one with more protection mechanisms added\n\n * large set of results (fault types X algorithms X how detected X …)\n * evaluate effectiveness of error detection\n\n* reflect on threats to validity of their findings \\#wow\n* \\# overall a comprehensive, detailed work},\n file = {:hajdu20using - Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts.pdf:PDF},\n groups = {fault injection},\n publisher = {IEEE},\n timestamp = {2021-01-20},\n}\n\n","author_short":["Hajdu, Á.","Ivaki, N.","Kocsis, I.","Klenik, A.","Gönczy, L.","Laranjeiro, N.","Madeira, H.","Pataricza, A."],"key":"hajdu20using","id":"hajdu20using","bibbaseid":"hajdu-ivaki-kocsis-klenik-gnczy-laranjeiro-madeira-pataricza-usingfaultinjectiontoassessblockchainsystemsinpresenceoffaultysmartcontracts","role":"author","urls":{},"metadata":{"authorlinks":{}},"downloads":0,"html":""},"bibtype":"article","biburl":"https://bibbase.org/network/files/AsPiHTmHHGjgy6xSQ","dataSources":["wjZw5s4JL49uLwn3p"],"keywords":[],"search_terms":["using","fault","injection","assess","blockchain","systems","presence","faulty","smart","contracts","hajdu","ivaki","kocsis","klenik","gönczy","laranjeiro","madeira","pataricza"],"title":"Using Fault Injection to Assess Blockchain Systems in Presence of Faulty Smart Contracts","year":null}