<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>Tunisian-Algerian Joint Conference on Applied Computing, November</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>A survey on event log extraction from blockchain</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ahlem Makni</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rawya Mars</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Saoussen Cheikhrouhou</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Slim Kallel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mohamed Sellami</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Digital Research Center of Sfax</institution>
          ,
          <country country="TN">Tunisia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>ReDCAD Laboratory, ENIS, University of Sfax</institution>
          ,
          <country country="TN">Tunisia</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>SAMOVAR, Télécom SudParis, Institut Polytechnique de Paris</institution>
          ,
          <addr-line>91120 Palaiseau</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <volume>0</volume>
      <fpage>6</fpage>
      <lpage>08</lpage>
      <abstract>
        <p>To address the traceability challenges associated with inter-organizational business processes enactment, one potential solution is to rely on the blockchain technology . In such cases, establishing process traceability requires analyzing and leveraging blockchain logs. In order to contribute to the discourse on this issue, this paper presents a comprehensive review of existing literature conducted to explore the multifaceted landscape of traceability in business processes. The review synthesizes a diverse range of studies focusing on the use of blockchain logs. These logs not only capture individual events but also ofer valuable insights into the entities involved in these processes . Researchers studied these entities using process mining techniques to unravel their complex lifecycles. Finally, this review of the literature has led to the identification of two categories of logs that can be linked with traceability within blockchain technology.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Business process</kwd>
        <kwd>Process mining</kwd>
        <kwd>Event log</kwd>
        <kwd>Blockchain</kwd>
        <kwd>Smart contracts</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Inter-Organizational Business Processes have become an integral component of modern business
practices. Essentially, IOBPs involve the collaboration between various organizations in order to
accomplish mutually agreed-upon objectives. However, a considerable challenge in the execution
of IOBP is the inherent lack of trust among collaborators, which can lead to disputes regarding
counterfeiting activities. To address this issue, recent discussions have proposed the integration
of Blockchain technology for more secure and transparent management of IOBP execution. The
concepts of blockchain and distributed ledgers have gained significant attention and sparked
numerous projects across various industries. One of the major challenges to Blockchain adoption
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], is ensuring seamless integration and interoperability [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] between diferent platforms. Two
widely utilized blockchain platforms are Ethereum and Hyperledger, which play a pivotal
role in advancing this revolutionary technology. In addition, other approaches [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] have been
proposed to leverage the trusted smart contract execution environment provided by blockchain
technology to enforce collaborative business processes. These can be observed or identified in
Caterpillar and Lorikeet. Caterpillar [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] is the first blockchain-based process execution engine
has the ability to handle process models that contain subprocesses and utilizes the Ethereum
blockchain to store the current status of each process instance, while employing smart contracts
generated by a BPMN [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] to Solidity 1 compiler for workflow routing. Lorikeet [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], for instance,
presents an innovative approach that can seamlessly bridge the gap between business process
specifications and smart contract execution, . It is a a Model-Driven Engineering (MDE) tool
that incorporates the methodology proposed by Weber et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and utilizes the translation
algorithm developed by Garcia et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Lorikeet has been successfully employed in various
industry projects, highlighting the practicality of generating process-oriented smart contracts.
As blockchain technology continues to be adopted in various industries and its applications
expand, a significant problem arises: how can we ensure the traceability between Business
Process Models and their actual execution, especially in Inter-Organizational Business Processes
(IOBPs) relying on multiple blockchain platforms ? One of the challenges in adopting blockchain
platforms for business processes is striking a balance between data privacy and security on
one hand, and transparency and trust among participants on the other. To illustrate this
challenge, we refer to a pharmaceutical supply chain [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This particular case study aims to
achieve two goals: (i) authentication of verification requests using verifiable credentials, and (ii)
improved verification processes between pharmacies and manufacturers. Through analyzing
event logs and transaction data recorded on blockchains, process mining provides insights
into how business processes are executed in reality [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. By reconstructing and visualizing
actual processes, process mining helps identify deviations from the intended BPM, ensuring
compliance and alignment in IOBPs. It should be noted that there can be variations in the
format and content of extracted, as diferent methods may be used to record events. Some
event logs focus on tracking activities within a business process, while others are specific to
certain involved objects. Recent studies in this field have demonstrated a notable emphasis on
event logs that are centered around objects rather than activities [
        <xref ref-type="bibr" rid="ref11 ref12">11, 12</xref>
        ]. This shift towards
object-centric event logs is motivated by the dificulties related to convergence and divergence
within activity-based event logs. For instance, considering a BP related to a pharmaceutical
supply chain, we can notice an significant number of important object-centric interactions in
addition to the activity centric ones. For instance, an object in this process, e.g., a purchase
order can be created, approved, Transmitted and confirmed. Every stage, beginning with order
placement and concluding with product delivery. In this paper, we aim at categorizing existing
work that concentrate on both activity and object event logs.
      </p>
      <p>The organization of this paper is as follows. Section 2 provides a detailed overview of blockchain
logging. Section 3 presents other logs format distinct from those extracted from the blockchain.
We thoroughly evaluate and discuss these works Section 4. Finally, in Section 5, concluding
remarks are made along with suggestions for future directions.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Blockchain logging</title>
      <p>In this section, we provide a comprehensive review of prior research in the area of extracting logs
from blockchains. Numerous studies have explored this topic, with certain works emphasizing
objects and others focusing on activities. We categorize the various studies for extracting
logs into three distinct groups: event-centric extraction, object-centric extraction and hybrid
approaches.</p>
      <sec id="sec-2-1">
        <title>2.1. Event-centric Extraction</title>
        <p>
          In this subsection, we refer to approaches focus on capturing specific events or activity that occur
on the blockchain, regardless of the related entities. The primary focus is to track and record
events like transfers, contract invocations, consensus changes, etc. In [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ], the authors present
extracted data from the blockchain into event logs formatted according to the IEEE Extensible
Event Stream (XES) standard [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. This approach is based on a configuration file called Manifest,
provides a set of rules for logging relevant process information into the blockchain, ensuring that
all the required data is captured and after that data extractor retrieves the logged information
from the blockchain and transforms it into a suitable format for process mining. By following
this framework, organizations can efectively utilize their existing blockchain infrastructure to
derive valuable insights into their business processes. Nevertheless, this framework is primarily
centered around Ethereum and needs to be adapted when applied to diferent blockchain systems.
Additionally, its functionality is constrained as it only supports a specific range of value builders.
It also has limited capabilities for handling complex conditions in attribute and element filtering,
and lacks comprehensive support for low-level logging interfaces.
        </p>
        <p>
          The authors of [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] describe their method for extracting process data from an Ethereum
blockchain ledger and converting it into a format that complies with the IEEE XES standard.
They validate their approach with a proof-of-concept prototype relying on an Ethereum’s public
blockchain smart contracts dataset. Their methodology allows extracting blockchain process
data, storing it as XES event logs, and supports data analysis through process mining techniques.
Adherence to IEEE XES ensures compatibility with existing process mining tools in the ProM 2
and Disco 3 toolkit. However, this work did not consider certain key aspects. For instance, not
properly aligning smart contract functions with process activities can lead to inaccuracies in
process mining due to potential mismatches. Moreover, assuming that each process instance
corresponds to a single smart contract may not always be valid, necessitating the use of more
sophisticated reconciliation techniques and obtaining supplementary data from certified sources
like oracles for precise timing information.
        </p>
        <p>
          The primary objective of the study in [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] is to extract event logs from decentralized
applications deployed and executed on the public Ethereum blockchain. The researchers utilized a
tool called ELF [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] to extract the event logs, which are available in XES format. In their work,
Bandara et al. demonstrated how data extraction was performed for four diferent blockchain
2https://promtools.org/
3https://fluxicon.com/disco/
applications: Augur 4, Forsage 5, CryptoKitties 6, and ChickenHunt 7. It is crucial to recognize
the constraints that need to be taken into account. Although ELF was primarily developed
for compatibility with Ethereum, it might necessitate modifications when utilized on
alternative blockchain platforms that employ distinct logging mechanisms. Moreover, while ELF
provides valuable functionality, it does impose certain limitations such as partial support for
more complex log extraction scenarios.
        </p>
        <p>
          Another approach [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] specifically focused on extracting process data from smart contracts
deployed on Hyperledger Fabric and Composer, which export them in CSV format. Their chosen
use case revolved around vehicle manufacturing networks. In choosing to focus on Hyperledger
Fabric and Composer rather than Ethereum, a pragmatic consideration was taken into account.
Unlike Ethereum, which has been observed to generate empty blocks during mining operations
resulting in complex and congested event logs, Hyperledger Fabric and Composer were deemed
more suitable for business-oriented smart contracts that prioritize clarity and eficiency over
unnecessary complexity. This decision aligns with the specific needs of their use case but
may limit the direct applicability of their approach within the broader blockchain landscape.
It emphasizes how crucial it is to select an appropriate blockchain platform based on the
particular requirements and characteristics of each application, as diferent platforms ofer
distinct advantages and disadvantages depending on the intended use case.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Object-centric Extraction</title>
        <p>In this Subsection, we enumerate approaches which focus on particular elements or entities
extracted from blockchain. The recovery of events is closely related to these elements, their
characteristics, or how they interact with one another. Identifying the entity that generates an
event is essential, and events are often located in the attributes or actions associated with these
objects.</p>
        <p>
          A noteworthy approach [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] dedicated to extracting OCELs logs from blockchain data, with
a primary focus on leveraging the capabilities of the Ethereum blockchain. In [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ], authors
provides an initial evaluation of the proposed methodology, rigorously assessing its technical
feasibility and performance. Furthermore, this study conducts a comparative analysis by
comparing the resulting OCEL-log to a prior case study that used the XES format. However,
The application of Object-Centric Event Logs in blockchain applications, like Augur 8, exposes
certain constraints. These constraints become evident when considering the simultaneous
existence of various entities, including DApp CAs, transactions, and user accounts. These
objects may undergo changes in their roles throughout a given process. It is worth noting that
OCEL currently does not provide explicit support for documenting these role transitions. As a
result, accurately representing the complete historical development of an object, including its
changing roles over time, poses a significant challenge. For instance, a token in Augur can be
assigned to the same user account as both the sender and receiver. However, OCEL currently
4https://augur.net/
5https://fr.bitdegree.org/traqueur-de-crypto/top-ethereum-dapps/forsage
6https://www.cryptokitties.co/
7https://chickenhunt.io/
8Augur is a peer-to-peer, decentralized exchange, enabling universal and transparent access to its markets
does not provide explicit support for documenting how an object’s roles change over time.
        </p>
        <p>
          The storage of event data has predominantly been done using "flat" formats such as XES.
However, a novel and more advanced data format named XOC [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] was introduced to address
certain limitations associated with previous formats. Unlike its predecessors, XOC does not
rely on a case notion and also avoids flattening multi-dimensional data. Notably, there has been
further progress in this area with the introduction of OCEL - an even more eficient log format
that surpasses its predecessor in terms of both storage capacity and processing capabilities.
        </p>
        <p>
          In [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], the authors introduced ACEL, a novel logging format and a novel solution for
extracting blockchain data from artifact-centric applications and transforming it into a structured
format tailored for process mining methods. ACEL logs ofers a more comprehensive and
enriching log format compared to the OCEL format. They capture data related to objects and
their evolutionary journey over time, as well as their intricate relationships with other entities.
As a result, ACEL logs emerge as a solid option choice for capturing event data originating from
artifact-centric applications, providing a more detailed and nuanced perspective on the dynamics
of these systems. This study highlights two primary constraints. Firstly, the extraction of ACEL
logs from blockchain relies on a manually written configuration file. Authors acknowledges the
potential dificulties users may face when writing these files. Secondly, the current extraction
algorithm is tailored specifically for Ethereum and therefore restricts its broader applicability to
other contexts or platforms.
        </p>
        <p>
          A novel logging framework called BLF is introduced in [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. This logging framework
specifically caters to decentralized applications on the blockchain, ofering an innovative solution for
analyzing event data from these applications and facilitating the extraction and interpretation
of logs. The authors emphasize that while BLF was initially developed for Ethereum and
Hyperledger blockchains, it has the potential for expansion in order to support other blockchain
platforms as well. The case studies employed in BLF include the widely recognized Ethereum
game known as CryptoKitties, as well as Augur. To explore these case studies further,
Hyperkitties an implementation of the CryptoKitties Ethereum smart contract within the Hyperledger
platform, was utilized. The primary aim to extract events from HyperKitties found within
various blocks and subsequently generate an event log formatted document in XES. The current
work lacks the exploration of other platforms beyond Ethereum and Hyperledger. Additionally,
it appears that there is room for further enhancement in the Blockchain Query Language (BcQl)
language.
        </p>
        <p>
          It is worth noting that apart from variations in log formats, several other aspects are being
explored like data-awareness of object-centric event logs [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ] and artifact centric event logs
[
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. This particular format established a restriction on the capabilities of OCEL to handle
object attributes that have dynamic values which may change over time [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. The DOCEL
format has been developed to tackle the identified concerns and improve the way process data,
involving various types of objects, is represented and analyzed. Hence, it can be stated that this
particular format serves as an expansion of the OCEL format. The authors present a proposed
method for transforming XES logs into DOCEL logs. Consolidating multiple XES format event
logs about each object involved in the process can be quite dificult. However, this algorithm
efectively combines these individual XES files into one cohesive DOCEL log while maintaining
the essential data flow characteristics that make XES a desirable event log format.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Hybrid Approaches</title>
      <p>In this section, we provide an overview of several approaches that integrate both event-centric
and object-centric strategies. These approaches enable the capturing of specific events within
the context of particular objects. They are aimed at transforming conventional event logs into
their object-centric counterparts.</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ], the authors have explored a method for converting an XES log format into an OCEL
log. In order to accomplish this objective, the authors integrate the process of analyzing semantic
characteristics within the text with the techniques of data profiling and control-flow-based
relation extraction. This method reveals additional data that was not initially recorded in
the OCEL log. This entails the incorporation of additional types of objects, attributes, and
connections, which enables a more comprehensive understanding of the process. However, One
of the main challenges we faced in their approach was determining the relationships between
objects in a 1:n relationship with the core case object. This complexity resulted in several
incorrect assignments of instances to their corresponding events.
      </p>
      <p>
        Currently,there is ongoing research focused on the automation of converting XES logs into
OCEL logs. Authors of [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] propose an algorithm to extract event data and transform it into
ACEL format. Also, authors of [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] propose an algorithm to transform XES logs into DOCEL
logs with the primary objective to associate all attributes with their respective objects. This
new format resolves the limitations of OCEL. It allows for a clear association of attributes with
both events and objects, as well as tracking changes in attribute values. Nevertheless, there are
certain constraints that need to be addressed in both the XES and DOCEL formats. In particular,
these limitations include a lack of ability to distinguish between object roles in events and
the absence of support for managing multiple objects within a single XES file. To overcome
such challenges, future research could explore opportunities for developing new algorithms
in DOCEL specifically aimed at object-centric process discovery and conformance checking.
This would help address the identified deficiencies while also opening up new avenues for
exploration.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. Comparison and discussion</title>
      <sec id="sec-4-1">
        <title>4.1. Activity vs object centric event logs</title>
        <p>After conducting our comprehensive review of existing approaches, we identify two distinct
methodology categories for extracting logs from blockchain. Our in-depth evaluation and
comparison between these categories, is summarized in Table 1 which exhibits the chronological
development of activity-centric and object-centric logs extraction methods and emphasises the
sequential advancement of log extraction methods over time.</p>
        <p>
          In recent research, there is a noticeable shift taking place: there is an increasing focus on
object-centric analyses as opposed to the established activity-centric ones. Many
ActivityCentric log approaches typically favor the XES format due to its versatility and compatibility
with various tools and platforms for event log analysis. However, in a specific case study [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]
conducted in 2021, the CSV format was chosen as the preferred format for recording logs on the
Hyperledger Fabric/Composer blockchain platform. This exceptional decision may be attributed
        </p>
        <p>Classification
Activity-Centric Logs
Object-Centric Logs
to specific requirements or constraints of the platform, highlighting how log formats can adapt
according to diferent blockchain platforms and use cases. In 2021, a significant transition
occurred in research, shifting the focus from activity-centric analysis to object-centric analysis
and this evolution underscores an increasingly acknowledged importance of delving into the
behaviors and interactions of individual objects within intricate systems. While event logs, a
mainstay in process mining, have conventionally been employed to capture sequential actions,
contemporary scholars are gravitating toward object-centric logs due to their potential to ofer
a more thorough grasp of system dynamics. It is important to note that event logs frequently
do not provide explicit information about the entities or objects involved in processes. This
can lead to challenges when trying to understand and analyze complex interrelationships. In
contrast, object-centric logs ofer a potential solution to these challenges. By placing emphasis
on analyzing the states, properties, and interactions of objects, researchers aim to provide a
more comprehensive and accurate representation of system dynamics. Moreover, researchers
are expected to develop novel approaches that harness the inherent structures and meanings of
objects as they delve further into object-centric log analysis.</p>
        <p>To facilitate a comprehensive comparison of activity-centric and object-centric logs generated
from blockchain technology, this comparison is presented in table 2. These logging methods
have unique features. The Activity-Centric approach predominantly records event sequences
with accurate timestamps, whereas the object-centric approach emphasizes entities and objects,
highlighting temporal relationships and semantic structures. It is important to note that
scalability issues may arise with extensive event volumes in the activity-centric model, requiring domain
expertise for interpretation. On the other hand, object-centric logs excel in managing large
numbers of objects and promoting deeper understanding of data. This thorough analysis helps
researchers and practitioners choose the most suitable approach for their blockchain-related
projects.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Discussion and future work</title>
        <p>This section delves into the research endeavors that have concentrated on addressing the
challenges associated with retrieving logs from blockchain environments. Additionally, it
discusses the utilization of process mining techniques to analyze these retrieved logs and obtain
valuable insights.</p>
        <p>The application of blockchain technology in IOBP can enhance data traceability, and
prove</p>
        <p>Activity-centric Logs
Records sequences of events</p>
        <p>Individual events with timestamps
Temporal Representation</p>
        <p>Precise event timestamps
Scalability
Results Interpretation</p>
        <p>Can pose challenges with large
event volumes
May require deep domain expertise.</p>
        <p>Object-Centric Logs
Focuses on entities and objects
Objects with attributes and
relationships
Temporal relationships among
objects
Better suited for managing a large
number of objects
Can facilitate understanding with
semantic structures
nance at diferent stages of inter-organizational processes. The main objective of [ 24] is to
develop a methodology for generating event logs during the execution of IOBP, which includes
data cleaning techniques. The output will be in both XES and CSV formats, making it suitable
for process mining tasks such as discovery and conformance checking.However, there exist
several inherent limitations that afect the extraction of event logs across various networks. An
important constraint to highlight is the occurrence of empty blocks during the mining process.
It is worth noting that this restriction applies not only to Ethereum but also extends to numerous
other blockchain platforms. The occurrence of empty blocks in a blockchain, where there are
no transactions or significant smart contract interactions present, can be attributed to diferent
factors such as mining optimizations, network delays, and intricacies in blockchain consensus
protocols. These empty blocks disrupt the smooth flow and integrity of event logs. As a result,
extracting a complete and consistent history of events becomes increasingly dificult due to
these sparse blocks that complicate the extraction process significantly.</p>
        <p>
          Addressing the issue of cross-chain compatibility is an ongoing challenge that requires
attention in the blockchain space. The seamless facilitation of communication and collaboration
between diferent blockchain networks remains a priority. In [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], there is a focus on extracting
artifact-centric event data from Ethereum using the ACEL model. This discussion prompts us to
explore if there is already a standardized logging format or if extensions to ACEL are necessary
for efective cross-chain analysis. Additionally, it raises important questions about whether
existing process mining techniques should be adopted or adapted, or if novel methods tailored
specifically for cross-chain processes need to be developed. These academic considerations
contribute significantly to our understanding of this topic
        </p>
        <p>Our investigation focuses on examining the practical utilization of Ethereum and Hyperledger
Fabric, both well-known blockchain platforms with significant influence in the field. These
platforms stand at the forefront of blockchain technology, each ofering unique features that set
them apart from one another. However, a considerable gap exists in terms of understanding
how these platforms can be efectively applied in real-world scenarios. Future research can
explore ways to facilitate cross-platform transactions in diverse ecosystems. The integration
of blockchain technology and process mining holds promise in addressing the longstanding
challenge of implementing blockchain in inter-organizational processes. This area of research
has the potential to make a significant contribution by providing practical insights into the
real-world applications and relevance of blockchain technology.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <p>This literature review has focused on the extraction of event logs from blockchains, with a
distinction between activity-centric and object-centric approaches. An analysis reveals that
recent research eforts have primarily concentrated on object-centric event log extraction
methods. Additionally, we have discussed the limitations associated with these approaches
in their respective categories. Our proposal presents a unique approach that leverages the
integration of blockchain platforms and object-centric event logs to track the complete lifecycle
of blockchain data. This integrated approach provides a solid groundwork for future research
eforts, particularly in the field of Business Process Management Systems that are compatible
with both blockchain technology and process mining techniques.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgment References</title>
      <p>This work was partially supported by the LABEX-TA project MeFoGL: "Méthode Formelles
pour le Génie Logiciel"
[24] M. Morales-Sandoval, J. A. Molina, H. M. Marin-Castro, J. L. Gonzalez-Compean,
Blockchain support for execution, monitoring and discovery of inter-organizational
business processes, PeerJ Computer Science 7 (2021) e731.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A. S.</given-names>
            <surname>Rajasekaran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Azees</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Al-Turjman</surname>
          </string-name>
          ,
          <article-title>A comprehensive survey on blockchain technology</article-title>
          ,
          <source>Sustainable Energy Technologies and Assessments</source>
          <volume>52</volume>
          (
          <year>2022</year>
          )
          <fpage>102039</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Belchior</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Vasconcelos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Guerreiro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Correia</surname>
          </string-name>
          ,
          <article-title>A survey on blockchain interoperability: Past, present, and future trends</article-title>
          ,
          <source>ACM Computing Surveys (CSUR) 54</source>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>41</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J.</given-names>
            <surname>Köpke</surname>
          </string-name>
          , G. Meroni,
          <string-name>
            <given-names>M.</given-names>
            <surname>Salnitri</surname>
          </string-name>
          ,
          <article-title>Designing secure business processes for blockchains with SecBPMN2BC</article-title>
          ,
          <source>Future Generation Computer Systems</source>
          <volume>141</volume>
          (
          <year>2023</year>
          )
          <fpage>382</fpage>
          -
          <lpage>398</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>O.</given-names>
            <surname>López-Pintado</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>García-Bañuelos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ponomarev</surname>
          </string-name>
          ,
          <article-title>Caterpillar: A business process execution engine on the ethereum blockchain</article-title>
          ,
          <source>Software: Practice and Experience</source>
          <volume>49</volume>
          (
          <year>2019</year>
          )
          <fpage>1162</fpage>
          -
          <lpage>1193</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Geiger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Harrer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lenhard</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Wirtz, Bpmn 2.0: The state of support and implementation</article-title>
          ,
          <source>Future Generation Computer Systems</source>
          <volume>80</volume>
          (
          <year>2018</year>
          )
          <fpage>250</fpage>
          -
          <lpage>262</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A. B.</given-names>
            <surname>Tran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Lu</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <article-title>Lorikeet: A model-driven engineering tool for blockchain-based business process execution and asset management</article-title>
          ., in: BPM (Dissertation/Demos/Industry),
          <year>2018</year>
          , pp.
          <fpage>56</fpage>
          -
          <lpage>60</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>I.</given-names>
            <surname>Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Riveret</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Governatori</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ponomarev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <article-title>Untrusted business process monitoring and execution using blockchain</article-title>
          ,
          <source>in: Business Process Management: 14th International Conference, BPM</source>
          <year>2016</year>
          , Rio de Janeiro, Brazil,
          <source>September 18-22</source>
          ,
          <year>2016</year>
          . Proceedings 14, Springer,
          <year>2016</year>
          , pp.
          <fpage>329</fpage>
          -
          <lpage>347</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>L.</given-names>
            <surname>García-Bañuelos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ponomarev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <article-title>Optimized execution of business processes on blockchain</article-title>
          ,
          <source>in: Business Process Management: 15th International Conference, BPM</source>
          <year>2017</year>
          , Barcelona, Spain,
          <source>September 10-15</source>
          ,
          <year>2017</year>
          , Proceedings 15, Springer,
          <year>2017</year>
          , pp.
          <fpage>130</fpage>
          -
          <lpage>146</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Abid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Cheikhrouhou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kallel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jmaiel</surname>
          </string-name>
          ,
          <article-title>A blockchain-based self-sovereign identity approach for inter-organizational business processes</article-title>
          ,
          <source>in: 2022 17th Conference on Computer Science and Intelligence Systems (FedCSIS)</source>
          , IEEE,
          <year>2022</year>
          , pp.
          <fpage>685</fpage>
          -
          <lpage>694</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>H. M.</given-names>
            <surname>Marin-Castro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Tello-Leal</surname>
          </string-name>
          ,
          <article-title>Event log preprocessing for process mining: a review</article-title>
          ,
          <source>Applied Sciences</source>
          <volume>11</volume>
          (
          <year>2021</year>
          )
          <fpage>10556</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>R.</given-names>
            <surname>Hobeck</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <article-title>Towards Object-Centric Process Mining for Blockchain Applications</article-title>
          ,
          <source>Technical Report, EasyChair</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>L. M. M'Baba</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Assy</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Sellami</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Gaaloul</surname>
            ,
            <given-names>M. F.</given-names>
          </string-name>
          <string-name>
            <surname>Nanne</surname>
          </string-name>
          ,
          <article-title>Extracting artifact-centric event logs from blockchain applications</article-title>
          ,
          <source>in: 2022 IEEE International Conference on Services Computing (SCC)</source>
          , IEEE,
          <year>2022</year>
          , pp.
          <fpage>274</fpage>
          -
          <lpage>283</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>C.</given-names>
            <surname>Klinkmüller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ponomarev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. B.</given-names>
            <surname>Tran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Weber</surname>
          </string-name>
          , W. van der Aalst,
          <article-title>Mining blockchain processes: extracting process mining data from blockchain applications</article-title>
          , in: Business Process Management:
          <article-title>Blockchain and Central and Eastern Europe Forum: BPM 2019 Blockchain and</article-title>
          CEE Forum, Vienna, Austria, September 1-
          <issue>6</issue>
          ,
          <year>2019</year>
          , Proceedings 17, Springer,
          <year>2019</year>
          , pp.
          <fpage>71</fpage>
          -
          <lpage>86</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>G.</given-names>
            <surname>Acampora</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Vitiello</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B. Di</given-names>
            <surname>Stefano</surname>
          </string-name>
          , W. van der Aalst,
          <string-name>
            <given-names>C.</given-names>
            <surname>Günther</surname>
          </string-name>
          , E. Verbeek, Ieee 1849tm:
          <article-title>The xes standard</article-title>
          ,
          <source>IEEE Computational Intelligence Magazine</source>
          (
          <year>2017</year>
          )
          <fpage>4</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>R.</given-names>
            <surname>Mühlberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bachhofner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Di Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>García-Bañuelos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>López-Pintado</surname>
          </string-name>
          ,
          <article-title>Extracting event logs for process mining from data stored on the blockchain</article-title>
          ,
          <source>in: International Conference on Business Process Management</source>
          , Springer,
          <year>2019</year>
          , pp.
          <fpage>690</fpage>
          -
          <lpage>703</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>H. D.</given-names>
            <surname>Bandara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bockrath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Hobeck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Klinkmüller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Pufahl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rebesky</surname>
          </string-name>
          , W. van der Aalst, I. Weber,
          <article-title>Event logs of ethereum-based applications (</article-title>
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>C.</given-names>
            <surname>Klinkmüller</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ponomarev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. B.</given-names>
            <surname>Tran</surname>
          </string-name>
          , W. van der Aalst,
          <article-title>Eficient logging for blockchain applications</article-title>
          , arXiv preprint arXiv:
          <year>2001</year>
          .
          <volume>10281</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>A.</given-names>
            <surname>Koschmider</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Duchmann</surname>
          </string-name>
          ,
          <article-title>Extraction of meaningful events for process mining from blockchain, Blockchain and Robotic Process Automation (</article-title>
          <year>2021</year>
          )
          <fpage>13</fpage>
          -
          <lpage>29</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>A. F.</given-names>
            <surname>Ghahfarokhi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Park</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Berti</surname>
          </string-name>
          , W. M. van der Aalst,
          <article-title>Ocel: A standard for object-centric event logs</article-title>
          ,
          <source>in: European Conference on Advances in Databases and Information Systems</source>
          , Springer,
          <year>2021</year>
          , pp.
          <fpage>169</fpage>
          -
          <lpage>175</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>G.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. G.</given-names>
            <surname>L. de Murillas</surname>
          </string-name>
          ,
          <string-name>
            <surname>R. M. de Carvalho</surname>
          </string-name>
          ,
          <string-name>
            <surname>W. M. Van Der Aalst</surname>
          </string-name>
          ,
          <article-title>Extracting object-centric event logs to support process mining on databases</article-title>
          ,
          <source>in: Information Systems in the Big Data Era: CAiSE Forum</source>
          <year>2018</year>
          , Tallinn, Estonia, June 11-15,
          <year>2018</year>
          , Proceedings 30, Springer,
          <year>2018</year>
          , pp.
          <fpage>182</fpage>
          -
          <lpage>199</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>P.</given-names>
            <surname>Beck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bockrath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Knoche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Digtiar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Petrich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Romanchenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Hobeck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Pufahl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Klinkmüller</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <article-title>Blf: A blockchain logging framework for mining blockchain data</article-title>
          ., in: BPM (PhD/Demos),
          <year>2021</year>
          , pp.
          <fpage>111</fpage>
          -
          <lpage>115</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <surname>W. M. van der Aalst</surname>
          </string-name>
          ,
          <article-title>Enhancing data-awareness of object-centric event logs</article-title>
          , in: Process Mining Workshops:
          <article-title>ICPM 2022 International Workshops</article-title>
          , Bozen-Bolzano, Italy,
          <source>October 23-28</source>
          ,
          <year>2022</year>
          , Revised Selected Papers, volume
          <volume>468</volume>
          ,
          <string-name>
            <surname>Springer</surname>
            <given-names>Nature</given-names>
          </string-name>
          ,
          <year>2023</year>
          , p.
          <fpage>18</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>A.</given-names>
            <surname>Rebmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-R.</given-names>
            <surname>Rehse</surname>
          </string-name>
          ,
          <string-name>
            <surname>H. Van der Aa</surname>
          </string-name>
          ,
          <article-title>Uncovering object-centric data in classical event logs for the automated transformation from XES to OCEL</article-title>
          , in: International Conference on Business Process Management, Springer,
          <year>2022</year>
          , pp.
          <fpage>379</fpage>
          -
          <lpage>396</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>